If a large part of your team sits in China, a question that never comes up in the Netherlands is suddenly a daily one: does Odoo stay fast and reliably reachable? There is no Odoo.sh data centre in China, Singapore and Mumbai are the nearest, and the Great Firewall stays a factor. This is what does work, when self-hosting inside China is the only route, and how to choose - as a practical elaboration of the broader hosting and data-residency trade-off.
The problem: latency plus the Great Firewall
Access to cloud environments outside China can be slow or unreliable. That comes from two things coinciding: 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 is a brake on the work.
This is exactly the profile where the default choice is no longer a given. A company with a site in China and one in Europe - such as a sourcing and import company - cannot simply pick the European node and expect the Chinese office to work smoothly with it.
What Odoo.sh does offer: Singapore and Mumbai
Odoo.sh runs on Google Cloud and offers 7 fixed hosting locations: Belgium, Iowa (US), Toronto, Dammam (Saudi Arabia), Mumbai (India), Singapore and Sydney. None of them 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: your users in China work acceptably fast, and you keep the management ease of Odoo.sh. But it does not remove the Great Firewall - international traffic stays international traffic, and reliability is not equal to a server inside the country.
Self-hosting inside China: when it is the only route
Two situations force towards self-hosting inside China:
- Strict data residency. If (certain) data must physically stay in China, no Odoo.sh location covers that. There is no node in China, so local storage is only possible through your own environment inside the country.
- Insufficient speed 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 achieve 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. That gives low latency and true local storage - at the cost of the management you carry yourself (or via a partner): updates, backups, security. For a publicly reachable website an ICP registration may also be required; for an internal business application that usually does not apply.
The trade-off: management ease versus local control
There is no universally right answer; there is the right one for your situation.
| 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 but no hard local-storage requirement do fine with a node in Singapore or Mumbai. As soon as data residency or operational speed is decisive, it tips towards self-hosting inside China.
In short
Running Odoo from China is possible, but requires a deliberate choice. There is no Odoo.sh node in China; Singapore and Mumbai are the nearest and lower latency, but do not remove the Great Firewall. If data must physically stay in China, or speed is insufficient despite a regional node, self-hosting inside China is the only route - with more management as the price. Test the data-residency requirement up front and weigh speed and management against each other explicitly.
Do you have a team or site in China and are unsure about the best hosting setup? Schedule a no-obligation Quickscan and together we determine whether Singapore/Mumbai suffices or self-hosting inside China is needed.
Read more: Odoo hosting and data residency international · Chinese accounting with Odoo · International accounting with Odoo · Odoo for procurement, sourcing and import companies