New SDK. New API. New tooling. A migration project, a steering committee, and a slide that says "Phase 1" in a font that means business. Eighteen months later the data still isn't sovereign, but the consultants have a lovely deck and the budget has gone to a better place.

We went the other way.

AWS gave the world S3 — three S's: Simple Storage Service. We kept all three and added a fourth. S4. Simple, Sovereign Storage Service. The extra S was free. Take it.

Native SigV4, path-style addressing, the whole protocol. Your code already knows how to talk to it — because it's the same protocol your code already talks to. We didn't reinvent the interface. We just changed what happens behind it.

boto3, aws-cli, rclone, Cyberduck, the vendor backup client nobody enjoys configuring and everybody's afraid to touch — all unchanged. You repoint one endpoint. That's the migration. The application above it never finds out anything happened, which is exactly how a migration should go and almost never does.

Here's the part that matters. Everything written through that endpoint gets encrypted, erasure-coded, and scattered across multiple providers before it lands anywhere. No single cloud ever holds a complete, reconstructable copy. A subpoena to any one of them produces fragments. Fragments are not data. They're confetti with a legal department.

So the same line of code that used to hand a hyperscaler a full, intact, court-order-ready copy of your data now hands out mathematically useless shards instead. Same SDK. Same call. Opposite outcome. Nobody upstream has to know, least of all the entity holding the shards.

The sovereign cloud market spent three years arguing about where the data centre sits, as if a postcode were a security control. The harder question was always who can be compelled to open it — and whether fixing that meant rewriting everything you own.

Turns out it doesn't. You just change the URL.

Three S's built the cloud everyone runs on. The fourth is the one that decides whose laws it answers to.

S4 is in beta, with real users on it today. Apply for the beta at SkyeConnex.com


Originally published by Ross Norrie, founder of SkyeConnex, on LinkedIn.

Published May 25, 2026 · More from the SkyeConnex blog