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 |
|---|---|---|---|
| Falkenstein, Germany 🇩🇪 | eu-central-1 | fsn1 | Available · default |
| Nuremberg, Germany 🇩🇪 | eu-central-2 | nbg1 | Coming soon |
| Helsinki, Finland 🇫🇮 | eu-west-1 | hel1 | Available |
| Ashburn, Virginia 🇺🇸 | us-east-1 | ash | Coming soon |
New projects deploy to eu-central-1 (Falkenstein) by default. eu-west-1 (Helsinki) is also live. The remaining regions are being brought online — additional regions will appear in the create-project dialog as they go live.
Latency Expectations
Approximate round-trip times from major cities to eu-central-1 (Falkenstein):
- Frankfurt: ~5 ms
- Amsterdam: ~12 ms
- London: ~22 ms
- Paris: ~18 ms
- Stockholm: ~25 ms
- Madrid: ~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
EU regions (Nuremberg, Falkenstein, Helsinki) keep customer data — database content, object storage, backups, logs — entirely inside the EU. The Ashburn region is provided for US-resident workloads; it is not GDPR-resident — pick 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