Does EdgeDB (Gel) Work in China? Data Residency, PIPL & an Offshore Database
EdgeDB — renamed Gel in 2025 — is a Postgres-based database, and its hosted form, Gel Cloud, runs only in offshore AWS regions (US West, US East, EU West), none in mainland China. So your China users' data lives offshore and crosses the border on every read and write: a PIPL data-residency and cross-border-transfer question, not a speed one.
Does EdgeDB (Gel) work in China?
Whether you can use EdgeDB — now Gel — for a mainland-China audience is first a data-residency question, not a speed one. Gel is the database your application reads from and writes to, so where it keeps that data is what China's law responds to.
Gel's hosted form, Gel Cloud (formerly EdgeDB Cloud), runs on Amazon Web Services, and its own CLI reference names the only places an instance can live: "Possible values are aws-us-west-2, aws-us-east-2, and aws-eu-west-1" — US West, US East and EU West, with nothing in mainland China. So the personal data your China users generate is stored offshore and crosses the border on every read and write: a cross-border transfer PIPL governs, and for a CIIO or large-volume handler, a data-residency duty no offshore region can meet. The table below is Gel's own wording and the rules it triggers.
This is a risk picture, not a verdict — your obligations turn on what you store, your data volumes and your role. Our China team can map your Gel data-residency exposure with you →
Compliance snapshot
- ! Reachable from China, but this is your database of record — the personal data itself crosses the border on every read and write
- ✕ Gel Cloud runs only in offshore AWS regions — US West, US East, EU West — with none in mainland China
- ! Your China users' data stored in Gel Cloud sits offshore — a cross-border transfer PIPL governs
- ! CIIOs and large-volume handlers owe in-country storage that no offshore Gel region can meet
- ✓ A compliant, ICP-filed in-country path exists — set in front of your stack, no rebuild or migration
What EdgeDB's own documentation says about China
| Fact | Primary source |
|---|---|
| In Gel's own documentation: a Gel Cloud instance can be created only in a fixed set of regions — "Possible values are aws-us-west-2, aws-us-east-2, and aws-eu-west-1" — that is US West (Oregon), US East (Ohio) and EU West (Ireland), all on Amazon Web Services. No region is inside mainland China, so the database of record for your China users sits offshore. | Gel — CLI reference, gel instance create (--region), retrieved 2026-10-07 |
| A database is the system of record: every read pulls personal data out and every write puts it back, so an application or user connecting from inside mainland China to an offshore Gel Cloud endpoint exchanges personal information across the border continuously, not once. PIPL governs that cross-border transfer — the personal-information handler (you, Gel's customer, not Gel) must give notice, obtain separate consent, and satisfy one transfer mechanism: a CAC security assessment, the CAC standard contract, or certification. | PIPL Chapter III, Articles 38–43 |
| For a CIIO or large-volume handler, personal information collected in China must be stored inside mainland China (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). Gel Cloud publishes no mainland-China region, so the only way to keep your China users' data on Chinese soil is to run the database of record on infrastructure inside the mainland — which is where an ICP filing and in-country storage enter the picture. | PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
| The exposure scales with volume and role, not merely with using the database: under the CAC's March 2024 cross-border data rules, a non-CIIO transferring fewer than 100,000 individuals' non-sensitive personal information in a calendar year is exempt from the security assessment, standard contract and certification — above that, a transfer mechanism is required. | CAC — Regulations on Promoting and Regulating Cross-border Data Flows, March 2024 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the deciding question about EdgeDB — the database that was renamed Gel in 2025 — is not how quickly a query comes back. It is where your data is allowed to live. EdgeDB is a Postgres-based, object-relational database: the system of record your application reads from and writes to, holding whatever personal data your users generate. Its managed form, Gel Cloud (formerly EdgeDB Cloud), keeps that database only in offshore AWS regions, with none inside mainland China. The endpoint is reachable; what China’s law answers to is that the data — and every read and write of it — sits on the wrong side of the border.
EdgeDB (Gel) in China at a glance
| What decides it | Where EdgeDB (Gel) stands for China |
|---|---|
| What it is | EdgeDB — renamed Gel in 2025 — is a Postgres-based, object-relational database: the system of record holding your application's data, which routinely includes users' personal information. Where that data lives is the deciding question. |
| Where it runs | Gel Cloud, the managed service, runs on AWS only: “Possible values are aws-us-west-2, aws-us-east-2, and aws-eu-west-1” — US West, US East and EU West. No region is inside mainland China; the nearest is still offshore. (EdgeDB and Gel are also open source, so a team can self-host — but then you choose and own the location.) |
| Your data in Gel | Personal data your app stores for Chinese users sits offshore — a cross-border transfer PIPL governs — and it moves across the border on every read and write. |
| Data residency | For a CIIO or large-volume handler, personal information collected in China must stay on the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). No Gel Cloud region can meet that duty. |
| Is it reachable? | The endpoint is offshore, so reaching it from China is a delivery matter shaped by the cross-border path. Reachable or not, the data of record is offshore — and that is the compliance fact. |
Your system of record lives offshore
EdgeDB — now Gel — is where your application actually keeps its data. Its managed service, Gel Cloud (formerly EdgeDB Cloud), runs on Amazon Web Services, and Gel’s own CLI reference names the only regions an instance can occupy: “Possible values are aws-us-west-2, aws-us-east-2, and aws-eu-west-1” — US West, US East and EU West. Not one is inside mainland China, and the nearest is still outside it. That single geographic fact settles the China question before any query is ever timed: the data your China users generate is stored on the far side of the border. For a critical information infrastructure operator or a large-volume handler, personal information collected in China has to be kept on the mainland, and no offshore Gel Cloud region can satisfy that.
A database is not a CDN — the personal data itself moves
With a static file, what crosses the border is a copy of an asset. With a database, what crosses the border is the personal data itself: every query reads it out, every insert and update writes it back, and replicas and backups of it live offshore. So an application — or a user — connecting from inside mainland China to an offshore Gel Cloud endpoint is exchanging personal information across the border continuously, not once. Under China’s Personal Information Protection Law, both the offshore storage and that ongoing flow are a cross-border transfer, and the duty falls on you — the handler — not on Gel: notice, separate consent, and one cleared transfer mechanism. A faster round trip does not make the data resident; that is the part performance tuning cannot reach.
Self-hosted or managed, location is still the compliance fact
EdgeDB and Gel are open source, so a team can also run the database itself rather than on Gel Cloud. That changes who picks the location, but not the test: wherever the system of record sits, the personal data it holds for your China users is governed by where it is stored. Gel Cloud — the managed path most teams take — publishes no mainland-China region at all, so on it the data is offshore by default. Whether that offshore endpoint answers quickly or slowly from China is a delivery matter, independent of all this; even an instant response still leaves the data outside the mainland. Running the database of record lawfully on infrastructure inside China is exactly the in-country footing that is hard to stand up, and doing it for a public service is where an ICP filing and in-country storage enter the picture. Treat this as a risk map, not a verdict: whether you face a localization duty, a transfer-mechanism obligation, or both turns on what you store, 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 on EdgeDB — Gel. We add the piece a database with no mainland presence cannot: compliant, ICP-filed storage and delivery from inside the mainland, set in front of the stack you already run — no rebuild, no second codebase, and no move off Gel. Our China team maps your cross-border and data-residency obligations against your entity and data volumes, then, where the law requires your China users’ data to stay on Chinese soil, stands up the in-country storage and delivery a lawful China presence needs — while your application keeps running exactly where it is.
Related reading:
Frequently Asked Questions
Does EdgeDB (Gel) store Chinese users' data in China?
No. Gel's hosted service, Gel Cloud, runs only on offshore AWS regions — its own CLI reference lists US West, US East and EU West as the possible region values, with none in mainland China. So the personal data your application stores for China users is held offshore, not on Chinese soil.
Is it illegal to use EdgeDB or Gel for a China-facing app?
Not in itself. The issue is the cross-border transfer of personal information, which PIPL allows if you give notice, obtain separate consent and meet one transfer mechanism. Whether you also owe in-country storage depends on your role — for example whether you are a critical information infrastructure operator — and how much personal data you handle. Treat it as a risk to settle with counsel, not a blanket ban.
Can 21YunBox help make our EdgeDB (Gel) setup compliant in China?
Yes. Our China team can assess your cross-border and data-residency exposure for your data volumes and role, then stand up compliant, ICP-filed in-country delivery — and, where the law requires your China users' data to stay on the mainland, in-country storage — in front of the stack you already run. Get in touch to work through your specific case.
