The €180M Sovereign Cloud Deal Is a Confession, Not a Strategy

Europe just paid €180 million to learn it doesn't own its own infrastructure

The European Commission is announcing today that it has awarded €180 million in cloud contracts to four European providers. The stated goal: digital sovereignty. The reality: at least one of those four providers runs on Google Cloud Platform underneath. Let that sit for a second. The EU is spending nearly two hundred million euros to fly a European flag on top of American infrastructure. This is not a strategy. This is a confession.

If you are a CEO, CTO, or founder building custom SaaS development products in Europe right now, you need to understand what this means. Not the press release version. The actual version. Because the gap between Europe's stated ambitions and its infrastructure reality is where the risk lives. And also where the opportunity is.

The sovereignty label versus the sovereignty stack

Berlin just published a new checklist defining what "sovereign" actually means for cloud infrastructure. Think about that timing. The money is already allocated. The contracts are signed. And now Germany is publishing the definition. This is like buying a house and then asking what "structurally sound" means.

The Register reports that one of the four selected providers operates on Google's backbone. Which means data might stay in the EU geographically, but the control plane, the orchestration layer, the deep infrastructure decisions are still made in Mountain View. Sovereignty is not about where the server sits. It is about who controls the stack. Who can push an update. Who can comply with a foreign government's data request at the infrastructure level. Who decides the roadmap.

Meanwhile, both Microsoft and AWS are announcing expanded "sovereign cloud" features in Stockholm this week. They are partnering with SAP. They are building dedicated regions. They are adding compliance checkboxes. They are doing exactly what smart incumbents do: they absorb the regulation into their product offering so that the regulation becomes a feature rather than a barrier. European sovereignty, powered by Seattle.

This is not conspiracy. It is business. And it is working.

The view from Jönköping versus San Francisco

I run HEIMLANDR.IO from Jönköping, Sweden. Not Stockholm. Not Berlin. Not the Valley. From here, the sovereign cloud conversation looks different than it does from a Brussels policy paper.

Sweden has real technical talent. We have a solid history with Ericsson, Spotify, Klarna, and a dense cluster of engineering-driven companies. We have stable energy. We have cold climate for data centers. On paper, Sweden should be a sovereign cloud powerhouse. In practice, almost every Swedish company I talk to runs on AWS or Azure. The government sector is tangled up in Schrems II compliance headaches. And the Swedish companies that could build sovereign infrastructure at scale are either too small, too underfunded, or too focused on selling to American customers to care.

The Nordics get some things right. Finland has invested seriously in AI infrastructure. Denmark is making moves with green data centers. Sweden's tech scene keeps producing world-class engineers. But none of that matters if the infrastructure layer underneath is controlled by three companies headquartered within 50 miles of each other in the Pacific Northwest.

The EU AI Act is here. GDPR enforcement is getting sharper. The Data Act adds new layers. But regulation without infrastructure is just paperwork. You cannot regulate your way to sovereignty. You have to build it. And right now, Europe is regulating at a pace that massively outstrips its building.

What "sovereign" actually requires

Let me be specific about what a real sovereign cloud stack looks like, because the discussion stays too abstract.

You need compute. Actual servers, in actual data centers, owned or leased by entities that fall entirely under EU jurisdiction. Not "hosted in EU region by a US company." Owned.

You need an orchestration layer. Kubernetes is open source. That part Europe can use freely. But the managed Kubernetes services (EKS, AKS, GKE) all funnel back to the hyperscalers. Running raw Kubernetes at scale requires serious operational capability that most European providers have not invested in building.

You need object storage. S3-compatible, but not S3. This is where projects like MinIO become interesting. Open source, S3-compatible, deployable on your own metal. Over 60,000 stars on GitHub. Battle-tested. No dependency on Amazon.

You need networking, identity, observability, CI/CD, and a hundred other pieces that most people take for granted because they click a button in the AWS console. Each of those buttons represents a dependency. Each dependency is a thread that, when pulled, leads back to American corporate control.

This is what €180 million should be buying. Not labels. Not checklists. Actual stack components that Europe owns from silicon to API.

The regulatory gap nobody is talking about

Here is what frustrates me as a builder. The EU is very good at defining what you cannot do. It is terrible at enabling what you should do.

GDPR is a genuine achievement. The AI Act, for all its flaws, is the first serious attempt at AI governance. But where is the EU's equivalent of DARPA? Where is the aggressive public investment in open source infrastructure? Where is the procurement reform that would let a 20-person company in Jönköping bid on a sovereign infrastructure contract without hiring a full-time EU grants administrator?

The procurement process itself is a filter that selects for large incumbents and consultancies. Which is how you end up with a "sovereign" provider running on Google. The companies big enough to win EU contracts are big enough to have partnership deals with American hyperscalers. The companies small enough to build genuinely independent infrastructure are too small to survive the procurement process.

