AWS European Sovereign Cloud alternative: sovereignty without a US parent

AWS and Microsoft now sell a "sovereign" cloud built for Europe, with EU staff and local governance. The operator is still a US company, and its parent remains subject to US law, the Cloud Act included. Bunker is hosted in France by a French company with no US parent, on a fully open-source stack.

The AWS European Sovereign Cloud is a real engineering effort. A dedicated region in Brandenburg, Germany, staffed by EU residents, with operations and support kept inside the European Union. Microsoft has gone the same way with its EU Data Boundary and a Sovereign Cloud line. Both genuinely solve data residency and local operations.

They do not change who owns the operator. Amazon and Microsoft are US companies, and a US parent stays within the reach of the Cloud Act and FISA Section 702 regardless of where the data sits. That gap is exactly what European data protection authorities debated during the EUCS sovereignty discussions and what Schrems II put on the table. Bunker answers it differently: hosted in France by a French company with no US ownership, subprocessors listed in the GDPR art. 28 contract, and code you can read and run yourself.

Where a European operator changes the legal picture

Jurisdiction follows the operator

A US company must comply with a Cloud Act order even for data held in its German region. Bunker is hosted in France by a French company with no US parent, and none of its subprocessors is under US jurisdiction. The subprocessors are listed in the GDPR art. 28 contract, so you can check each link yourself.

Open source you can audit

Bunker runs on Kubernetes, PostgreSQL, Ceph S3 and open LLM stacks. Your security team can read the code that holds your data, line by line. The hyperscaler sovereign offers keep their control plane proprietary, so the audit stops at the documentation.

Managed or on your own racks

Run Bunker as a managed sovereign cloud, or install the same stack on hardware you own. The AWS and Microsoft sovereign regions stay tied to their own datacenters and operating model, with no path to bring the platform in-house.

No egress tax on leaving

Bunker charges no egress fees and uses open formats, so moving data out costs nothing extra. On the hyperscalers, data transfer pricing and proprietary services raise the cost of an exit the longer you stay.

Bunker against the hyperscaler sovereign offers

Criterion Bunker AWS European Sovereign Cloud Microsoft EU Data Boundary
Operator nationality French Amazon, a US company Microsoft, a US company
US parent company None Amazon.com Inc. (US) Microsoft Corp. (US)
Within scope of the Cloud Act / FISA 702 French company, no US parent, no US subprocessor (listed in the GDPR art. 28 contract) Yes, the US parent remains bound Yes, the US parent remains bound
Data residency in the EU France Yes, region in Brandenburg, Germany Yes, EU Data Boundary
EU staff and local governance Yes Yes, EU residents and local control Yes, EU operations
Open source and auditable Full stack, public code No, proprietary control plane No, proprietary control plane
Reversibility / on-premise Re-internalisable on your hardware No, tied to AWS No, tied to Azure
Egress fees None Charged Charged

Why data residency is not the same as legal sovereignty

AWS EUSovereign CloudEU operatorData residencyLegal sovereignty

Data residency answers one question: where do the bytes physically live? The AWS European Sovereign Cloud answers it well, with a region in Germany, EU staff and a governance structure designed to keep operations inside the Union. Microsoft does the same with its EU Data Boundary. For many GDPR concerns, that is a meaningful step, and it removes the simplest objections about transatlantic transfers.

Legal sovereignty answers a harder question: which law can compel the operator? The Cloud Act lets US authorities order a US company to produce data it controls, including data stored by a foreign subsidiary. FISA Section 702 adds surveillance powers over non-US targets. As long as the operating entity has a US parent, those obligations follow the company, not the datacenter. Local governance and EU personnel reduce the practical likelihood of a request reaching your data, yet they do not extinguish the parent company's duty to comply. Bunker is hosted in France by a French company with no US parent, and none of the subprocessors listed in its GDPR art. 28 contract is under US jurisdiction. The distinction is the one regulators raised throughout the EUCS debate and the one Schrems II forced organisations to take seriously.

Frequently asked questions

Isn't AWS European Sovereign Cloud already sovereign?

It is sovereign on data residency and operations. The region sits in Germany, staff are EU residents, and governance is local. The limit is legal: Amazon is a US company, so the Cloud Act and FISA 702 still bind the parent. Sovereignty over the physical and operational layer does not remove that obligation over the corporate layer.

Does Microsoft EU Data Boundary keep my data away from US authorities?

The EU Data Boundary keeps storage and most processing inside the European Union, which addresses data residency. It does not change Microsoft's status as a US company. A Cloud Act order can still be directed at the parent, and Microsoft has acknowledged it cannot guarantee it would never have to comply. Residency and legal reach are two separate questions.

Where does Bunker stand on the US CLOUD Act?

Bunker is hosted in France by a French company with no US parent, and none of its subprocessors is under US jurisdiction. The subprocessors are listed in the GDPR art. 28 contract. US extraterritorial law works by compelling companies under US jurisdiction, so those links are what you should check, with us as with any provider. No provider can promise absolute immunity, and we do not.

What do I give up by choosing a European operator over a hyperscaler?

You give up the very long catalogue of proprietary managed services that AWS and Azure offer. Bunker covers the infrastructure most SMEs and mid-market companies need: compute on Kubernetes, PostgreSQL, Ceph S3 storage, private LLMs, monitoring. In exchange you get auditable open source, no egress fees, and the option to run the same stack on your own hardware. An audit of your workloads shows what maps over cleanly and what needs work.

Sovereignty you can check in the contract

We map your workloads, compare the real exposure, and build a path to a French operator you can audit.

AWS and Amazon Web Services are trademarks of Amazon.com, Inc. Microsoft is a trademark of Microsoft Corporation. Bunker is not affiliated with Amazon or Microsoft; these names are used only to identify the services compared.