Ideas on sovereign, business-driven technology
Practical thinking on enterprise architecture, EU data sovereignty, Kubernetes, and compliant automation — from the work we do every day.
Denmark's shelved Office pilot: sovereignty needs results, not just first steps
Denmark quietly dropped its Collabora pilot without an evaluation – a lesson in how to design sovereignty pilots that actually teach you something.
Read moreContracts signed before 1 October: what Sweden's new NIS2 rules ask of your suppliers
New Swedish NIS2 regulations require operators to revisit existing supplier contracts – and the clauses only work if your architecture lets you use them.
Read moreWhich sovereignty level do you actually need? Preparing for CADA's four assurance levels
Sweden's consultation responses on the EU Cloud and AI Development Act show everyone wants sovereignty but few want to pay – classifying your workloads against the four assurance levels now is the cheapest way to prepare.
Read moreKubernetes 1.34 is end of life – make your next upgrade boring
Kubernetes 1.34 stops receiving patches on 27 October 2026 – a good moment to turn cluster upgrades from a project into a routine.
Read morePHP2Shell: the patch is easy – finding PHP in your containers is the real work
Two critical PHP core flaws show that in a container platform, response time depends on knowing what runs where – not on the patch itself.
Read moreResilience is not sovereignty – three questions to ask your cloud provider
AWS is disconnecting its EU cloud and Microsoft is adding European oversight – good steps, but sovereignty comes down to jurisdiction, control and portability.
Read moreAWS is unplugging its EU cloud from the US — what it proves, and what it doesn't
On 24 October AWS disconnects its European sovereign cloud from its global network. The test shows technical resilience — but not the question that decides it for healthcare and the public sector: who can legally reach the data.
Read moreWhy change should be business-driven, not IT-led
Every system, tool, or purchase should answer a business requirement — not land because someone thought it was clever. When the business drives change, you stop shipping things nobody asked for.
Read moreEU digital sovereignty: what it actually means for your cloud
Sovereignty is not a checkbox or a data-centre location. It is about who can compel access to your data — and designing so the answer stays in Europe.
Read moreOne cluster per solution wastes what Kubernetes gives you
Kubernetes strips the operating-system overhead from every app, and for stateless workloads the disks and backups too. Run a cluster per solution and per environment, though, and you throw away its biggest win.
Read moreKnow every application you run — or pay for it twice
If you can't list the applications you run, you can't know which capabilities you already have — and you end up buying the same one twice. Keep the catalogue where your service management lives.
Read moreThe roles that keep a delivery team shipping
With many developers, clear roles are what keep delivery predictable: a product owner close to the business, two kinds of project manager, and a spec that's settled before it reaches the team.
Read more