A Stack Harbor PaaS installation can expose more than one region — a distinct hardware set with its own location, capacity, and pricing, but operated under the same platform interface. Regions let an installation host workloads in multiple geographies, mix hardware tiers (for example, lean dev/test against heavier production), and let you move applications between locations without rebuilding them.
This section covers the two parts of working with regions:
- Choosing a region — what region selection affects, where the dropdown appears in the creation flows, and how to read the details for each available region.
- Migration between regions — moving a running environment to a different region without recreating it, in either live (zero-restart) or offline mode.
When this matters
- Multi-geography deployments — pick the region closest to your traffic origin to keep latency down.
- Compliance — pick a region in the jurisdiction your data must reside in.
- Lifecycle separation — run dev and test in a cheaper region and production in a region tuned for it.
- Disaster recovery — span two regions in separate data centres and front them with the appropriate routing layer.
What stays the same across regions
The platform itself does not change. Dashboard, CLI, API, container types, runtimes, deployment surfaces — all identical region to region. What changes is the underlying hardware, the location, the available capacity, and (depending on the installation) the price and the auto-assigned environment domain.