§04/EXIT-RAMPS-DESIGNED-IN
Optionality
Writing on exit ramps designed in — portable data formats, vendor-neutral architecture, and migrations that are a planned quarter, not a rewrite.
Optionality is the cheapest thing to design in and the most expensive to retrofit. These articles are about keeping the cost of changing your mind bounded — choosing formats, protocols, and boundaries such that replacing a component is a scoped quarter of work rather than a rewrite with a business case attached.
The recurring test is simple: for each layer you depend on, can you name the replacement, the data you would have to move, and roughly what the move would cost? Where that question has a clean answer the writing focuses on the migration mechanics; where it does not, the article is usually about why the lock-in is structural and what to do instead.
Start here
European Sovereign Cloud: Build, Buy, or Self-Host FrameworkA decision framework for build, buy, or self-host — and where each one quietly costs optionality.
Data gravity is the real lock-in
Compute is portable and state is not. Analytics, object storage, block storage, and the relational tier — the four places where leaving gets expensive, and the formats that keep the bill finite.
Owning the pipeline that builds you
CI and the registry are load-bearing dependencies that rarely appear on a risk register — until a runner queue, a rate limit, or a pricing change stops your releases.
Portable runtimes and fleet shapes
Architecture choices that keep workloads movable: portable execution, disconnected and edge fleets, tenancy that consolidates without welding tenants together, and GitOps that survives cluster count.
Exits taken, and what they cost
Migrations written up after the fact rather than proposed in advance — identity, event streaming, mesh networking, and a full move back off the cloud.
All 68 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.







































































































































