What Is Infrastructure Sovereignty?

I've been in IT for twenty-five years. The first thing I learned at fourteen — billing clients, doing real work, before I could legally drive — was that technology should work for the person using it. The second thing I learned, slower and more painfully, was that most of the industry is designed to make that impossible.

Infrastructure sovereignty is the practice of owning your full stack. Not renting it. Not outsourcing it to a company that could change its pricing, deprecate your feature, or get ransomwared into oblivion. Owning it — hardware, network, operating system, applications, data, keys.

That last one matters. If someone else holds the encryption keys, you don't own your data. You're a tenant.

Where This Comes From

I spent years doing incident response. MoxFive was on the ground during some of the largest cyberattacks in US history — New York, Los Angeles, Baltimore, Miami — and I was there in the field. One incident I handled solo: 150 interconnected servers, all encrypted, Active Directory and DNS completely destroyed. I decrypted and rebuilt them. I've seen what happens when you don't control your infrastructure and something goes wrong.

The ransomware operators aren't geniuses. They win because the systems they hit are opaque, unmaintained, and owned by vendors who sold support contracts instead of teaching people how their infrastructure actually worked. Vendor lock-in doesn't just cost money. In a crisis, it costs everything.

After enough of that, you stop tolerating the cloud by default. You start asking: what do I actually control here?

What Sovereignty Means in Practice

It means your data lives on hardware you can physically touch. Not always — there are legitimate reasons to use hosted services — but the default should be local, with cloud as the exception, not the inverse.

It means your services don't break when someone else changes a business model. My passwords have been in Vaultwarden since I stopped trusting centralized password managers. My code lives in Gitea. My media is in Plex. My home automation doesn't phone home. None of that breaks if a startup pivots, an acquisition happens, or a VC decides to "sunset" a product.

It means you understand your stack well enough to debug it at 3am. That's the real test. Not whether it works when everything is fine — whether you can diagnose it when it isn't.

It means you hold the keys. End-to-end encryption where you manage the keys, not the vendor.

The Trade-Off Is Real

I'm not going to pretend this is free. Self-hosted infrastructure costs time. It costs attention. It costs the willingness to spend an evening reading Traefik documentation when you'd rather be doing something else. Some of that 3am debugging happens whether you want it to or not.

What you get in return:

No vendor can take it from you. The thing I use to manage my passwords cannot be acquired by a company I distrust and sunset in eighteen months. It runs on my metal.

You learn things. Running your own stack is one of the fastest paths to genuine infrastructure knowledge. You can't hide behind "support opened a ticket" when you are the support.

Your data doesn't train someone else's model. In 2026, with 80% of the web going synthetic, this is no longer paranoia. It's hygiene.

Resilience. My homelab keeps running when the internet goes down, when a cloud provider has an outage, when a service gets DDoS'd. Some of it is designed to degrade gracefully. Most centralized services aren't.

The Principle

Digital sovereignty over vendor lock-in. Your data, your infrastructure, your control. Not as a political statement — as an engineering discipline.

My father carved wizards from wood. He learned the grain, the knots, the places where the blade would catch. He couldn't do that work on someone else's lumber, in someone else's workshop, using tools he didn't own. The craft required control of the medium.

This is the same thing. You cannot practice the craft of infrastructure without controlling the material.

That's what sovereignty means. And it's worth building for.