Platform
Regions
Where your data physically lives.
| ID | Location | Status | Notes |
|---|---|---|---|
pl-waw-1 | Warsaw, Poland | Available | Azure Poland Central. Database, files, backups and logs stay in Poland (off-site backup copies in Azure Poland Central). |
eu-north-1 | Stockholm, Sweden | Available | Azure Sweden Central. Nordic markets and a second EU location, ~20 ms from Poland. |
eu-central-1 | Frankfurt, Germany | Coming soon | DACH market |
eu-west-1 | Amsterdam, Netherlands | Coming soon | Benelux, UK |
us-east-1 | Virginia, USA | Coming soon | North America |
Current availability (and free capacity) is shown when you pick a region in the New project form. A region without free capacity is temporarily disabled while we add another server.
How it works
Every region is one or more database servers. A project gets its own isolated stack of Supabase services on a server in the chosen region. The project's API is always at https://<ref>.host.ulewicz.space and Postgres at db-<ref>.host.ulewicz.space:5432 (TLS) — regardless of region.
- Routing: the control plane knows which server runs each project and routes every operation there. For projects outside Warsaw we create DNS records for
<ref>,db-<ref>,cache-<ref>andsearch-<ref>pointing at that server (TTL 60 s). - Certificates: every server has the same wildcard certificate for
*.host.ulewicz.space, so URLs and keys don't depend on the region. - Choose the region closest to your users and your application server — latency between backend and database matters most.
- You can move a project to another region later, keeping its URL and keys.
API and MCP
When creating a project through the Management API or MCP, pass region (e.g. "eu-north-1"). An unavailable region returns 422; no capacity returns 503 with a description.