More and more people are talking about Sovereign Cloud. A lot of private and public money is flowing towards “solving” the EU Sovereign Cloud need. But what is that need, really?
What does “sovereign” actually mean? A session at the recent CTOClub (thanks Tom and Niels!) sparked some thinking on this. Here is my take.
At the surface: political and emotional
Most of the EU Sovereign Cloud conversation is driven by either political or emotional pressure.
The political angle is clear: there is growing concern over who controls systems and data. There is also an economic incentive to keep digital spending inside the EU. As a result, governments, heavily regulated industries, and critical infrastructure organisations are prioritising EU-based cloud. That will trickle down: any organisation supplying them will increasingly face the same requirement.
The emotional angle is one I encounter just as often. Business owners see what is happening in the world and start imagining worst-case scenarios: what if access to US cloud services gets disrupted? What if data becomes a geopolitical lever? That fear, sometimes informed and sometimes not, is what drives many people toward EU Sovereign Cloud.
Both are valid motivations. But neither makes the decision straightforward. What could help is a more structured way of looking at what “sovereign” actually covers.
The PESTLE lens
One way is through the PESTLE framework. It allows for analysing the external environment a business operates in, across six dimensions. Applied to cloud sovereignty, it maps like this:
- Political: governments are legislating data residency and pushing for strategic digital autonomy.
- Economic: EU-based cloud is becoming a procurement requirement, a cost consideration, and a competitive differentiator all at once.
- Social: public trust in where data lives is becoming a real factor, especially in healthcare, education, and public services.
- Technological: the infrastructure layer itself, who controls it and how portable your workloads are. (Spoiler: container-based workloads FTW)
- Legal: GDPR, the Schrems II ruling, and emerging data act legislation all impose hard constraints.
- Environmental: EU-based providers are increasingly held to stricter sustainability standards.
The Technological lens is the right one
Most companies feel pressure at least from two or three of the above dimensions. But often that is not even clear today.
The one that is most directly actionable, and what you can do something with today, is the Technological dimension: not just which provider to pick, but whether your architecture actually gives you the freedom to move when the other dimension get more importance and at what cost.
How Kubernetes enables EU cloud portability
This is where containers and Kubernetes become relevant, and not just as a technical detail.
Kubernetes is a core part of our Skyscrapers Platform Blueprint.
One of its less-discussed properties is that it acts as an abstraction layer over the underlying cloud. Your workloads are defined in a way that is largely independent of which provider is running them. You are not locked in by the platform itself, only by the services you choose to build around it.
That directly addresses the Technological dimension of PESTLE. The question should not just be “which EU cloud provider do we pick?” It should be “how do we build so that switching is actually more realistic?”
Real-world Kubernetes migration: AWS to Scaleway
We recently migrated a customer from AWS to Scaleway, a European cloud provider. They were driven mostly by the Social and Economic dimensions.
Because their workloads were running on Kubernetes, the migration was reasonably straightforward. No rearchitecting, no months-long rewrite.
More details on this specific case are coming soon, but the point is clear: the investment in a well-structured platform pays off precisely in moments like these (amongst other benefits).
Conclusion
EU Sovereign Cloud is not a single checkbox. It is a spectrum of concerns spanning politics, law, economics, and technology. The organisations that will navigate it best are not those who panic-buy EU cloud logos, but those who build with portability and control in mind from the start.
Kubernetes and the way you architect around it matters more than most people realise when it comes to true cloud sovereignty.
Curious what that could look like for your platform or team? I am happy to talk and learn about your specific perspective!