Odoo May Use AWS for Non-EU Cloud Databases from 24 September

From 24 September 2026, Odoo may use Amazon Web Services alongside its existing providers to host Odoo Cloud databases in non-EU regions. New customers outside the EU may be placed on AWS depending on their selected hosting region and Odoo’s infrastructure requirements. Existing databases will ordinarily remain on their current infrastructure, although Odoo says they may move to AWS during lifecycle or restoration operations. (Odoo Sub Processor Update Non Eu Regions Only; Privacy)

The expansion does not apply to databases hosted in Odoo’s EU region. Customers can continue to select an available Odoo hosting region, but they cannot choose the infrastructure provider used within that region. (Odoo Sub Processor Update Non Eu Regions Only; Privacy; Cloud Sla) Organisations should therefore treat the hosting region and infrastructure provider as separate matters when reviewing data location, contracts and vendor risk.

What changes on 24 September

The change expands the infrastructure providers Odoo may use outside the EU. It does not mean every new non-EU database will be placed on AWS or that all existing databases will be transferred on the effective date. (Odoo Sub Processor Update Non Eu Regions Only; Privacy)

For new customers, placement may depend on the selected region and Odoo’s infrastructure requirements. Customers can select a hosting region only where that region is available, and Odoo does not provide a separate choice of infrastructure provider within it. (Odoo Sub Processor Update Non Eu Regions Only; Privacy; Cloud Sla) Selecting an Odoo region therefore does not confirm that a particular infrastructure company will host the database.

Odoo’s published update does not identify which new databases will use AWS or describe how databases will be allocated among providers. (Odoo Sub Processor Update Non Eu Regions Only) Organisations planning a non-EU deployment after 24 September 2026 should confirm the proposed hosting region and ask what provider information Odoo can supply before completing procurement, privacy or security approval.

Existing databases are not automatically moving

Odoo says existing non-EU customers will ordinarily remain on their current infrastructure. A database may nevertheless move to AWS later through lifecycle or restoration operations. (Odoo Sub Processor Update Non Eu Regions Only) The effective date is therefore not a universal migration date. At the same time, the provider supporting an existing database may not remain unchanged throughout the database’s life.

The update does not define which lifecycle events may cause a move or explain the customer notification process for a provider change. (Odoo Sub Processor Update Non Eu Regions Only) Organisations with provider-specific requirements should ask Odoo how these operations are managed and what information is provided before or after a transfer.

Internal records should distinguish between the selected Odoo hosting region and the provider currently supporting the database. Risk registers, processing inventories and architecture documents that name only the current provider may need to account for Odoo’s ability to use AWS in non-EU regions. (Odoo Sub Processor Update Non Eu Regions Only; Privacy)

EU-hosted databases are excluded

Odoo states that databases hosted in its EU region are not affected by this AWS expansion. (Odoo Sub Processor Update Non Eu Regions Only) Organisations should confirm the assigned hosting region of each database rather than relying on office locations, billing addresses or user locations. The exclusion is based on the region where the database is hosted.

Customers may select an Odoo hosting region subject to availability, but the update does not establish that every customer can move to the EU region. (Odoo Sub Processor Update Non Eu Regions Only; Privacy; Cloud Sla) Any organisation considering a region change should first confirm availability and assess its contractual, operational and data-location requirements.

Region choice does not include provider choice

Customers can select an available Odoo hosting region, but Odoo controls the infrastructure provider used within it. The AWS update does not introduce an option for customers to request or reject a particular provider inside a non-EU region. (Odoo Sub Processor Update Non Eu Regions Only; Privacy; Cloud Sla)

This distinction matters when procurement or compliance questionnaires ask about both data location and hosting providers. Naming the selected region answers the location question, but it does not establish that one provider will support the database permanently. (Odoo Sub Processor Update Non Eu Regions Only; Privacy; Cloud Sla)

Where internal policy requires approval of named providers, organisations should determine whether that approval can cover the providers Odoo may use within the selected region. A requirement limiting hosting to one provider may not align with Odoo’s stated model for non-EU regions. (Odoo Sub Processor Update Non Eu Regions Only; Privacy; Cloud Sla)

Service commitments remain unchanged

Odoo says its commitments concerning security, backups, availability and disaster recovery remain unchanged regardless of the underlying infrastructure provider. The addition of AWS does not create a separate set of stated service commitments for AWS-hosted databases. (Odoo Sub Processor Update Non Eu Regions Only; Cloud Sla)

Customers should still compare the applicable Odoo Cloud terms and service-level material with their own requirements. Odoo’s statement does not resolve organisation-specific questions about evidence, audit records, recovery expectations, risk acceptance or internal control wording. (Odoo Sub Processor Update Non Eu Regions Only; Cloud Sla)

Review subprocessor and governance records

Because Odoo is expanding its possible use of AWS for non-EU Cloud databases, organisations may need to review records that identify Odoo’s subprocessors or supporting infrastructure providers. (Odoo Sub Processor Update Non Eu Regions Only; Privacy) The necessary action will depend on each organisation’s contracts, privacy obligations and approval processes.

A review should identify each Odoo Cloud database, its selected region, whether it is existing or planned, and the provider information recorded internally. Teams can then check whether their documentation allows for provider changes during lifecycle or restoration operations. (Odoo Sub Processor Update Non Eu Regions Only)

The update should not be recorded as confirmation that a particular existing database will transfer to AWS. Odoo’s stated position is that existing non-EU databases ordinarily remain on their current infrastructure, although a later move may occur during lifecycle or restoration work. (Odoo Sub Processor Update Non Eu Regions Only)

What to verify with Odoo

Before approving a new non-EU deployment after 24 September 2026, organisations should confirm the selected hosting region, its availability and the provider information Odoo can supply for the planned database. They should also ask how a later provider change would appear in customer records or notifications. (Odoo Sub Processor Update Non Eu Regions Only; Privacy; Cloud Sla)

For existing databases, customers should verify the current region and provider, what Odoo means by lifecycle operations in practice, and the process followed when restoration results in a change of infrastructure. Odoo confirms that such a move may occur, but its update does not provide operational details. (Odoo Sub Processor Update Non Eu Regions Only)

Vendor-risk assessments, processing records, architecture diagrams and approval documents should distinguish between Odoo as the cloud service provider and the underlying infrastructure provider. The confirmed position is that customers choose an available region, Odoo chooses the provider within that region, and databases hosted in the EU region are excluded from this AWS expansion. (Odoo Sub Processor Update Non Eu Regions Only; Privacy; Cloud Sla)