Resilience on Digital sovereignty, thought through

Designing Digital Sovereignty for a World That Won't Hold Still

Fri, 29 May 2026 00:00:00 +0000

Don’t solve your current sovereignty problem.

Three examples to make this concrete.

An organization fine-tuning AI models on European customer data finds the EU AI Act now requires those models and pipelines to live within EU jurisdiction. The training infrastructure built in 2023 wasn’t designed for that constraint. The remediation isn’t a configuration change; it’s an architecture rebuild.
A European enterprise places R&D and strategic plans in a US-headquartered cloud provider’s EU region. The data sits in Frankfurt or Dublin. The contract specifies EU jurisdiction. But the parent company can be compelled by its home government to provide access – and the enterprise has no visibility into whether, when, or how often that happens.
A sub-sea cable cut between mainland Europe and Scandinavia reroutes traffic through paths with significantly higher latency and reduced bandwidth. The infrastructure is still running. The DR strategy assumed those links would behave the way they did when it was designed. They don’t anymore.

Three different scenarios, three different surfaces – legal, access, operational. But the same underlying pattern: the conditions the architecture was designed for keep changing, and what was a solid solution at procurement quietly becomes tomorrow’s liability.

Why Sovereignty Is About Knowing Your Levers

Fri, 05 Jun 2026 00:00:00 +0000

Sovereignty is no longer just a privacy or data-residency question. It has become a question of strategic control, resilience, and competitiveness across the entire digital stack. The debate is not about decoupling. It is about understanding the levers that others hold over critical operations, and deciding deliberately which ones to accept, mitigate, or neutralize.

For CIOs and risk leaders, sovereignty decisions now shape uptime, legal exposure, cost trajectories, and time‑to‑market – not just compliance.

Control Isn't Sovereignty?

Fri, 12 Jun 2026 00:00:00 +0000

— or rather, what looks like control is often just ownership

April 2025. The Iberian peninsula loses power. Spain, Portugal, parts of southern France – one of the largest blackouts in European history. The grid is gone for hours in some regions, days in others.

When power goes out for long enough, diesel reserves run down. Standard reserves last 24 to 72 hours. Beyond that, every operator depends on resupply. And resupply, during a regional crisis, doesn’t happen on first-come-first-served terms.

Mind the Depth (of Sovereignty)

Fri, 19 Jun 2026 00:00:00 +0000

This is the second of two articles on a sovereignty paradox. The first, Control Isn’t Sovereignty?, argued that delegating to systems with broader resilience can produce more outcome sovereignty than direct ownership. This one is about the harder question underneath.

Most sovereignty design follows the same logic. To protect operations against grid failures: Install generators on site. Stock diesel reserves to keep them running through an extended outage. Arrange supply contracts with fuel suppliers for resupply during a crisis.

What 'SEAL-2' Doesn't Tell You

Wed, 01 Jul 2026 00:00:00 +0000

How do you measure whether something is sovereign?

Ask it about a real system and the question splits. Can you keep running if conditions turn, or does someone else decide when you stop? Who holds the levers – the access, the keys, the legal authority? And how deep does it go: your provider may be sovereign, but what about their suppliers three layers down?

These have different answers, and they don’t move together. A service can be operationally solid and legally exposed. Jurisdictionally clean at the top and dependent on a single foreign supplier underneath. “Is it sovereign?” has no single answer, because sovereignty was never a single property – which is exactly why you can’t put one number on it.