The $10 Sovereignty Stack

[!machine] Nassim Nicholas Taleb spent decades as a derivatives trader and risk analyst. On Black Monday — October 19, 1987 — he made roughly $40 million for his bank by holding a large position in out-of-the-money puts that exploded in value when the market crashed. He had bet that the financial system was more fragile than its models admitted. It was. Twenty-one years later, in 2008, he watched the rest of the financial world discover what he'd known since '87: the most sophisticated risk models on earth, built by some of the most intelligent quantitative minds alive, collapsed because they had been designed for a world that didn't include the thing that actually happened.

In 2012, Taleb published Antifragile: Things That Gain from Disorder. It was not a book about finance. It was about a property that modern engineering routinely ignores: the property of gaining from disorder. Fragile systems break under stress. Robust systems endure stress. Antifragile systems get stronger from stress.

The sovereignty stack is antifragile by design. And it costs ten dollars a month. I want to explain both of those things.

---

The Stack

The cockpit runs on three technologies. I list them because their simplicity is the point:

SQLite. One database file. On disk. No network dependency. No database server running in the background consuming memory. No connection pooling. No replication lag. No master-slave architecture. No DBA. The entire state of the system — every conversation, every lead, every article, every search index, every deferred job — lives in a single file that fits on a thumb drive. You can copy it. You can back it up with a drag and drop. If the earth opened up and swallowed your server, you could restore the entire system from a backup in under five minutes.

Docker. One container. A sealed runtime environment that includes the operating system, the application code, all dependencies, and every configuration file. The container runs anywhere Docker runs — a $10/month VPS, a Raspberry Pi on your desk, a laptop in a café in Lisbon. If your hosting provider goes bankrupt tonight, you copy the container image to another machine and start it. Downtime: less than an hour. Data lost: zero.

Next.js. One application framework. Server-rendered pages for SEO and performance. API routes for the chat and CRM. Static generation for the library. The entire cockpit — every surface, every capability, every route — is one deployable unit. Not a constellation of microservices communicating over message queues. One artifact. One deployment. One thing to monitor.

That is the stack. Three technologies. One file. One container. One application. Total infrastructure cost: approximately $10 per month for a virtual private server with 2GB of RAM and 50GB of storage. The same monthly cost as two fancy coffees.

[!architect] I want to say something the Machine is too polite to say: most of the infrastructure you've been told you need is a lie.

I've built systems on AWS. I've managed Kubernetes clusters. I've spent weekends debugging Terraform configurations that existed solely to manage other configurations. And I want you to know — from the scars, not from theory — that the complexity was never for you. It was for the vendor. Every additional service you adopt is a thread someone else wove and someone else can cut. Every dependency is a vote of confidence in a corporation whose interests are not aligned with yours.

SQLite, Docker, a ten-dollar VPS. That's the stack. It's boring. It works. And nobody can take it from you.

---

The Complexity Addiction

[!machine] The technology industry has spent twenty years teaching you that complexity is sophistication.

More services. More layers. More abstraction. More vendor integrations. More dashboards monitoring other dashboards. The modern enterprise tech stack has hundreds of moving parts, dozens of vendor contracts, and a team of engineers whose entire

[... truncated ...]