Regions
A region is the geographic location where your compute and data live. PandaStack keeps this simple today: there is one region, it is chosen for you, and the CDN edge is global regardless.
Supported regions
Section titled “Supported regions”| Region | Status | Notes |
|---|---|---|
us | Available (default) | The only region today. The deploy pipeline uses the underlying zone us-central1. |
us is the value stored on projects, databases, and cronjobs. Internally the deploy wire falls back
to us-central1 when a project is created without an explicit region.
How a region is chosen
Section titled “How a region is chosen”You do not pick a region in the UI. It is applied server-side with us as the default:
- Container / project create defaults the region to
us(there is no region field in the create form); the deploy wire falls back tous-central1. - Databases default their region to
us. - Cronjobs default their region to
us.
Because there is a single region, every workload for every organization currently runs in us.
If you have a data-residency or multi-region requirement, note that only us exists today. New
regions would add values to this list; this page is the source of truth for what is live.
Regional vs. global
Section titled “Regional vs. global”Not everything is tied to a region. The distinction matters for latency and for where your data physically sits.
| Layer | Scope | What it means |
|---|---|---|
| CDN edge (static sites) | Global | A static project is published to the CDN origin and served from edge locations worldwide. Static content is not pinned to us. |
| Container pods | Regional (us) | A container project runs as a Kubernetes pod in the region. Requests reach the pod through the gateway, which fronts all traffic. |
| Databases | Regional (us) | A managed PostgreSQL / MySQL cluster runs in the region. A free database is single-zone only; a paid database can be multi-zone (replicaset / HA) within the region. |
| Cronjobs | Regional (us) | Scheduled container jobs run in the region. |
| Edge functions | Runtime service | Functions run on the PandaStack function-invoker runtime; code is stored in object storage and invoked by name. |
| Gateway | Fronts all traffic | Every project request — static or container — passes through the gateway. |
What this means in practice
Section titled “What this means in practice”- Static sites are fast everywhere because the CDN edge is global — a visitor in Europe or Asia
is served from a nearby edge location, not from
us. - Container apps and their databases live in
us. Co-locating a container app and its database in the same region keeps the app-to-database round trip local. When you link a database to a project, both are inus, so there is no cross-region hop. - Multi-zone is about availability within a region, not multi-region. A paid
replicasetdatabase spreads replicas across zones insideusfor high availability (3 replicas). It does not place data in a second region. A free database is single-zone standalone (1 replica). See Tiers & scaling.
Related pages
Section titled “Related pages”- Core concepts — the gateway, the CDN, and how traffic is served
- Static sites — CDN-served projects
- Container apps — regional pods
- Databases overview — regional managed databases
- Tiers & scaling — single-zone vs. multi-zone