Search for a command to run...
Series
How cloud dependency became the default — and what it takes to build systems you can actually leave.
A seven-chapter series on cloud dependency, sovereignty, and the architecture that makes exit possible. From the build-vs-buy trade-off through jurisdictional risk, the work of regaining control, and the platform shift AI workloads are now forcing.
| # | Chapter | Status |
|---|---|---|
| 1 | The Old Trade-off — Vendor vs. In-House Before AI Changed the Rules | ✅ Published |
| 2 | Two Races at Once — Why AI Is Both a Security Emergency and a Competitive One | ✅ Published |
| 3 | The Sovereignty Illusion — What Companies Get Wrong About Cloud Independence | ✅ Published |
| 4 | You Can't Govern What You Can't See | 🚧 Coming soon |
| 5 | The Architecture of Exit | 🚧 Coming soon |
| 6 | Built for the Wrong Workload | 🚧 Coming soon |
| 7 | Orchestrating the Agents | 🚧 Coming soon |
This is the first chapter of Built to Leave, a series on cloud dependency, sovereignty, and the architecture that makes exit possible. The series follows the problem from its origins — the build-vs-bu
This is the second chapter of Built to Leave, a series on cloud dependency, sovereignty, and the architecture that makes exit possible. The series follows the problem from its origins — the build-vs-b
This is the third chapter of Built to Leave, a series on cloud dependency, sovereignty, and the architecture that makes exit possible. The series follows the problem from its origins — the build-vs-bu
