Does Pantheon Work in China? ICP, Data Residency & an Offshore WebOps Host
Pantheon runs no region inside mainland China — it hosts WordPress and Drupal sites on Google Cloud in Canada, Australia, the EU and the US — so a China-facing site is served offshore with no ICP-filing path, and your users' CMS and visitor data lands outside the mainland under PIPL. A compliance-first look at the two doors.
Does Pantheon work in China?
No — not as a compliant mainland presence. Pantheon hosts your WordPress or Drupal site on Google Cloud in Canada, Australia, the EU or the US, with no region inside mainland China — so there is nothing on Pantheon to attach an ICP filing to, and "we're on Pantheon" does not carry across the border.
Pantheon states it has "been running as a SaaS offering on Google Cloud since 2017," and lists its footprint as "data center locations in Canada, Australia, and the European Union—with more on the way!" — none of it inside the mainland. A public site served to mainland visitors needs an ICP filing bound to a hosting resource physically in China, and Pantheon has none; meanwhile the CMS, account and visitor data your site stores lives on Google Cloud offshore — a cross-border transfer PIPL governs. The table below is Pantheon's own wording and the rule each line triggers.
This is a risk map, not a verdict — whether you need an ICP filing, in-country storage, or both turns on what you serve, how much personal data you hold and who your users are. Our China team can map your exposure with you →
Compliance snapshot
- ✕ A public site served from Pantheon's offshore cloud can't be ICP-filed
- ✕ Pantheon runs no mainland-China region — nothing in-country to file against
- ! China users' CMS and visitor data sit on Google Cloud, outside the mainland — PIPL applies
- ! Pantheon's Global CDN has no mainland PoP; China traffic is served cross-border
- ! A compliant China presence needs ICP-filed, in-country delivery Pantheon doesn't offer
What Pantheon's own documentation says about China
| Fact | Primary source |
|---|---|
| Pantheon runs on Google Cloud, with no region inside mainland China. Pantheon states it has "been running as a SaaS offering on Google Cloud since 2017," and lists its hosting footprint as "data center locations in Canada, Australia, and the European Union—with more on the way!" None sits inside the mainland, so a China-facing Pantheon site is served entirely offshore. | Pantheon — Global Regions & Google Cloud press materials (pantheon.io), retrieved 2026-10-07 |
| With no mainland hosting resource, there is nothing to attach an ICP filing to. A public website served to mainland visitors from inside China requires an ICP filing bound to a hosting resource physically in the mainland (State Council Order No. 292; MIIT Order No. 33). Because every Pantheon region is offshore, the platform offers no ICP-filing path of its own — being reachable from China is not the same as being cleared to operate there. | Pantheon — Global Regions (pantheon.io), retrieved 2026-10-07; State Council Order No. 292; MIIT Order No. 33 |
| Your site's personal data lives on Google Cloud, outside the mainland. As a WebOps platform for WordPress and Drupal, Pantheon stores your CMS content, user accounts and visitor data in its offshore Google Cloud regions. For Chinese users that is a cross-border transfer of personal information under PIPL (notice, separate consent and a transfer mechanism, Articles 38–43), and a CIIO or large-volume handler must store China-collected personal information in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — a duty an offshore region cannot meet. | Pantheon — Global Regions / Global CDN docs (pantheon.io & docs.pantheon.io), retrieved 2026-10-07; PIPL Articles 38–43 & 40; Cybersecurity Law Article 39 (formerly Article 37) |
| Pantheon's own Global CDN has no mainland-China edge. Pantheon describes its Global CDN as a way to "tap into powerful and strategically distributed CHI metro Points of Presence (POPs) around the globe," routing each request to the "closest" POP — but none is inside the mainland, so Chinese visitors are served from across the border. That delivery gap is the reachability half of the question, separate from the legal half that decides whether you may operate there at all. | Pantheon Docs — Global CDN (docs.pantheon.io), retrieved 2026-10-07 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For an audience inside mainland China, the first thing to settle about Pantheon is not how quickly it paints a page — it is whether a site served from Pantheon can be operated there lawfully at all. Pantheon answers the part that decides it in its own documentation: it is a WebOps platform that runs on Google Cloud, with hosting regions in Canada, Australia and the European Union and a content delivery network whose points of presence are spread around the globe — not one of them inside the mainland. A China-facing Pantheon site is therefore reachable but entirely offshore, which leaves it with no footing for the ICP filing a public mainland site requires, and turns the personal data it stores for Chinese users into a cross-border transfer China’s law governs. The delivery distance is real; the licensing and the data residency are the exposure.
Pantheon in China at a glance
| What decides it | In Pantheon's own terms |
|---|---|
| Where it runs | A WebOps platform running “as a SaaS offering on Google Cloud,” with data center regions in Canada, Australia and the European Union (and the United States). No region is inside mainland China. |
| Content delivery | Pantheon's Global CDN routes each visitor to the “closest” of its “strategically distributed CHI metro Points of Presence (POPs) around the globe” — none in the mainland, so China traffic is served across the border. |
| Serving the public | A site served to mainland visitors from inside China needs an ICP filing tied to a mainland hosting resource. With no mainland region, Pantheon offers no ICP-filing path of its own. |
| Your data on Pantheon | CMS content, user accounts and visitor data for Chinese users sit on Google Cloud offshore — a cross-border transfer PIPL governs, plus a data-localization duty for CIIOs and large-volume handlers that offshore regions cannot meet. |
| Is it reachable? | Yes — the site loads, but from offshore and with no nearby CDN edge, so distance shows up as slow, cross-border delivery rather than a block. |
No mainland region, so no footing for an ICP filing
Pantheon hosts on Google Cloud, and its published footprint stops at the mainland’s edge: in its own materials it has “been running as a SaaS offering on Google Cloud since 2017,” and its Global Regions page lists “data center locations in Canada, Australia, and the European Union—with more on the way!” — with the United States as its default home. Not one of those regions is inside mainland China.
That geography settles the licensing question before performance is ever in play. A public-facing website delivered to mainland visitors from inside China turns on an ICP filing (ICP 备案) under State Council Order No. 292 and MIIT Order No. 33, and that filing has to attach to a hosting resource that physically sits in the mainland. Pantheon runs none, so there is simply nothing on the platform to file against. This is where “our site is already on Pantheon” stops short: being reachable from China is not the same as being cleared to operate there, and no amount of platform tuning conjures the in-country footing a filing needs.
Your China users’ data stays on Google Cloud, offshore
Pantheon is a WebOps platform for WordPress and Drupal, so the personal data your site handles — CMS records, registered-user accounts, form submissions and visitor logs — lives in Pantheon’s Google Cloud regions in Canada, Australia, the EU or the US. For users in China, moving that information offshore is a cross-border transfer under China’s Personal Information Protection Law, and the handler — you, not Pantheon — has to give notice, obtain separate consent, and clear one 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 none of Pantheon’s offshore regions can satisfy.
Reachable, not cleared — the delivery half
A Pantheon site is not a blank screen in China; it loads. But every byte arrives from offshore, because Pantheon’s Global CDN — which it describes as a way to “tap into powerful and strategically distributed CHI metro Points of Presence (POPs) around the globe” — has no point of presence inside the mainland, and each visitor is routed to the “closest” edge, which for a Chinese user is still across the border. So the exposure on a China-facing Pantheon site is not only that delivery is slow and uneven — it is that reaching the site gives you neither an ICP filing nor in-country data residency. Those gaps are compliance facts, and no cache tuning or edge configuration closes them.
This is a risk map, not a verdict: whether an ICP filing, in-country storage, or both apply to you turns on what your site serves, how much personal data it holds, and who its users are — a call worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep running on Pantheon. What Pantheon cannot give a mainland audience — a lawful, in-country footing — we add alongside it: compliant, ICP-filed delivery from inside the mainland, sitting in front of the Pantheon origin you already publish from, with no rebuild, no second codebase and no migration off the WebOps workflow your team relies on. Our China team first maps which obligations actually bind you — ICP filing, PIPL cross-border, data residency — against your entity and your data volumes, then stands up the in-country delivery and storage a compliant presence needs, so your WordPress or Drupal site stays exactly where it runs today.
Related reading:
Frequently Asked Questions
Does our existing Pantheon site work in China?
It will load, but "working" in the compliance sense is the harder question. Pantheon hosts your site on Google Cloud in Canada, Australia, the EU or the US — none inside mainland China — so a public site served to mainland visitors has no in-country hosting resource to carry an ICP filing, and the personal data it stores sits offshore under PIPL. Reaching China and being cleared to operate there are two different things.
Can we just move our Pantheon site into a mainland-China region?
Pantheon doesn't offer one. Its published footprint is Canada, Australia and the European Union, all on Google Cloud, with no mainland-China region — so unlike a cloud that runs a separate China partition, there is no in-country Pantheon region to switch to. A compliant mainland presence has to be built on an ICP-filed hosting resource physically inside China, which sits alongside your Pantheon origin rather than replacing it.
Can 21YunBox help make our Pantheon site work in China?
Yes. Our China team can map which obligations apply — assessing your PIPL cross-border and data-residency exposure for your entity, data volumes and users — and stand up the ICP-filed, in-country delivery a compliant China presence requires, in front of the Pantheon site you already run. Get in touch to work through your specific case.
