Odoo hosting and data residency for international companies: where does your data live (Singapore, Europe or China)?

With hosting most companies think of “which form”: Odoo Online, Odoo.sh or self-hosting. For an international company there is a question on top of that, which often weighs heavier: where does your data live, and who can reach it quickly and legally? As soon as a large part of your team sits in China, for example, the choice between a Singapore node, Europe or a self-hosted environment suddenly becomes urgent. This is the trade-off, as a deep-dive on our hosting guide.

Three questions that coincide

Data location looks like a technical detail, but it touches three things at once that you cannot see separately:

Performance and access - how fast and reliably can your users reach it, from where they sit?
Data residency and compliance - must (certain) data physically stay in a country or region?
The hosting form - Odoo Online, a chosen Odoo.sh region, or self-hosting?

For a company on one location in the Netherlands those three are rarely a problem. As soon as you go international, they start to grate - and then the default choice is no longer a given.

Where your data can live

Briefly the options, because that is where it starts:

Odoo Online runs your database in a data centre in a region that matches you. Simple, but you have little steering on the exact location.
Odoo.sh runs on Google Cloud and lets you choose the hosting region when setting up your project, from 7 fixed locations: Belgium (Europe), Iowa (US), Toronto (Canada), Dammam (Saudi Arabia), Mumbai (India), Singapore and Sydney. This is the route if the data location must be a deliberate choice - provided your destination is on that list.
Self-hosting (on-premise or with your own hosting provider) gives full control over where the data lives - at the cost of the management you carry yourself.

The choice between these forms we work out more broadly in the hosting guide; here it is about the location behind it.

Performance from China: the sharpest example

If a large part of your team sits in mainland China, this is the point you cannot ignore. Access to cloud environments outside China can be slow or unreliable - a known phenomenon. Odoo.sh has no data centre in China itself; the nearest fixed locations are Singapore and Mumbai. Such a node in the region lowers latency noticeably, but does not fully remove the underlying limitations.

The trade-off then becomes concrete: a regional node (Singapore or Mumbai) for daily speed, or - for strict local-storage requirements - self-hosting within China, because an Odoo.sh node in China does not exist. We saw this at a sourcing and import company where most users sat in China: precisely there, “Singapore versus Europe” becomes not a theoretical but a daily question.

Data residency and compliance

The second question is legal, not technical. Data residency is the requirement that certain data physically stays in a country or region. In the EU the GDPR applies; some countries have their own data localisation laws. That co-determines your choice:

If your data falls under European rules, an EU node is the logical choice.
If local legislation requires data to stay in the country, self-hosting or a local environment may be needed.
If you work with multiple entities in multiple countries, the setup can differ per entity - which relates to how you connect the international accounting.

The rule: test this up front. Discovering data residency requirements afterwards is an expensive surprise.

The trade-off in practice

There is no universally right location; there is the right one for your situation. The questions that decide the choice:

Where do your daily users sit? The majority determines the logical region; the rest deliberately accepts a bit more latency.
Which data requirements apply? GDPR, local data localisation, customer or sector requirements.
How critical is speed from difficult regions? For an operational team working in the system all day, latency weighs heavier than for occasional users.
How much management do you want to carry? Self-hosting gives control over the location, but puts the maintenance on you - see the trade-off in the hosting guide.

In short

For an international company hosting is not only a question of form, but of location: where does your data live, and who can reach it quickly and legally? Odoo.sh lets you choose from 7 fixed regions, self-hosting gives full control, and Odoo Online is the simplest but the least steerable. If your team is spread across regions - certainly with part in China - you make that choice deliberately, based on where your users sit and which data requirements apply. Test performance and residency up front, not afterwards.

Do you have users or sites in multiple countries and are unsure about the data location? Schedule a no-obligation Quickscan and together we will determine the right hosting form and region for your situation.

Frequently asked questions

Where does my Odoo data live?

That depends on your hosting form. Odoo.sh runs on Google Cloud and offers 7 fixed locations: Belgium (Europe), Iowa (US), Toronto (Canada), Dammam (Saudi Arabia), Mumbai (India), Singapore and Sydney - you pick one when setting up your project. With Odoo Online your database runs in a region that matches your location. If you self-host (on-premise or with your own provider), you fully determine where the data lives. For an international company this is a deliberate choice, not a detail.

Does Odoo work well from China?

Access to cloud environments from mainland China is a known point of attention: traffic to servers outside China can be slow or unreliable. Odoo.sh has no data centre in China; the nearest fixed locations are Singapore and Mumbai (India). Those help latency but do not fully remove the underlying limitations. If most of your users sit in China and strict requirements apply, self-hosting within China is the only route to local storage - weigh that explicitly.

Can I choose which region Odoo runs in?

With Odoo.sh you choose the hosting region when setting up your project, from 7 fixed Google Cloud locations: Belgium, Iowa (US), Toronto, Dammam (Saudi Arabia), Mumbai, Singapore and Sydney. With Odoo Online your database runs in a region matching your location. If you want full control over the data location - for data residency requirements or a location not on the list - self-hosting is the route.

What does data residency mean for Odoo?

Data residency is the requirement that (certain) data physically stays in a country or region. In the EU the GDPR applies; some countries have their own data localisation laws. For Odoo this means you choose the hosting region and form that meet your requirements: an EU node for GDPR-sensitive data, or self-hosting where the law requires local storage. Test this up front, not afterwards.

Odoo hosting in Singapore or Europe: how do you choose?

Choose based on where your users sit and what the data requirements are. If your team is mainly in Asia, a node in the region (Singapore, or Mumbai) lowers latency. If your data falls under European rules or your head office is in the EU, a European node (Belgium) is more logical. With multiple regions at once you choose the location where most daily users sit, and deliberately accept the latency for the rest.

Recognize this from your own setup?

A 30-min scan turns hunches into a concrete view, what stays standard Odoo, what becomes custom, what doesn’t need code at all.

Get in touch ← Back to blog