In ECI Research’s conversation with Stack8s at KubeCon EU 2026, the most important message was not simply that European buyers care about sovereignty. That much is already established. The more important point is that sovereignty is shifting from a policy discussion into a platform design requirement.
That distinction matters. Enterprises are no longer evaluating sovereignty only through the lens of data residency or legal jurisdiction. They are increasingly connecting sovereignty to compute access, vendor concentration, resilience, and the ability to move workloads without being trapped by a single provider’s pricing or operating model.
Sovereignty is becoming an infrastructure question
Jeremy’s framing was blunt but useful: compute is scarce, and when organizations centralize too much of their operating model around a small number of hyperscalers, they also centralize risk. That risk is not limited to price. It extends to access, prioritization, and strategic control.
The takeaway is that sovereignty is no longer just about where data sits. It is about whether an organization can maintain control over infrastructure decisions end to end. If compute allocation, service availability, and platform economics are effectively dictated by a small number of providers, then sovereignty is constrained even if workloads remain technically compliant.
This is one reason the KubeCon EU conversation around sovereign cloud continues to evolve. Buyers increasingly want architectures that preserve optionality across on-premises, hosted, and cloud environments rather than forcing a binary choice.
Compliance is accelerating the conversation, but resilience is the deeper driver
The interview tied this trend to European regulation, including the Cyber Resilience Act. That is directionally correct, but the stronger point is that regulation is accelerating a concern that already existed.
Across ECI’s research base, compliance, governance, and security repeatedly appear alongside operational complexity and modernization pressure. In Day 0 infrastructure research, organizations consistently report that cloud-native adoption is shaped by:
- Security and compliance concerns
- Budget constraints
- Integration complexity
- Legacy modernization pressure
- Skill and operational challenges
That pattern matters because it shows sovereignty is not emerging in isolation. It is part of a broader enterprise effort to reduce fragility in modern digital infrastructure.
Jeremy’s geopolitical examples were intentionally provocative, but they reinforce a real enterprise concern: dependence is easy to ignore until an external event exposes it. In that sense, sovereignty is becoming a resilience strategy as much as a regulatory strategy.
The real buyer question: can compute become portable?
One of the strongest lines in the interview was the comparison between compute and electricity. The idea is simple: switching compute providers should become easier, more routine, and less disruptive.
That is an ambitious goal, and the market is still far from achieving it consistently. But it captures a real buyer demand. Enterprises want:
- Lower switching friction across environments
- Better alignment between data location and compute placement
- Less exposure to vendor lock-in
- More predictable cloud economics
- A clearer path to resilience when supply, pricing, or regulation changes
This is where Kubernetes and platform engineering continue to matter. The value is not Kubernetes by itself. The value is the abstraction layer it can provide when paired with operational discipline, policy controls, and workload portability.
Cost pressure is now part of the sovereignty story
The Stack8s claim that some customers can save up to 85% on cloud bills should be treated carefully. As with any aggressive cost claim, there should be skepticism until the baseline, workload profile, and migration assumptions are clear.
Still, the claim resonates because cost has become inseparable from sovereignty discussions. ECI’s research already shows that cost savings, compliance, and AI readiness increasingly appear together in enterprise decision-making.
In theCUBE’s Data Platforms research, organizations reported pressure from:
- Compliance requirements such as GDPR and DORA
- AI infrastructure cost
- Lack of interoperability
- Skills shortages
- The need for faster insights with tighter economic control
That combination suggests that sovereignty is not just an ideological or regional preference. It is often a practical response to rising infrastructure costs, interoperability limits, and the need to align compute consumption with business priorities.
AI changes the labor equation, not the need for talent
The interview also touched on AI and skills. Jeremy argued that skills are not the core problem because AI can help teams move faster and do more with fewer people. That view reflects a broader market trend, but it deserves nuance.
AI can compress some delivery work. It can improve productivity. It can reduce the number of people needed for certain implementation tasks. But that does not eliminate the need for skilled operators, architects, and platform teams. In many cases, it increases the premium on judgment.
To sum it up: AI may reduce the labor required for repetitive infrastructure and development work, but it does not remove the need for organizations to understand governance, portability, resilience, and platform tradeoffs. If anything, it raises the stakes for making those decisions well.
Bottom line
The Stack8s conversation reflects a broader shift at KubeCon EU 2026. Sovereignty is no longer just a regional talking point or a compliance checkbox. It is becoming a design principle for infrastructure platforms.
The organizations that will benefit most are not simply the ones that move away from hyperscalers. They are the ones that build enough portability, policy control, and cost discipline into their platforms that they retain real strategic choice.
That is the more durable definition of sovereignty: not isolation, but optionality under pressure.
