What EU-native means, and why an EU region is not enough
The difference between data stored in the EU and infrastructure governed by EU law alone, and why it matters for GDPR and the US CLOUD Act.
"EU data residency" and "EU-native" sound similar. They are not the same thing, and the difference matters when you write your GDPR file or answer a customer security review.
Data residency is about where
Every large US cloud provider offers EU regions. Choosing Frankfurt or Dublin puts your data on servers physically located in the EU. That is data residency.
It does not change who operates the infrastructure, or which laws apply to the company that does.
EU-native is about who
EU-native means the infrastructure provider itself is owned and headquartered in the European Union and governed by EU law alone. It is not a US hyperscaler operating an EU region.
That distinction matters because of the US CLOUD Act, which can require US-based providers to hand over data they control, regardless of where it is stored. A US provider's EU region is still operated by a company subject to US law. An EU-native provider falls outside the reach of the CLOUD Act.
What it changes in practice
- GDPR transfers. With workloads and backups on EU-native providers, transfer mechanisms and the CLOUD Act drop out of your GDPR file.
- Security reviews. Customer questionnaires about extraterritorial access get a short, simple answer.
- Sub-processors. Fewer non-EU sub-processors to list and assess.
Which providers qualify
Cloud Exit builds exclusively on EU-native providers, including:
- Hetzner for compute, storage and networking
- Syself for managed Kubernetes
Both are German companies subject exclusively to EU law. Data residency is Germany or elsewhere in the EU.
What EU-native does not do on its own
Choosing an EU-native provider removes one risk. It does not make an environment secure or compliant by itself. That still takes a hardened baseline, encryption, access control, tested backups and audit evidence. Every cluster we build ships with that baseline from day one.
Moving from a US hyperscaler
If you run on AWS, Google Cloud or Azure today, the move to EU-native infrastructure can be done in phases, with a rollback plan at each step and no big-bang cutover. Our cloud migration page describes how.
This guide is backed by a service we run every day.
See the compliance baseline