Does Fly.io Work in China? ICP, Data Residency & an Offshore Host
Fly.io publishes no region inside mainland China — it runs your app in its own datacenters abroad, nearest Tokyo and Singapore — so a China-facing site is served offshore with no ICP-filing path, and your users' data lands outside the mainland under PIPL. A compliance-first look at the offshore-host question.
Does Fly.io work in China?
No — not in the way mainland China requires. Fly.io will gladly run your app, but every region it publishes sits outside the mainland, so a China-facing Fly.io site is reachable yet wholly offshore: there is no hosting resource to anchor an ICP filing, and your users' data is stored abroad.
Fly.io describes itself plainly — it "runs applications physically close to users: in datacenters around the world, on servers we run ourselves" — and the regions it publishes reach Tokyo and Singapore but stop short of mainland China. That geography settles the licensing before speed is ever discussed: a public site served to mainland visitors needs an ICP filing bound to a hosting resource inside China, and Fly.io has none to file against. Keep serving China from an offshore Fly region and your users' personal information lives abroad — a cross-border transfer PIPL governs. The table below is Fly.io's own wording and the rule each gap 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
- ✕ Fly.io publishes no region inside mainland China
- ✕ A public site served offshore can't hold an ICP filing
- ! China visitors' personal data lands offshore — PIPL governs it
- ! CIIO or high-volume? In-country storage can't be met on an offshore region
- ✓ Reachable, and a solid global origin to keep behind in-country delivery
What Fly.io's own documentation says about China
| Fact | Primary source |
|---|---|
Fly.io runs your app on its own servers worldwide — none of them in mainland China. In its own words, Fly.io "runs applications physically close to users: in datacenters around the world, on servers we run ourselves," and the regions it publishes reach Tokyo (nrt) and Singapore (sin) but include no location inside the mainland. The footprint is fixed to Fly.io's own datacenters — there is no mainland region to deploy into. | Fly.io Docs — Regions (docs.fly.io/reference/regions), retrieved 2026-10-07 |
| No mainland region means no footing for an ICP filing. 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, and that filing must attach to a hosting resource physically located in the mainland. Fly.io publishes none, so there is nothing on Fly.io to file against — "we already run on Fly.io" does not carry into China. | Fly.io Docs — Regions (docs.fly.io/reference/regions), retrieved 2026-10-07; State Council Order No. 292; MIIT Order No. 33 |
| Your China users' personal data sits wherever your Fly region sits — offshore. Deploy to the nearest Fly.io regions and your users' personal information is stored in Tokyo or Singapore, outside the mainland: a cross-border transfer under PIPL that requires notice, separate consent and a transfer mechanism (Articles 38–43). 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 duty no offshore Fly region can meet. | Fly.io Docs — Regions (docs.fly.io/reference/regions), retrieved 2026-10-07; PIPL Articles 38–43 & 40; Cybersecurity Law Article 39 (formerly Article 37) |
| What's left is a delivery question, not a licensing one. Because Fly.io runs "in datacenters around the world, on servers we run ourselves," a China-facing Fly app is reached across the border from the nearest offshore region — a matter of distance and routing that varies, not a systematic block. But reachability was never what decides whether you may operate in the mainland: the ICP filing and in-country data residency are, and an offshore origin satisfies neither. | Fly.io Docs — Regions (docs.fly.io/reference/regions), retrieved 2026-10-07 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the deciding question about Fly.io is not how quickly it serves a page — it is where your application is allowed to run and where your users’ data is allowed to live. Fly.io answers the first in its own documentation: it runs apps in its own datacenters around the world, and not one of those datacenters is inside mainland China. A China-facing app on Fly.io is therefore reachable but wholly offshore, which leaves it with no hosting resource to anchor an ICP filing and turns the personal data you hold for Chinese users into a cross-border transfer China’s law governs. The reachability is genuine; the licensing and the data residency are the exposure.
Fly.io in China at a glance
| What decides it | In Fly.io's own terms |
|---|---|
| Where it runs | Fly.io “runs applications… in datacenters around the world, on servers we run ourselves.” Its published regions reach Tokyo (nrt) and Singapore (sin), but none is inside mainland China; the nearest are still offshore. |
| A mainland region | There is none to deploy into. The footprint is fixed to Fly.io's own datacenters, so you cannot add a mainland location of the kind an ICP filing has to attach to. |
| 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, Fly.io offers no ICP-filing path of its own. |
| Your data on Fly.io | Personal data of Chinese users runs in whichever offshore region you deploy to — a cross-border transfer PIPL governs, plus an in-country storage duty for CIIOs and large-volume handlers that offshore regions cannot meet. |
| Is it reachable? | Yes — as any offshore origin is. Reaching it from the mainland is a delivery question of distance and routing, not a block. |
No mainland region, so nothing to anchor an ICP filing
Fly.io runs your application on its own servers, in its own datacenters — and it tells you where. In its Regions reference it “runs applications physically close to users: in datacenters around the world, on servers we run ourselves,” and the published list reaches Tokyo (nrt) and Singapore (sin) in the Asia-Pacific, alongside regions across Europe, the Americas and Australia. Not one of them is in mainland China, and the closest — Tokyo and Singapore — are still outside it.
That geography settles the licensing question before performance ever enters it. 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 must attach to a hosting resource physically located in the mainland. Fly.io has none, so there is simply nothing on Fly.io to file against. That is where “we already ship on Fly.io” runs out: reaching China is not the same as being cleared to operate there, and choosing a region nearer the coast does not create the mainland footing a filing needs.
Your China users’ data stays offshore
Serve China from Fly.io and your users’ personal information lives wherever your region does — Tokyo, Singapore, Frankfurt, a US city — but always outside the mainland. Under China’s Personal Information Protection Law that is a cross-border transfer, and the handler — you, not Fly.io — 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 no offshore Fly region can satisfy.
Reachable, not cleared — which is the whole point
Fly.io is a global application host, not a service the mainland systematically blocks, so reaching an offshore Fly app from inside China is a delivery question — distance, routing, the occasional slow paint — that varies, rather than a wall. But reachability was never the question that decides whether you may operate there. A China-facing Fly.io site can load perfectly and still have no ICP filing and no in-country data residency, because those are licensing and data-location facts, not network ones. No amount of region selection or tuning closes them; they are closed only by putting a compliant, mainland-based layer in the path.
This is a risk map, not a verdict — whether an ICP filing, in-country storage, or both apply to you depends on what you publish, the volume of personal data you handle, and who your users are, and it is worth settling with counsel before you build on it.
Where 21YunBox fits — a compliant overlay, not a migration
You keep shipping on Fly.io. We add the one piece a host with no mainland footprint cannot: compliant, ICP-filed delivery from inside the mainland, set in front of your existing Fly.io origin — no rebuild, no second codebase, and no move off Fly. Our China team maps your ICP and data-residency obligations against your entity and data volumes, then stands up the in-country delivery and storage a lawful China presence needs, while your application keeps running in the Fly regions you already deploy to. Fly.io stays your origin; the compliant mainland layer sits in front of it.
Related reading:
Frequently Asked Questions
Does our existing Fly.io app work for users in mainland China?
It will load — Fly.io is a global host and nothing about it is systematically blocked — but "works" in the mainland is a compliance question, and there it falls short on two counts. Fly.io publishes no region inside mainland China, so a public site served from an offshore Fly region has no hosting resource to attach an ICP filing to, and your China users' personal data is stored abroad, which PIPL treats as a cross-border transfer. Reaching China is not the same as being cleared to operate there.
Can we just deploy to Fly.io's nearest region to China?
The nearest Fly.io regions — Tokyo and Singapore — are still outside mainland China, and that is what the rules turn on. An ICP filing must attach to a hosting resource physically inside the mainland, and data-localization duties require personal information collected in China to stay in the mainland; an offshore region, however close, meets neither. Proximity improves the network path, not the legal position.
Can 21YunBox help make our Fly.io app work in China?
Yes. You keep running your app on Fly.io exactly as you do now, and our China team adds the piece Fly.io cannot: ICP-filed, in-country delivery in front of your existing Fly origin, with no rebuild and no second codebase. We assess your PIPL cross-border and data-residency exposure for your entity, data volumes and users, then stand up the compliant mainland presence a lawful China operation needs. Get in touch to work through your case.
