The Sovereign Cloud Still Has a Master Key

Europe's Cloud and AI Development Act moves data under a friendlier legal roof. But a sovereign cloud still has an operator who can be ordered to open it. Here is the architecture that removes it.

Right now your most sensitive files may be sitting on a server that can be opened without your knowledge, on the order of a government you never voted for, under a law you never read. The sovereign cloud is sold as the cure for exactly that fear. You do not get a phone call. The provider receives the order, the provider complies, and the first you learn of it, if you ever do, is after the data is already gone.

Europe just spent serious political capital trying to close that gap. It is worth understanding why the fix it chose narrows the problem without removing it.

What Europe actually changed

On 3 June 2026 the European Commission adopted the Cloud and AI Development Act, the centrepiece of its tech sovereignty package. At the most sensitive tier, the one covering critical government systems, US cloud hyperscalers would be barred outright, and other providers would have to prove verified data localisation and legal ring-fencing to qualify at all.

The target is named in the open: the US CLOUD Act. That law lets American authorities compel a US-based provider to produce data in its possession, custody, or control, no matter where on the planet the bytes physically sit. As a congressional analysis frames it, access follows corporate control, not data location. A data centre in Frankfurt does not protect you if a company in California can be ordered to unlock it.

This is not hypothetical history. The law exists because, in a dispute that began in 2013, US investigators demanded emails a provider had stored on a server in Ireland, the provider refused, and Congress resolved the standoff in 2018 by making corporate control, not geography, the test. Location was argued in court, and location lost.

So Europe is moving the data under a different legal roof. For some threat models that is genuine progress, and it shrinks the set of authorities that can reach into a European hospital or ministry. We have made the location case ourselves, in why you want a personal server over a rented one. The point worth sitting with is what the location fix still leaves untouched.

A sovereign cloud is still a cloud

Run sovereign workloads on a managed stack and control-plane access still sits with a third party. If that third party can technically produce your data, that third party can be ordered to produce it. The flag on the building and the postcode of the disk are not the variable that sets your exposure. The variable is who can turn the lock.

Relocating that lock from a US operator to a European one changes whose court can demand the key. It does not change the fact that a key exists, that one company holds it, and that holding it makes that company a single point a subpoena, a breach, or an acquisition can all aim at. Sovereignty defined this way answers the question which government. It never reaches the question whether anyone at all. This is the deeper reason we keep arguing to burn the rented cloud rather than redecorate it.

Architecture that cannot be ordered to betray you

There is exactly one kind of data an operator cannot be compelled to hand over: data the operator cannot read. That single constraint is where Elacity starts, and it is why we keep returning to compute you actually own instead of compute you rent on better terms.

Content stays encrypted everywhere except a single sealed moment of use. The key that unlocks what you own is never held in one place. It is split across multiple independent machines, an owned two-of-three quorum, and each machine re-checks your on-chain rights before it releases its share. No single operator, Elacity included, holds the key. There is no one party a court can serve, because there is no one party that can comply.

Even at the instant of use, the key is used and never owned. It exists in the clear for a fraction of a second inside a sealed sandbox, welded to that one action, then wiped. An order to produce the key arrives to find nothing standing still long enough to seize. Your own machine remains the source of truth, and the cloud, the chain, even the key network sit beneath it as guests you can swap out.

This is trust-minimised, not trustless, and claiming otherwise would be the lie that discredits everything around it. A quorum that colluded could in principle reconstruct a key. The threshold is built so that normal operation never does, and so that betrayal would require several independent parties to break together, in the open, on the record. Today that quorum is an owned, operator-run set rather than a permissionless market of stakers, which is honest direction rather than finished work. The claim is not that your data is beyond all reach. It is that no single party can be ordered to surrender it, and reaching it would mean forcing several parties to fail at once.

A sovereign cloud asks you to trust a better landlord. The harder and more durable question is whether anyone needs to hold your key at all. If you want to follow how we are answering it, follow Elacity on X.