Does DatoCMS Work in China? ICP, EU Data Residency & the Compliance Gate

DatoCMS is a capable way to manage content, and nothing here asks you to move off it. But “does DatoCMS work in China” quietly folds together two different questions. DatoCMS is a headless CMS — a content backend that feeds whatever website or app you build, not the page a visitor actually opens. The thing that has to be cleared to operate in mainland China is therefore the public site you deploy from it, and clearing it is a compliance matter — an ICP filing, and personal-data rules — that a content backend hosted in Europe neither answers nor can answer on your behalf. Below is what DatoCMS documents about itself, and the doors that decide the question, in its own words and China’s own law.

DatoCMS in China at a glance

Headless means the gate isn’t on DatoCMS

Start with what DatoCMS says it is. In its own documentation it is “a cloud-based headless CMS,” and “a headless CMS clearly separates the actual content from the display layer and the front-end user experience.” It hands your content to whatever frontend you build through “a content infrastructure that comprises different APIs” — a backend, in other words, much like a database sitting behind your site rather than the site itself.

That distinction is the whole compliance story. A mainland visitor never loads DatoCMS; they load the website you deploy, and it is that website — the frontend served to people inside China — that an ICP filing (备案) governs under State Council Order No. 292 and MIIT Order No. 33. DatoCMS carries no filing of its own, and being a backend it was never going to: there is nothing on DatoCMS for a mainland regulator to file against. So “we use DatoCMS” tells you nothing about whether your China-facing site is cleared to operate — the filing lands on you, wherever and however you publish.

Your content’s home is Ireland, not the mainland

Where that backend lives still matters, because your content — and anything you keep alongside it — lives there too. DatoCMS is direct about the location: “all our servers are based in European Union, in Ireland in particular,” running on “a dedicated Kubernetes cluster in AWS,” and on its own community forum it confirms that “all our CMS hosting and data storage are based exclusively in the EU (Ireland),” with no option to pick another region. There is no mainland-China region to select, and no self-hosting path into one.

For most teams that is a modest exposure, and worth saying plainly: DatoCMS mainly holds your content, not a database of your users, so it is not primarily a store of personal information. But to the extent you do keep China users’ personal data in it — form submissions, member profiles, author records — that data now rests in the EU, and moving or exposing it across the border is a cross-border transfer under China’s Personal Information Protection Law: notice, separate consent, and one approved transfer mechanism (a CAC security assessment, the CAC standard contract, or certification — Articles 38–43). If you are a critical information infrastructure operator or a large-volume handler, personal information collected in China must be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)), a residency duty an Ireland-only store cannot meet.

Reachable and cached is not the same as licensed

DatoCMS leans on delivery to stay quick: content moves through “a global network of delivery” with “a layer of caching with Cloudflare,” pushing copies close to visitors wherever they sit. That makes a page load faster, and it is easy to read speed as the answer to “does it work in China.” It isn’t. A cache sitting near a user is a performance feature, not a permit: it holds no ICP filing, and it does not move your authoritative data out of Ireland.

So reachability is the lighter half of this question. Even a site that paints quickly from cache still needs the filing for its public frontend, and still has to account for where its users’ personal data ends up. Those are compliance facts, and no amount of edge caching settles them.

This is a risk map, not a verdict: whether you need an ICP filing, in-country data storage, or both comes down to what your site collects, how much personal data you hold, and who your visitors are — worth settling with counsel before you build.

Where 21YunBox fits — a compliant overlay, not a migration

You keep DatoCMS as your content backend, exactly as it runs today — same models, same APIs, same editing workflow. What a headless CMS hosted in Europe cannot give you is the one thing a mainland audience requires: compliant, ICP-filed delivery from inside the mainland, placed in front of the public site you build from DatoCMS — no rebuild, no second codebase, and no move off DatoCMS. Our China team works out which obligations land on that public site — the ICP filing, and any PIPL cross-border or data-residency duty for your entity, your data and your users — and stands up the in-country delivery a lawful China presence needs, while DatoCMS stays your single source of content.

Get a compliance assessment →

Related reading:

• What is the China ICP license, and how do you get one?
• Cross-border data transfers under PIPL