Does Acquia work in China?
Whether Acquia works in China is a hosting-location question — ICP filing and data residency — before it is a speed one. Acquia Cloud is managed Drupal hosting, and Acquia's own documentation puts that hosting on AWS regions across the United States, Europe and Asia Pacific, with none inside mainland China.
That one fact — where Acquia runs your Drupal site — sets the two answers a mainland audience turns on. A public site served to people in mainland China needs an ICP filing (备案) bound to a licensed in-country host, and Acquia's offshore regions give that filing nothing to attach to. Because an Acquia-hosted site also keeps user accounts, comments and webform submissions on those same offshore servers, the personal data of visitors in China leaves the country — a cross-border transfer PIPL governs. The table below sets Acquia's own wording against the rule each door triggers.
This is a risk picture to confirm with counsel, not a verdict — what applies turns on whether you serve the public in China and the data your site collects. Our China team can map your Acquia hosting and data exposure with you →
Compliance snapshot
- ✕ Acquia Cloud is managed Drupal hosting on AWS regions across the US, Europe and Asia Pacific — none inside mainland China (Acquia's own docs)
- ✕ Served to the mainland from those offshore regions, a public site has no in-country host for the ICP filing (备案) to attach to
- ! Accounts, comments and webform data live on offshore AWS — for visitors in China that's a cross-border PI transfer under PIPL
- ! Offshore-hosted pages cross the border on every request and third-party assets can fail on their own — reachability, not a block
- ✓ Compliant path: keep Acquia as your Drupal origin and add ICP-filed, in-country delivery in front — an overlay, not a re-platform
What decides whether an Acquia-hosted site can serve mainland China
| Fact | Primary source |
|---|---|
| In Acquia's own documentation, Acquia Cloud runs on AWS regions outside mainland China. Acquia's Products and Services glossary states that "Currently, Acquia utilizes AWS services in the following regions" and lists US East (Northern Virginia), US West (Oregon), EU West (Dublin, Ireland), EU Central (Frankfurt, Germany), APAC (Singapore, Sydney) and South America (São Paulo) — none inside mainland China. Acquia is managed Drupal hosting, so that region list is where your site and its data physically live. | Acquia Docs — Products and Services Guide: Definitions ("Regions"), retrieved 2026-10-08 |
| A public mainland site needs an ICP filing, and Acquia's offshore regions have nothing to file against. Under State Council Order No. 292 (Article 4) and MIIT Order No. 33, an ICP filing (备案) attaches to a hosting resource physically inside mainland China and to a mainland legal entity. Because Acquia Cloud offers no mainland region, a site served to China from Acquia has no in-country resource for the filing to bind to — the gap is the hosting location, not Drupal. | State Council Order No. 292 (Measures for the Administration of Internet Information Services), Article 4; MIIT Order No. 33 |
| Content and personal data on Acquia sit offshore, so for a China audience that is a cross-border transfer under PIPL. An Acquia-hosted Drupal site keeps user accounts, comments and contact or webform submissions in its database on Acquia's AWS regions. Carrying the personal data of people in China out of the country engages PIPL (Chapter III, Articles 38–43: notice, separate consent, and one transfer mechanism — a CAC security assessment, the CAC standard contract, or certification). A CIIO or large-volume handler must keep personal information collected in China inside the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). | PIPL Chapter III, Articles 38–43 and Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
| How heavy that duty is scales with volume and role, not with choosing Acquia. Under the CAC's March 2024 Regulations on Promoting and Regulating Cross-border Data Flows, a non-CIIO transferring fewer than 100,000 individuals' non-sensitive personal information in a calendar year is exempt from the security assessment, the standard contract and certification — above that threshold, or as a CIIO, a transfer mechanism or in-country storage applies. | CAC — Regulations on Promoting and Regulating Cross-border Data Flows, March 2024 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
Acquia is a managed Drupal cloud and digital experience platform (DXP): instead of running Drupal on a server of your own, you let Acquia host and operate it for you. That convenience is also what makes “does Acquia work in China” a sharper question than it first looks, because the one decision that governs the China answer — where the servers sit — is made for you, and Acquia’s own documentation puts those servers offshore.
Acquia Cloud runs on Amazon Web Services, and the regions Acquia lists span the United States, Europe and Asia Pacific — with none inside mainland China. For a mainland audience that single fact opens two compliance doors no amount of caching or theme work can close: the ICP filing a public site needs, and the data-residency rules that reach the personal data an Acquia-hosted site collects. Below is what Acquia documents about where it hosts, and how China’s own law treats each door — in Acquia’s words and China’s statutes, so you can take it to counsel rather than to a benchmark.
Acquia in China at a glance
| What decides it | In Acquia's own words — and China's own law |
|---|---|
| What Acquia is | Managed Drupal cloud hosting and a digital experience platform. Acquia runs your Drupal site for you, and its own documentation places that hosting on AWS regions across the United States, Europe and Asia Pacific. The hosting decision is made for you — and it lands offshore. |
| Is it blocked? | Not the useful question. Acquia-hosted pages are reachable from the mainland, but because the regions sit offshore, requests cross the border on every visit and third-party assets can fail on their own. That is a delivery matter, not what decides whether you may run the site for a Chinese audience. |
| Serving the public in China | A public site shown to mainland visitors needs an ICP filing (备案) tied to a licensed mainland host and a mainland legal entity (State Council Order 292, Article 4; MIIT Order 33). Acquia offers no mainland region, so there is no in-country host for the filing to attach to. |
| Content and data | User accounts, comments and contact or webform submissions are personal information, and on Acquia they live on offshore AWS. For visitors in China that is a cross-border transfer PIPL governs; a CIIO or large-volume handler must keep personal information collected in China inside the mainland. |
| The working design | Keep Acquia as your Drupal origin; add ICP-filed, in-country delivery in front of it for mainland visitors — and where the law requires, keep your users' data on Chinese soil. An overlay, not a re-platform. |
What Acquia actually is — managed Drupal hosting, and the hosting sits offshore
Acquia wraps enterprise hosting, support and DXP tooling around Drupal, and runs the result on Amazon Web Services. With plain self-hosted Drupal, “where you host it” is a choice you make; with Acquia Cloud, Acquia has already made that choice, and its published region list is the answer — the United States, Europe, Asia Pacific (Singapore and Sydney) and South America, with nothing inside mainland China.
That is why the familiar “is it blocked” framing misses the point. Reachability still matters at the edges — a site served from offshore can be slow for mainland visitors, and themes or modules that pull in third-party fonts, analytics or map libraries can load assets that are themselves degraded inside the mainland — but that is delivery, not what decides whether you may run an Acquia site for a Chinese audience. What decides that are the two doors below, and both of them turn on that offshore hosting location.
The first door: an ICP filing for a public mainland site
Serving a public website to people in mainland China turns on a permission that has nothing to do with Drupal’s code or Acquia’s tooling: an ICP filing (备案). Under State Council Order No. 292 (Article 4) and MIIT Order No. 33, that filing attaches to a hosting resource physically inside the mainland and to a mainland legal entity — and a site served from Acquia’s offshore regions has nothing in-country for it to bind to.
This is where Acquia differs from bare Drupal in a way that matters. With a self-hosted Drupal instance you could place the server on a licensed mainland host and make the same site filable; Acquia Cloud’s managed regions simply do not include a mainland one. So the compliant route is not to leave Acquia but to add ICP-filed, in-country delivery in front of your Acquia origin. The filing follows the in-country hosting, which is exactly the piece Acquia’s region list does not supply.
The second door: the personal data an Acquia site collects
An Acquia site rarely just displays pages. User accounts, comments, contact and webform submissions, and anything a commerce or membership module records all land in the Drupal database — and on Acquia that database lives on the offshore AWS regions above. For a mainland audience, that makes data residency the second door.
A visitor in China’s account details and form submissions are personal information. Hosted offshore, that personal information is being carried out of the mainland, which China’s Personal Information Protection Law governs as a cross-border transfer (Chapter III, Articles 38–43: notice, separate consent, and one permitted transfer mechanism — a CAC security assessment, the CAC standard contract, or certification). The weight scales with volume and role rather than with using Acquia at all: under the CAC’s March 2024 cross-border rules, a non-CIIO moving fewer than 100,000 individuals’ non-sensitive personal information in a calendar year is exempt from those mechanisms, while a CIIO or large-volume handler must keep personal information collected in China inside the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). Which of these applies to you is a question for counsel, so treat the specifics as a risk picture rather than a default.
Where 21YunBox fits — a compliant overlay, not a re-platform
You keep Acquia exactly as you run it today — same Drupal build, same modules, same themes, same deployment pipeline. What a mainland-China audience adds is the one thing Acquia’s offshore regions cannot supply: ICP-filed delivery from inside the mainland, placed in front of your existing Acquia origin, with a fixed in-country entry so each visitor’s real IP is not carried across the border. Our China team maps which obligations apply to your entity and the data your site holds, handles the ICP filing, and stands up the in-country entry — and where the law requires your users’ data to stay on Chinese soil, helps you keep that data in-country. No rebuild, no second codebase, no leaving Acquia.
Related reading:
Frequently Asked Questions
Is Acquia blocked in China?
No, and that is not the question that decides a mainland launch. Acquia-hosted pages are reachable from the mainland, but because Acquia Cloud's regions sit outside mainland China, requests cross the border on every visit and third-party assets can fail on their own — that is delivery, not a block. What actually decides whether you may run the site for a Chinese audience are two compliance doors: a public mainland site needs an ICP filing Acquia's offshore regions can't hold, and the personal data your site collects sits offshore under PIPL.
Where does Acquia host my Drupal site and its data?
On Amazon Web Services. Acquia's own documentation lists its regions as US East (Northern Virginia), US West (Oregon), EU West (Dublin), EU Central (Frankfurt), APAC (Singapore, Sydney) and South America (São Paulo) — none inside mainland China. So for a mainland audience your content and the personal data your site collects live offshore by default, which is what makes both the ICP and data-residency doors apply. Treat the specifics as a risk to confirm with counsel.
Can 21YunBox help make our Acquia site compliant in China?
Yes. Our China team can assess your ICP and data-residency exposure for your entity and the data your site holds, handle the ICP filing, and stand up ICP-filed, in-country delivery in front of your existing Acquia origin — and, where the law requires your users' data to stay on the mainland, help you keep that data in-country. You keep Acquia as your Drupal platform; there is no rebuild. Get in touch to work through your specific setup.