Sweden's own public sector IT strategy is not much better. SVT has reported multiple times on the chaos of government IT procurement. Billions of kronor flowing into legacy systems maintained by the same three system integrators. The digital sovereignty conversation barely exists at the municipal level, where most public services actually run.

Where this goes: 2027 to 2031

The trajectory here is not encouraging without a serious correction.

In the next two to three years, American hyperscalers will complete their "sovereign by compliance" play. Every AWS region in Europe will have a "sovereign" checkbox. Azure will offer data residency, key management under EU entity control, and all the audit trails regulators want. The infrastructure will still be American. But it will be legally defensible as sovereign. The EU will accept this because the alternative is admitting the €180 million did not solve the problem.

The path toward AGI makes this worse, not better. Training large models requires massive compute. Inference at scale requires massive compute. Europe does not have the GPU clusters. It does not have the custom silicon programs. Every European AI company of any significance trains on American cloud. When the models get powerful enough to matter for national security, economic competitiveness, and critical infrastructure, Europe will discover that its AI capability is a tenant in someone else's building.

The realistic good scenario: a handful of European infrastructure companies, possibly backed by sovereign wealth funds or pension capital, build a genuine alternative stack. Open source based. Interoperable. Not trying to replicate AWS feature-for-feature but covering the 80% that most workloads actually need. If the Nordics lead this, which they could given the talent and energy advantages, it could become a real business, not just a policy project.

The bad scenario: Europe keeps writing checks for sovereignty theater while every actual workload runs on US rails. And one day a geopolitical event makes the dependency obvious in a way that press releases cannot paper over.

What to actually do about this

If you are building software in Europe right now, here is my practical take:

Architect for portability from day one. Use containers. Use Kubernetes. Abstract your storage layer behind S3-compatible APIs. Do not hard-wire to any single cloud provider's proprietary services. This is just good fullstack development practice, but it is also your insurance policy. If you need to move, you can move.

Evaluate self-hosted alternatives seriously. The awesome-selfhosted repo on GitHub has nearly 290,000 stars for a reason. There are production-quality, open source replacements for most SaaS tools you pay for. For workflow automation, n8n is a real option with 186,000+ stars and native AI capabilities. For observability, Netdata runs anywhere. For object storage, MinIO. For reverse proxy and ingress, Traefik. The pieces exist. Assembly is the hard part.

If you are in blockchain development or smart contract development, the sovereignty question is even more acute. Decentralized protocols are supposed to be jurisdiction-neutral, but the nodes run somewhere. The RPCs connect through someone's infrastructure. If your chain's validator set runs 70% on AWS us-east-1, your decentralization is cosmetic. Think about this when choosing infrastructure for your nodes, your indexers, your frontends.

Build with European partners where the capability exists. Software development in Sweden and the Nordics is genuinely world-class. The engineering is here. The security mindset is here. What has been missing is the ambition to build infrastructure rather than just applications on top of someone else's infrastructure. That is starting to change. Be part of the change.

What to look at

MinIO - If you are not running your own S3-compatible object storage yet, start here. 60,000+ stars. Production-proven. This is one of the genuine building blocks for any sovereign or hybrid infrastructure play.

n8n - Self-hostable workflow automation with AI capabilities. For any team building AI agents or automation pipelines, this is worth evaluating as an alternative to cloud-locked orchestration tools.

awesome-selfhosted - The canonical list of self-hostable software. Bookmark it. Use it as your starting point every time you are about to sign up for another SaaS tool with US data processing.

The Berlin sovereign cloud checklist - Whatever your opinion on its timing, it is the most concrete attempt yet to define what sovereign actually means. Read it. Use it as a framework when evaluating your own dependencies.

The bottom line

€180 million is not a lot of money for continental-scale cloud infrastructure. AWS spent more than that last quarter on cooling systems. The number itself tells you the EU's actual commitment level. This is a gesture dressed up as a program.

But here is the thing. The EU does not need to outspend the hyperscalers. It needs to outbuild them where it matters. Open source gives us the code. European data centers give us the physical layer. European engineers give us the talent. What is missing is the will to assemble these into something coherent and the funding structures that reach builders instead of consultants.

From Jönköping, I see it clearly. The talent is here. The energy is here. The problem is not capability. The problem is that Europe keeps buying the label of sovereignty instead of building the reality of it. At some point, the invoice comes due. And you cannot pay it with press releases.

Build your own stack. Own your own data. Stop renting your sovereignty from Mountain View.

Fredrik Brunnberg is the CEO of HEIMLANDR.IO, building AI and software solutions from Jönköping, Sweden. This is the daily HEIMLANDR briefing. If you found this valuable, share it with someone who builds things.