Does CoreMedia Work in China? Offshore Cloud Hosting, Data Residency & ICP
CoreMedia Content Cloud is a CoreMedia-hosted DXP on public-cloud data centers (Amazon Web Services is the example it names), and its service description names no mainland-China region — so your content and rich-media assets are served from offshore, any personal data in them sits outside the mainland under PIPL, and the public site still needs an ICP filing. A compliance-first look at where your content lives and who files for the site.
Does CoreMedia work in China?
Whether you can use CoreMedia in mainland China is first a data-residency and delivery question, not a speed one. CoreMedia Content Cloud is a CoreMedia-hosted digital experience platform that keeps your content and rich-media assets — and any personal data your models hold — and serves them to the audiences you build for. Where it keeps and delivers them is what China's law responds to.
In its own platform service description CoreMedia deploys the service to “data centers operated by public cloud vendors (such as Amazon Web Services),” and “the Subscriber has to choose a Geographic Region” at subscription — but “The information of the regions that CoreMedia supports will be provided upon Subscriber's request,” so the supported-region list is not published and no mainland-China region is named. By default, then, your content and the personal data around it are held offshore — a cross-border transfer of personal information PIPL governs — and the ICP filing lands on the public mainland site you serve, not on CoreMedia. The table below is CoreMedia's own wording and the rule each line triggers.
This is a risk picture, not a verdict — what applies turns on the region you can actually get, what your content holds, and who your users are. Our China team can map your CoreMedia exposure with you →
What CoreMedia's own documentation says about China
| Fact | Primary source |
|---|---|
| CoreMedia Content Cloud is a CoreMedia-hosted service running on third-party public cloud. Its own platform service description says the service is deployed to “data centers operated by public cloud vendors (such as Amazon Web Services),” and that “These data centers are operated in alignment with the Tier III+ guidelines (as per the Uptime Institute classification).” So your content and rich-media assets live on public-cloud infrastructure CoreMedia operates for you — not, by default, on the mainland. | CoreMedia — Content Cloud Platform Service Description, §2.4.2 Data Centers (coremedia.com), retrieved 2026-10-08 |
| You choose a region at subscription, but the list of regions isn't published. CoreMedia states “the Subscriber has to choose a Geographic Region that the CoreMedia Content Cloud - Service will be deployed to,” and that “The information of the regions that CoreMedia supports will be provided upon Subscriber's request.” No mainland-China region is named anywhere in the service description — the only production zones it names publicly are in Western Europe and South America — so whether an in-country region is even on offer is something you have to confirm with CoreMedia before you build. | CoreMedia — Content Cloud Platform Service Description, §2.4.2 Data Centers (coremedia.com), retrieved 2026-10-08 |
| What CoreMedia stores for you sits in that chosen offshore region. By its service description CoreMedia keeps “all user-managed non-binary content and content workflow state in a relational database,” binary content such as “images, videos etc.” in a relational database or cloud storage, and “some collaborative content metadata in a NoSQL database.” Content models, asset metadata and editorial or contact records routinely carry names, email addresses and the images of identifiable people — so the personal data wrapped around your content is held wherever that region is. | CoreMedia — Content Cloud Platform Service Description, §2.4.3 Backup & Restore (coremedia.com), retrieved 2026-10-08 |
| Personal data gathered in China and held offshore is a cross-border transfer PIPL governs. The handler — you, CoreMedia's customer, not CoreMedia — must give notice, obtain separate consent, and satisfy one transfer mechanism (a CAC security assessment, the CAC standard contract, or certification). For 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 offshore region cannot meet. | PIPL Chapter III, Articles 38–43 and Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
| The ICP filing attaches to your public site, not to CoreMedia. A public-facing website served to mainland visitors from inside China turns on an ICP filing (ICP 备案) under State Council Order No. 292 and MIIT Order No. 33, tied to a hosting resource physically inside the mainland. Because CoreMedia names no mainland-China region, it gives that site no in-country footing to file against — reaching CoreMedia from Shanghai is not the same as being licensed to operate there. | PRC Regulations on Telecommunications (State Council Order No. 292); Administrative Measures for the Filing of Non-operational Internet Information Services (MIIT Order No. 33) |
Sources verified by the 21YunBox compliance team on 2026-10-08.
For a mainland-China audience, the deciding question about CoreMedia is not how quickly a hero image paints — it is where your content and rich-media assets are allowed to live, where the personal data around them ends up, and whether the site that serves them can be licensed to operate. CoreMedia Content Cloud is a digital experience platform CoreMedia hosts for you, and it answers those questions in its own service description: the service runs on public-cloud data centers, and the list of regions it supports is not published. A China-facing site built on it is reachable, but its content is delivered from offshore, its users’ data is held offshore, and the public site in front of it still needs an ICP filing CoreMedia gives it no footing for. The reachability is real; the residency and the licensing are the exposure.
CoreMedia in China at a glance
| What decides it | In CoreMedia's own terms |
|---|---|
| Where it runs | A CoreMedia-hosted service deployed to “data centers operated by public cloud vendors (such as Amazon Web Services),” run to “Tier III+ guidelines (as per the Uptime Institute classification).” Public-cloud infrastructure CoreMedia operates for you — not, by default, on the mainland. |
| Which region | “The Subscriber has to choose a Geographic Region” at subscription, and “The information of the regions that CoreMedia supports will be provided upon Subscriber's request.” The supported-region list is not published, and no mainland-China region is named. |
| What it stores | Content and workflow state in a relational database, binary assets such as “images, videos etc.” in a relational database or cloud storage, collaborative metadata in a NoSQL store — all within the chosen offshore region, together with the personal data your content carries. |
| The ICP question | A public mainland site served from inside China turns on an ICP filing tied to an in-country host. CoreMedia names no mainland region, so it offers that site no footing of its own to file against. |
| Is it reachable? | Yes — instances are “connected to the internet via the public cloud provider's global internet backbone.” The exposure is not a block; it is where the content, the data and the filing sit. |
A CoreMedia-hosted service on public cloud, offshore by default
CoreMedia Content Cloud is not something you run in your own data center — it is a service CoreMedia operates for you. In its platform service description the service is deployed to “data centers operated by public cloud vendors (such as Amazon Web Services),” run to “Tier III+ guidelines (as per the Uptime Institute classification),” and each instance is “connected to the internet via the public cloud provider’s global internet backbone.” For a China-facing audience that settles the starting point before performance ever enters it: the platform your content lives on is public-cloud infrastructure, and a mainland visitor reaches it across the border. (CoreMedia also supports self-managed deployments; there the residency choice is yours to make, but the two China doors below are unchanged.)
The region list isn’t published — so residency is the first thing to settle
Where exactly your instance sits is a choice made once, at subscription: “the Subscriber has to choose a Geographic Region that the CoreMedia Content Cloud - Service will be deployed to.” But CoreMedia does not publish which regions are on offer — “The information of the regions that CoreMedia supports will be provided upon Subscriber’s request.” No mainland-China region is named anywhere in the service description, and the only production zones it names publicly are in Western Europe and South America. So for a China deployment you cannot assume an in-country region exists — you have to ask CoreMedia, and treat the answer as a data-residency fact to confirm before you build, not after.
Your content, assets and the data around them stay offshore
By its service description CoreMedia keeps “all user-managed non-binary content and content workflow state in a relational database,” binary content such as “images, videos etc.” in a relational database or cloud storage, and “some collaborative content metadata in a NoSQL database” — all within the Geographic Region you were given. A digital experience platform’s content models, asset metadata and editorial or contact records routinely carry names, email addresses and the images of identifiable people. Gathered from people in China and held in an offshore region, that is a cross-border transfer of personal information under China’s Personal Information Protection Law: the handler — you, CoreMedia’s customer, not CoreMedia — has to give notice, obtain separate consent, and clear one transfer mechanism (a CAC security assessment, the CAC standard contract, or certification). For 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 offshore region cannot meet, and one you cannot be sure CoreMedia can place in-country without asking.
Who gets ICP-filed — your site, not the platform
Because CoreMedia is the platform your public site is built on and served through, the licensing question does not attach to it the way it attaches to a host of record. It attaches to the public-facing site you deliver to mainland visitors. Put that site in front of people inside China and an ICP filing (ICP 备案) switches on under State Council Order No. 292 and MIIT Order No. 33, and the filing has to attach to a hosting resource physically located in the mainland. CoreMedia names no mainland region, so there is nothing on CoreMedia to file against — the filing is yours to arrange for the site you run on it. “We already run on CoreMedia” does not carry the site into China: calling an offshore platform from Shanghai is not the same as being cleared to operate a public site there.
This is a risk map rather than a verdict: whether an ICP filing, in-country storage for the personal data in your content, or both apply to you depends on what you publish, the region CoreMedia can actually give you, the volume of personal information you handle, and who your users are — settle it with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep shipping on CoreMedia, and your content, assets and region settings stay as they are. We supply the one piece a CoreMedia-hosted platform with no named mainland region leaves to you: compliant, ICP-filed delivery from inside the mainland, set in front of the site you already run — no rebuild, no parallel codebase, and no move off CoreMedia. Our China team weighs your ICP and PIPL data-residency obligations against your entity and the personal data your content holds, then stands up the in-country delivery — and, where the law demands it, the in-country storage — a lawful China presence requires, while your CoreMedia deployment stays exactly where it is.
Related reading:
