Sovereignty Is Now a Feature. Welcome. We Kept Your Seat Warm.

Pillar 03 · Residency

Bias Declaration: I founded SkyeConnex. We defined Data Sovereignty as a Service and took it to market while sovereignty was still a panel topic. Weigh everything below accordingly.

BetaKit ran an op-ed this week.

https://betakit.com/sovereignty-is-now-a-feature-and-canadian-founders-are-shipping-it-for-free/

"Sovereignty is now a feature, and Canadian founders are shipping it for free."

Now.

Buyers have changed, the author reports. Sales calls open with jurisdiction questions. Where does the data live. Who owns you. Which foreign statute reaches your subprocessors.

Welcome to the call. Those questions have been the first slide of our deck since last year. We were told the market wasn't asking. Turns out the market just needed a 50 percent tariff to find its voice.

So the diagnosis is right. Three years late by the author's own count, but right. The prescription is where it gets fun.

The advice: write a one-page sovereignty spec sheet. Incorporation, ownership, residency, subprocessors, governing law, continuity plan. Hand it over before being asked.

A spec sheet is a promise. A residency clause is a promise. A continuity commitment is a promise. Promises are the one thing a foreign court can order you to break. The CLOUD Act does not read your PDF. When the production order lands, that beautifully formatted one-pager becomes Exhibit A. You knew which statutes reached you. You wrote them down. Thanks for the list.

The article warns against maple-washing. The vocabulary sounds familiar because it is. Some of us have been publishing on flag-washing and sovereignty theatre for years. Nice to see the phrasing circulate. Ideas that escape their author are the ones that won.

The warning itself lands, though. A flag on the pricing page and a .ca domain will not survive an architecture review. Correct. Then the piece prescribes more paper. A flag on a spec sheet is still a flag. Procurement reviews the architecture either way. The author said so himself, two paragraphs earlier.

Every one of those reviews reduces to a single question. The compelled-disclosure demand arrives. What can you actually produce? If the answer depends on your intentions, your governing-law clause, or your lawyer's stamina, you have residency. Residency is real estate. Data with a mailing address.

Custody works differently. Client-side encryption before a byte leaves the customer. Erasure-coded shards spread across independent jurisdictions. A zero-knowledge key hierarchy where no single operator can reconstruct the data or be ordered to. Including us. The answer to the subpoena becomes "we can't," and it holds up because mathematics doesn't take meetings. Try shipping that as a paint job.

Credit where due. The piece is right that sovereignty claims now get verified the way security claims are. Right again that giving sovereignty away signals you think it's worthless. We agree. We priced it, built the category, and put the acronym on the tin. DSaaS. First to market names the category. Second to market writes the op-ed.

The trade war will end. The physics won't change. Sovereignty by architecture, not by promise.

Everything else is a feature request.