Available Regions
Where your PocketBase Cloud deployment runs depends on your plan.
Pro — pick your dedicated compute’s region
Pro subscribers choose a region at checkout, and their dedicated compute is provisioned there. There are 10 locations to choose from:
Europe
| Region | Location |
|---|---|
| GRA | Gravelines, France |
| SBG | Strasbourg, France |
| RBX | Roubaix, France |
| DE | Frankfurt, Germany |
| UK | London, United Kingdom |
| WAW | Warsaw, Poland |
Americas
| Region | Location |
|---|---|
| BHS | Beauharnois, Canada |
| VIN | Vint Hill, Virginia, United States |
Asia-Pacific
| Region | Location |
|---|---|
| SGP | Singapore |
| SYD | Sydney, Australia |
Your compute’s region is fixed once provisioned — there’s no migration between regions today.
Free & Starter — shared server pool
Free and Starter deployments run on a shared server pool rather than a dedicated compute. Starter lets you choose which pool location your deployment lands in; Free is placed automatically. The shared pool runs on:
| Region | Location |
|---|---|
| fsn1 | Falkenstein, Germany |
| nbg1 | Nuremberg, Germany |
| hel1 | Helsinki, Finland |
| ash | Ashburn, Virginia, United States |
| hil | Hillsboro, Oregon, United States |
| sin | Singapore |
Choosing a region
Using the portal
Pro subscribers pick their compute’s region at checkout on the Plan page. Starter users may choose the pool location in the create form when deploying a PocketBase instance or frontend — it is optional, and leaving it on Any region places the deploy where there is the most free capacity. Free deployments are always placed automatically.
Using the CLI
Starter deployments take the pool location as an optional flag; without it the platform picks the region with the most free capacity:
pb cloud pb deploy --name my-app-db --location fsn1
pb cloud frontend deploy --name web --location fsn1Pro deployments target a specific compute rather than a region — the dedicated
compute is never auto-selected. Deploy asks which one when there is a choice,
and --compute settles it outright:
pb cloud compute ls # ids you can deploy to
pb cloud pb deploy --name my-app-db --compute <id>The same applies in a project shared with an organization, whatever your own plan: it runs on the organization owner’s compute, and you pick which.
Compute is provisioned by the platform, not the CLI: pb cloud compute ls
lists what your account can already deploy onto, and Pro compute is created
when you subscribe.
(--compute was called --server, and pb cloud compute ls was
pb cloud server ls; both old spellings still work.)
See Plans & Billing for what each plan
includes, and Installing the CLI
to get pb.