§01/OWN-THE-PERIMETER
Sovereignty
Writing on owning the stack you depend on — cloud exits, bare metal, self-hosted platforms, and the engineering that removes invisible landlords.
Sovereignty is the largest body of writing here because it is the one every other pillar eventually leans on. The through-line is not that managed services are bad — it is that a dependency you cannot inspect, recover, or leave is a liability you have not priced. Most of these articles start from a specific rented layer and work out what owning it actually costs in engineering hours, hardware, and on-call load.
Read them as engineering documents rather than position pieces. Where a claim is load-bearing it is tied to a control, a benchmark, or a regulator's text, and where self-hosting is the wrong answer the article says so. If you are evaluating a move rather than executing one, the repatriation playbook and the build-vs-buy framework are the two that will tell you fastest whether the rest is worth reading.
Start here
Cloud Repatriation: The Kubernetes Engineering PlaybookThe end-to-end shape of a cloud exit, with the costs that usually go unbudgeted.
Deciding whether to leave at all
The framing work that comes before any migration: what sovereignty means as a testable property, what the European market actually offers, and where the legal ground has already shifted under existing architectures.
Owning the substrate
Bare metal is where sovereignty stops being a policy word and becomes a provisioning problem. Machine lifecycle, immutable hosts, ingress without a cloud load balancer, and storage you can actually restore from.
Running AI without exporting your data
Inference is the newest rented layer and the one with the least considered exit. Capacity planning, serving in production, gateway-level residency control, and retrieval that stays on your side of the boundary.
Jurisdiction, residency, and the regulator
Where data physically sits is an architecture decision with a legal consequence. India's DPDP and CERT-In regimes, government-cloud empanelment, and the EU instruments that increasingly assume you can prove residency.
All 83 articles expressing this pillar
Executive Briefing
Thirty minutes to clarify your infrastructure risk
Walk us through your vendor footprint and regulatory constraints. We will tell you honestly where sovereignty creates leverage — and where it does not. No pitch deck. No obligation.





































































































































































