Does Replit Work in China? ICP, Offshore Hosting & Google-Cloud Dependencies
Replit runs on Google Cloud with no region inside mainland China — published apps are hosted in the US (the EU for enterprise), so a China-facing Replit app is served offshore with no ICP-filing path, your app and user data land outside the mainland under PIPL, and Replit's reliance on Google Cloud and Google services adds a reachability risk on top. A compliance-first look at the two doors.
Does Replit work in China?
Whether Replit works for a mainland-China audience is first a licensing and data-residency question, not a speed one. Replit's editor is reachable from inside China — the risk is where your published app runs, what it stores, and the Google services it leans on.
Replit publishes to Google Cloud: by its own documentation every published app is hosted in the United States, with the European Union available to enterprise customers, and its geography list (North America, Europe, Asia, South America, Australia) has no region inside mainland China. So an app served to mainland visitors from Replit reaches them from offshore, with no ICP-filing path on Replit itself; any personal data it holds for Chinese users is a cross-border transfer PIPL governs; and because the stack rides on Google Cloud and Google services, its reachability inside China cannot be assumed. The table below is Replit's own setup and the China rules it triggers — plus the compliant, ICP-filed in-country path.
This is a risk map, not a legal verdict — your obligations turn on what you serve and what you store. Our China team can map the ICP and data-residency path with you →
What Replit's own documentation says about China
| Fact | Primary source |
|---|---|
| In Replit's own documentation, "Replit's infrastructure is backed by Google Cloud Platform (GCP). All published apps are hosted in the United States. Enterprise customers can contact sales to request their published apps to be hosted in the European Union instead." Each customer gets a "dedicated, single-tenant GCP project" for published apps, and Replit's geography options — North America, Europe, Asia, South America and Australia — include no region inside mainland China. The nearest, Asia, is still offshore to the mainland, and both the Google Cloud hosting and the Google services Replit depends on are offshore dependencies whose reachability inside China cannot be assumed. | Replit Docs — Publishing and Geography, retrieved 2026-10-07 |
| Serving a public website or app to mainland-China visitors from inside the mainland requires an ICP filing (ICP 备案) under the State Council's Order No. 292 and MIIT's Order No. 33, and the filing is tied to a mainland hosting resource. Because Replit operates no mainland-China region, a Replit-hosted app has no ICP-filing path on Replit itself — it is reaching China from offshore. | PRC Regulations on Telecommunications (State Council Order No. 292); Administrative Measures for the Filing of Non-operational Internet Information Services (MIIT Order No. 33) |
| If your Replit app holds Chinese users' personal data, that data sits offshore (the United States, the EU, or another Replit geography), so PIPL requires the handler to give notice, obtain separate consent, and meet a transfer mechanism (a CAC security assessment, the CAC standard contract, or certification). For a CIIO or large-volume handler, personal information collected in China must be stored in mainland China (PIPL Article 40; CSL Article 37) — which Replit's offshore regions cannot satisfy. | PIPL Chapter III, Articles 38–43 and Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the first question about Replit is not how quickly the editor loads — it is whether an app you publish on it can be operated there lawfully, and where the data behind it is allowed to live. Replit answers the location part in its own documentation: every published app runs on Google Cloud, hosted in the United States, with the European Union available to enterprise customers — and no region inside mainland China. That makes a China-facing Replit app reachable but entirely offshore, which leaves it with no footing for the ICP filing a public mainland site requires, and turns any personal data it holds for Chinese users into a cross-border transfer China’s law governs. On top of both, the Google Cloud and Google services Replit is built on are themselves dependencies whose reachability inside China cannot be assumed.
Replit in China at a glance
| What decides it | In Replit's own terms |
|---|---|
| Where it runs | Published apps run on Google Cloud, hosted in the United States, with the EU available to enterprise customers. Replit's geography options are North America, Europe, Asia, South America and Australia — none inside mainland China, and the nearest, Asia, is still offshore. |
| Who runs the infrastructure | Replit's infrastructure is “backed by Google Cloud Platform (GCP),” and each customer gets a “dedicated, single-tenant GCP project” for published apps — compute, storage and secrets all sit on Google Cloud. |
| Serving the public | A site or app served to mainland visitors from inside China needs an ICP filing tied to a mainland hosting resource. With no mainland region, Replit offers no ICP-filing path of its own. |
| Your app and user data | Personal data your Replit app holds for Chinese users sits offshore — a cross-border transfer PIPL governs, plus a data-localization duty for CIIOs and large-volume handlers that offshore regions cannot meet. |
| Delivery dependency | The stack rides on Google Cloud and commonly reaches for Google services; their reachability inside mainland China cannot be assumed, so an app can be offshore for compliance and fragile for delivery at the same time. |
No mainland region on Google Cloud, so no footing for an ICP filing
Every app you publish on Replit runs on Google Cloud. In Replit’s own words, “Replit’s infrastructure is backed by Google Cloud Platform (GCP). All published apps are hosted in the United States,” with the European Union available to enterprise customers and geography choices spanning North America, Europe, Asia, South America and Australia — not one of them inside mainland China, and the nearest, Asia, still outside it.
That geography settles the licensing question before performance ever enters it. A public-facing site or app 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 must attach to a hosting resource physically located in the mainland. Replit has none, so there is simply nothing on Replit to file against. That is where “we already deploy on Replit” runs out: reaching China is not the same as being cleared to operate there, and picking a different Replit geography only moves the app between offshore regions — it never creates the mainland footing a filing needs.
Your China users’ app data stays offshore
Publish a China-facing app on Replit and the personal information it collects lives in the United States, the EU, or whichever offshore geography you select — never the mainland. Under China’s Personal Information Protection Law that is a cross-border transfer, and the handler — you, not Replit — has to give notice, obtain separate consent, and clear one transfer mechanism: a CAC security assessment, the CAC standard contract, or certification. 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 Replit’s regions can satisfy, because every one of them sits on Google Cloud outside China.
Built on Google Cloud and Google services — a reachability risk stacked on the compliance one
The two doors above are compliance facts. Replit adds a third, practical consideration that is not about licensing at all: the platform is built on Google Cloud, and Replit-generated apps commonly reach for Google-hosted services and libraries. Google properties have a long, widely reported record of unreliable reachability inside mainland China, and running on Google Cloud does nothing to change that. We publish no first-party measurement for Replit, so we put no number on it here — but the direction is clear enough to plan around: an app can be offshore for compliance and fragile for delivery at the same time when its runtime, storage, and front-end dependencies all trace back to Google. Which of your app’s dependencies actually load from inside China is worth testing against your real build before you commit.
This is a risk map, not a verdict: whether you need an ICP filing, in-country storage, or both — and how exposed your Google dependencies leave you — depends on what you serve, how much personal data you hold, and who your users are. Worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep building and publishing on Replit. We add the one piece a platform with no mainland presence cannot: compliant, ICP-filed in-country delivery set in front of your Replit-hosted app — no rebuild, no second codebase, and no move off Replit. Our China team maps your ICP and data-residency obligations against your entity and data volumes, then stands up the in-country delivery a lawful China presence needs, while your app keeps running exactly where Replit puts it.
Related reading:
