Most of an architecture is settled in procurement rather than in design. I have spent fourteen years on both sides of that table, building the platforms and running the migrations that have to work afterwards.
What I write about here is digital sovereignty, meaning what an organisation can still run, change and prove once the outside connections go away. Almost nobody tests that, which is the part I keep returning to.
Digital sovereignty
A series on keeping control of infrastructure you don’t fully own, and on testing whether you have it.
- Sovereignty Is a Control Boundary, Not a Location January 2026
- In China, Someone Else Operates Your Cloud 2019
Cloud and infrastructure
- Multi-Cloud and Omni Cloud Are Not the Same Thing 2023
- Developer Autonomy Is a Platform Decision 2022
- Azure Governance Never Finishes 2019
- Security Questions to Settle Before a Migration 2019
Security
- The Gap Where the Provider’s Responsibility Ends 2022
- Smart Cities Need Their Own Security Model 2022
- AI Arms Both Sides of Security 2019
- Four Azure Tools for Securing What You Run 2019
- Cryptography in a Post-Quantum World 2019
- What Quantum Computing Does and Does Not Threaten 2019
- Cybersecurity on the Blockchain 2019
Emerging technology
- Coco Is a Framework, Not a Ledger 2018
- Blockchain After the Cryptocurrency Hype 2019
- AI Moved Fraud Detection Into Real Time 2017
- Smart Contracts and ‘Code Is Law’ 2019
Technical notes
Azure, PowerShell, Active Directory and AirWatch, from 2017 and 2018. Browse the notes →
Ulv Bjørnsson 