Regions
HostStack runs on Hetzner infrastructure across Europe and the US East coast. Every service, database, and managed addon is deployed in a single region — we don't split workloads across providers or continents to keep latency between sibling resources predictable.
Available Regions
| Region | Slug | Hetzner DC | Status |
|---|---|---|---|
| Helsinki, Finland (FI) | eu-central-1 | hel1 | Available · default |
| Nuremberg, Germany (DE) | eu-central-2 | nbg1 | Coming soon |
| Falkenstein, Germany (DE) | eu-west-1 | fsn1 | Coming soon |
| Ashburn, Virginia (US) | us-east-1 | ash | Coming soon |
New projects deploy to eu-central-1 (Helsinki, Finland) — currently our only live region and the default. The remaining regions are on the roadmap; each will appear in the create-project dialog once workers are provisioned in it.
Latency Expectations
Approximate round-trip times from major cities to eu-central-1 (Helsinki):
- Helsinki: ~1 ms
- Stockholm: ~8 ms
- Warsaw: ~20 ms
- Frankfurt: ~28 ms
- Amsterdam: ~30 ms
- London: ~35 ms
A North American region (us-east-1, Ashburn) is on the roadmap for latency-sensitive workloads — typical RTT from NYC ~10 ms, from SF ~70 ms.
Cross-Region Latency
Sibling resources (your service ↔ your database, your service ↔ your Redis) always land in the same region. The intra-region link is sub-1 ms inside Hetzner's network, so a HostStack-managed Postgres feels local from any HostStack service in the same region. Cross-region requests use the public internet — expect typical 20–100 ms.
GDPR & Data Residency
Our live EU region — Helsinki, Finland — keeps customer data (database content, object storage, backups, logs) entirely inside the EU, as will the Nuremberg and Falkenstein regions when they come online. The planned Ashburn region is for US-resident workloads; it is not GDPR-resident — stay on an EU region if your data subjects are in the EU. See our privacy policy and DPA for the formal commitments.
Next: Networking · Managed Databases