Pillar 03 · Residency

Every sovereign cloud pitch this year has a green slide. Hydro. Cold climate. A leaf somewhere in the corner.

Fine. Now ask what the slide is actually claiming.

Carbon-aware computing works by moving workloads to wherever the grid is cleanest at that moment. The spread is huge even inside one country. Quebec’s grid runs at roughly 30 grams of CO2 per kWh. Alberta’s runs at over 450. Same country, same laws, about 15 times apart. Hyperscalers chase spreads like that around the planet all day.

Data residency says you can’t chase it. The data stays where the law says it stays.

Most vendors handle that collision by not mentioning it. We went and looked.

We ran it against our own placement data. Seven residency zones. In four of them there is no carbon choice at all. Every UK region sits in the same moderate band. Every region in Asia Pacific, the Middle East and Africa sits in a high band. That’s 32 regions in APAC alone and not one of them gets you out. Only the EU, North America and South America leave real room to choose.

So for most of the world, the carbon footprint of sovereign data was set the day the residency rule was written. The lawyer picked the grid. The sustainability team inherited it.

But notice what that table assumes. It assumes the thing being placed is a whole copy of your data. One readable file, sitting in one building, on one grid. That’s what residency was written for, because a whole copy in the wrong building is a whole copy someone can be compelled to hand over.

Now change the unit.

Our custody layer never stores a whole copy anywhere. Every file is encrypted on the client, then split into shards spread across independent hosts. No shard is readable. No single host, operator or government can rebuild the file from what it holds. The sovereignty lives in the math and the keys, and the keys never leave the customer.

That changes the placement question completely. Instead of asking which one building your data must live in, you’re asking where a set of unreadable fragments can sit. More hosts means more grids to choose from. And since any five of seven shards rebuild the file, you’re not hostage to any one of them.

The lawyer still decides what’s allowed. What changes is what the lawyer is being asked to approve. “Can an unreadable fragment sit on a hydro grid next door?” is a very different conversation from “can our customer database move to another country?” Some regimes will say yes. Some won’t. The architecture gives you something new to put on the table.

Where the answer is yes, carbon gets to break the tie. It never gets a vote on whether a location is allowed. You can’t put a weight on unlawful.

Which leaves the harder question. What can a vendor honestly claim?

Most emissions numbers on slides are an estimate multiplied by somebody else’s coefficient. Pick a different coefficient and you get a different planet.

We started with the one thing we can prove, which is how much we store. The same sharding that makes the data unreadable also makes it lean. Our erasure coding gives the same protection as three-copy replication on less than half the disk. Every account sees its real ratio, along with what its coding survives, because efficiency without the durability trade is half a story. That ratio needs no emissions factor. Whatever a terabyte-year really costs in watts cancels out. Nobody can argue with my coefficient because I didn’t pick one.

Everything else follows the same rule. We sign storage exposure and nothing we can’t measure, because a signature on a guess just makes the guess look audited. Customers choose their own baseline, because what they would have done without us isn’t something anyone can observe. And our build fails if anyone types “net zero” into the product. The test suite has better claim discipline than most marketing departments.

Canada made all of this easier to fudge this year. The Budget 2025 Implementation Act, No. 1 received Royal Assent on March 26, 2026 and removed the requirement for environmental claims to be backed by an internationally recognized methodology. Claims still need adequate and proper substantiation. The bar moved on paper. It didn’t move for anyone who has to defend the number in front of a procurement officer.

Sovereignty used to mean picking a building and accepting its grid. Break the data into pieces nobody can read and you get to ask a better question. Then only claim what you can prove.

Bias Declaration. I’m the founder and CEO of SkyeConnex. This describes how we approach the problem and I have every reason to make it look good. Which is why it only says what we can prove.