Default Amsterdam.
More regions on request.
Every workload starts in Amsterdam for EU data residency, GDPR alignment, and low-latency European access. Additional regions are supported through partners — your platform stays identical.
AMS-IX-connected, Tier III equivalent, EU jurisdiction.
The Netherlands is the proof — not the boundary. EU data residency, redundant power, redundant cooling, and AMS-IX peering for low-latency access across Europe.
Operated by Stakater AB, a Swedish company under EU jurisdiction. Data Processing Agreements and ISO certificates available for your legal review.
One operating model. Six places we can deploy it.
Amsterdam is the default. The rest are supported through infrastructure partners — same managed OpenShift, same SLAs, same operating posture.
Location should fit the customer.
We add regions for real customer reasons: latency, jurisdiction, procurement. New locations are provisioned quickly once the need is concrete.
Plan Your Deployment →- Meet customers in-region for latency, geography, and procurement requirements
- Deploy from an EU baseline — GDPR alignment and EU data residency without being Netherlands-only
- Expand through regional partners across Europe, the US, and APAC
- Keep the same managed OpenShift platform, day-2 ops, and tooling everywhere
Need a region we haven't deployed yet? Tell us.
Book a 30-minute call. We'll scope the right region, partner, and operating model for your workload.