Does Fauna Work in China? End-of-Service, Data Residency & PIPL
Fauna has sunset its managed database — end of service was May 30, 2025 — so a China-facing app on it must migrate regardless. And while it ran, Fauna stored your records only in offshore US, Europe and Global regions, with no mainland-China region, making China a PIPL cross-border transfer. A compliance-first look.
Does Fauna work in China?
No — and two things point the same way. Fauna has sunset its managed database, so any China-facing app still on it has to migrate regardless; and while it ran, it kept your records — your Chinese users' personal information among them — only in offshore regions, which makes serving the mainland a cross-border transfer under PIPL.
Fauna announced in 2025 that it would sunset its managed database service — the managed service was turned off on May 30, 2025, with accounts and their data set for permanent deletion. Fauna described itself as a "transactional database delivered as a secure, scalable, web-native API," and it ran only in United States, Europe and Global region groups, none inside mainland China. A database holds the personal information your application collects, so serving Chinese users from it leaves that data offshore — a cross-border transfer PIPL governs (notice, separate consent, a transfer mechanism) — while the ICP filing a public site needs attaches to the app in front of the database, not to Fauna. The table below pairs Fauna's own words with the rule each one triggers.
This is a risk map, not a verdict — whether your move off Fauna also triggers an ICP filing, in-country storage, or a PIPL transfer mechanism turns on your entity, your data and your users. Our China team can map your exposure with you →
What Fauna's own documentation says about China
| Fact | Primary source |
|---|---|
| Fauna has sunset its managed database service. In the announcement that opened its wind-down, Fauna announced it would sunset the managed database service; the service was turned off on May 30, 2025, and Fauna stated accounts and their associated data would be permanently deleted afterward. A platform that is shutting down is a migration you cannot defer — a China-facing app on Fauna has to move no matter how its ICP and data questions resolve. | Fauna — "The Future of Fauna" sunset announcement and End of Life FAQ (fauna.com); end of service May 30, 2025 |
| Fauna ran no region inside mainland China. Its documentation offered three region groups — United States, Europe and Global — with database replicas only in the US and Europe, and each database pinned to a single group. There was no mainland-China region and no production Asia replica, so a China-facing app stored its users' records offshore by design — the starting point for a cross-border transfer of personal information under PIPL (Articles 38–43). | Fauna Docs — Region groups (docs.fauna.com) |
| Fauna is a database, so the sharp edge is data residency, not reachability. Fauna describes itself as a "transactional database delivered as a secure, scalable, web-native API" — it stores the personal information your application collects. Serve Chinese users from an offshore region and that storage is a cross-border transfer PIPL governs: the handler (you, not Fauna) must give notice, obtain separate consent and satisfy a transfer mechanism (Articles 38–43), and for a CIIO or large-volume handler the data must be stored inside the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). | Fauna (github.com/fauna), retrieved 2026-10-07; PIPL Articles 38–43 & 40; Cybersecurity Law Article 39 (formerly Article 37) |
| The ICP filing belongs to the app in front of the database — not to Fauna. A database is not the public-facing site that gets filed; a China ICP filing (ICP 备案, under State Council Order No. 292 and MIIT Order No. 33) attaches to the mainland-hosted website or service your users actually reach. With no mainland region, Fauna gave that app no in-country footing to file against — so the filing obligation sat with your application all along, and an offshore database left it nothing in the mainland to anchor to. | State Council Order No. 292; MIIT Order No. 33 — China's ICP regime |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the question about Fauna is not how quickly it answers a query — it is whether you may keep your users’ data where Fauna kept it, and whether Fauna will be there at all. Both answers push the same way. Fauna has announced the end of its managed service, so a China-facing app built on it faces a migration no matter what; and while the service ran, it stored your records only in offshore regions, which turns serving Chinese users into a cross-border transfer of personal data under China’s law. Reachability was never the hard part here — the licensing of your data’s home is.
Fauna in China at a glance
| What decides it | In Fauna's own terms |
|---|---|
| Is it still available? | No. Fauna announced it would “sunset the Fauna service”; the managed service was turned off on May 30, 2025, and accounts and their data were set for permanent deletion. A China-facing app on Fauna has to move regardless. |
| What it is | A “transactional database delivered as a secure, scalable, web-native API” — it holds your application's records, not a public website that gets ICP-filed. |
| Where it ran | Three region groups — United States, Europe and Global — with replicas only in the US and Europe, each database pinned to a single group. No region inside mainland China; no production Asia replica. |
| Your China users' data | Stored in those offshore regions — a cross-border transfer of personal information PIPL governs. For a CIIO or large-volume handler, China data must stay in the mainland, which an offshore database cannot do. |
| Where ICP sits | On the public app or site in front of the database, under State Council Order No. 292 and MIIT Order No. 33 — not on Fauna, which gave that app no mainland footing. |
A database that is winding down — migration comes first
Before any China question, there is a plainer one: will Fauna still be here? Its own answer is no. In the announcement that opened its wind-down, Fauna wrote that “after careful consideration, we have made the hard decision to sunset the Fauna service over the next several months” — the managed service was turned off on May 30, 2025, and Fauna said accounts and their associated data would be permanently deleted after the cutoff. Whatever you concluded about PIPL or ICP, an application built on Fauna now has to move to another database. That makes migration the first fact of this page, not a footnote to it: the only open choice is where your records live next, and whether that destination is one you can lawfully operate from in mainland China.
No mainland region, so your China users’ data lived offshore
While it ran, Fauna stored data in three region groups — United States, Europe and Global — with replicas only in the US and Europe and each database pinned to a single group. None sat inside mainland China, and the Southeast-Asia location that once appeared on its map never became a live production replica. For a mainland audience, that geography is the exposure. A database holds the personal information your application collects, so serving Chinese users from an offshore Fauna region made that storage a cross-border transfer under China’s Personal Information Protection Law: the handler — you, not Fauna — 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 no offshore region can satisfy.
Where ICP actually sits — on the app, not the database
It is tempting to ask whether Fauna itself could be “ICP-filed.” It could not, and that is the wrong place to look. An ICP filing (ICP 备案, under State Council Order No. 292 and MIIT Order No. 33) attaches to the public-facing website or service your users reach from inside China, hosted on a mainland resource — not to the database sitting behind it. Fauna, with no mainland region, simply gave that public app no in-country footing to file against. So the ICP obligation never belonged to Fauna; it belonged to your application, and an offshore database left it with nothing in the mainland to anchor to. That distinction matters as you choose what comes next: the thing you file is the origin your visitors actually hit, and it has to live where the filing can.
This is a risk map, not a verdict: whether your move off Fauna triggers an ICP filing, in-country storage, a PIPL transfer mechanism, or all three depends on what you serve, how much personal data you hold, and who your users are — worth settling with counsel before you rebuild.
Where 21YunBox fits — a compliant overlay, not a migration
Fauna is going away, so some migration is already on your roadmap — but the hard part of a China launch was never swapping one database for another. It is being cleared to serve the mainland at all: an ICP-filed origin inside China and a lawful home for your users’ data. That is the piece we add. Wherever your records land next, 21YunBox places compliant, ICP-filed delivery from inside the mainland in front of your existing origin — no rebuild, no second codebase, and no re-architecting onto a China-only stack. Our China team maps your PIPL cross-border and data-residency obligations against your entity, your data volumes and your users, then stands up the in-country delivery and storage a lawful China presence needs, while the application you choose stays exactly where you run it.
Related reading:
