With hosting most companies think of the form: Odoo Online, Odoo.sh or self-hosting. For an international company a second question 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, the choice between Europe, a Singapore node or self-hosting becomes urgent. This post covers that trade-off, as a deep-dive on our hosting guide.
Three questions that coincide
Data location looks like a technical detail. It touches three things at once that you cannot judge 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 with one location in the Netherlands those three are rarely a problem. Once you go international, they start to grate. Then the default choice is no longer a given.
Where your data can live
The options, because that is where it starts:
- Odoo Online runs your database in a data centre in a region that matches you. Simple, with little say over 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 when 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. You carry the management yourself.
The hosting guide covers the choice between these forms. Here it is about the location behind it.
Odoo from China: the sharpest case
If a large part of your team sits in mainland China, a question that never comes up in the Netherlands becomes a daily one: does Odoo stay fast and reliably reachable?
Latency plus the Great Firewall
Access to cloud environments outside China can be slow or unreliable. Two things coincide: the sheer distance to a server in Europe or the US, and the Great Firewall that filters and slows international traffic. For an occasional user that is annoying. For an operational team processing orders, stock and purchasing in Odoo all day, it brakes the work.
A company with a site in China and one in Europe cannot simply pick the European node and expect the Chinese office to work smoothly with it. We saw this at a sourcing and import company where most users sat in China. There, “Singapore or Europe” was a daily question.
What Odoo.sh offers: Singapore and Mumbai
None of the 7 Odoo.sh locations is in China. The nearest are Singapore and Mumbai.
A node in Singapore or Mumbai lowers latency from China noticeably compared to Europe or the US. For many companies that is enough: users in China work acceptably fast, and you keep the management ease of Odoo.sh. It does not remove the Great Firewall. International traffic stays international traffic, and reliability does not match a server inside the country.
When self-hosting inside China is the only route
Two situations push you towards self-hosting inside China:
- Strict data residency. If (certain) data must physically stay in China, no Odoo.sh location covers that. Local storage is only possible through your own environment inside the country.
- Too slow despite a regional node. If Singapore or Mumbai is still too slow or too erratic for your operational team, a server inside China is the only way to get truly low latency.
Self-hosting then means running Odoo on a server or cloud provider inside China, for example a local region of Alibaba Cloud or Tencent Cloud. You get low latency and true local storage. The price is the management you carry yourself or via a partner: updates, backups, security. A publicly reachable website may also need an ICP registration; for an internal business application that usually does not apply.
Singapore/Mumbai or self-hosting in China
| Question | Towards Singapore/Mumbai (Odoo.sh) | Towards self-hosting in China |
|---|---|---|
| Must data physically stay in China? | No | Yes |
| How critical is speed for the China team? | Acceptable with regional node | Maximal, local server needed |
| How much management do you want to carry? | Little (managed) | More (self or via partner) |
| Publicly reachable site? | No ICP question | Possible ICP registration |
Most companies with a China team and no hard local-storage requirement do fine with a node in Singapore or Mumbai. Once data residency or operational speed is decisive, it tips towards self-hosting inside China. If you also run a Chinese entity, read how Chinese accounting works in Odoo.
Data residency and compliance
The second question is legal. 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 law requires data to stay in the country, self-hosting or a local environment may be needed. China is the clearest example, because no Odoo.sh node exists there.
- If you work with multiple entities in multiple countries, the setup can differ per entity. That ties in with how you connect the international accounting.
The rule: test this up front. Discovering data residency requirements afterwards is an expensive surprise.
How to choose
There is no universally right location. There is the right one for your situation. Four questions decide it:
- 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 and puts the maintenance on you. See the trade-off in the hosting guide.
In short
For an international company, hosting is a question of location as much as form. Odoo.sh lets you choose from 7 fixed regions, self-hosting gives full control, and Odoo Online is the simplest and the least steerable. There is no Odoo.sh node in China: Singapore and Mumbai lower latency, but do not remove the Great Firewall. If data must stay in China, or speed falls short despite a regional node, self-hosting inside China is the only route. Test performance and residency up front.
Do you have users or sites in multiple countries, or a team in China, 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.
Read more: Odoo hosting: Online, Odoo.sh or self-hosting? · Odoo for international rollouts · International accounting with Odoo · Chinese accounting with Odoo · Odoo for procurement, sourcing and import companies · What does an Odoo implementation cost?