Critical analysis, migration playbooks, and governance guides. Curated insights for decision-makers building the sovereign open enterprise.
Open, capable, sovereign: in AI you get to pick two. The frontier models are proprietary and revocable, the open ones you cannot run or cannot match, and even Europe's champion runs on chips it will never make. Sovereignty is not the model you pick. It's the weakest layer beneath it.
"Buy European" has become Europe's answer to digital dependence. But a European vendor is one acquisition away from being American, and hosting on home soil won't stop US law. Real sovereignty isn't where your software comes from. It's whether you can leave it.
Every digital sovereignty talk ends the same way: set up an OSPO, and the idea gets filed under someday. But the office is not the point. It is a container for the jobs your vendor used to do, priced into the license fee and now yours to own. Name who owns them and you are ahead of most.
Google published the Open Knowledge Format, an open, vendor-neutral way to hold the knowledge your AI reads: nothing but text files. Then it bundled its own tooling beside it, every piece pointing back to Google Cloud. The format is worth taking. The strings are worth cutting.
Digital sovereignty is not a product you buy. It is a stack of unglamorous decisions about where your data lives. A personal look at the foundation layer beneath the apps, the storage, code, formats and backups, and why that is where your freedom actually lives.
On June 17, Germany and France signed a joint definition of digital sovereignty. Every past attempt, from Quaero to Gaia-X, died the same way: a fight over whose national champion wins. This time there is nothing to own. They are writing the rules instead, which bind all 27 EU members, not two.
Euro-Office launched as Europe's sovereign alternative to Microsoft 365. Then it made Microsoft's OOXML the default format, not the open ODF standard. Why that default quietly hands the document layer back to Microsoft, and why open formats, not European servers, are the real test of sovereignty.
Europe just unveiled its long-delayed tech sovereignty package. Even a big tech lobbyist found opposing it dispiriting. The real fight now is between two kinds of sovereignty: the kind that builds walls, and the kind you can read, run, and trust.
A Dutch 'sovereign' cloud almost became American overnight, and only a last-minute government veto stopped it. Real digital sovereignty was never just about where your data sits. It is about whose courts can reach it, and Europe's billion-euro plan still misses the point.
96% of commercial software depends on open source. The value it creates: $8.8 trillion. A third of the developers maintaining it are unpaid. A practical framework of six shifts to move from extracting value to sustaining the ecosystem your organization depends on.
Google is shutting down Gemini CLI and replacing it with a closed-source tool. 100,000 stars, 6,000 contributions, hundreds of volunteers. Enterprise customers keep access. The community that built it gets 30 days. When the value lives in a proprietary API, even forking cannot save you.
Digital sovereignty projects don't fail because of the technology. They fail because someone swapped the software without rebuilding what it sits on. A four-layer framework drawn from Denmark, France, Germany, and Spain shows why the sequence matters more than the stack.
Most people stick with one AI provider because trying alternatives is friction. OpenCode Go changes that: one interface, any model. DeepSeek V4 Pro and Kimi K2.6 are delivering results that required premium subscriptions a year ago. The barrier to exploring is gone.
The NHS survived hostile state attacks on its open-source pandemic app with zero critical breaches. Now it ordered every team to hide their public code in one week. AI was the justification, not the reason. When a taxpayer-funded health system abandons transparency, that's a democratic decision.
Almost 90% of the world's software supply chain relies on a single platform. Microsoft folded GitHub into its AI division. The engineers who built on it are walking out, and open source is going sovereign.
Anthropic pulled Claude Code from its $20 plan and reversed course within days, but the signal matters more than the reversal. Every major AI tool is sold below cost. When subsidies end, every workflow built on rented AI becomes a cost you didn't budget for or a capability you lose overnight.
AI didn't break the code; it broke the economics. Hallucinated bug reports, spam pull requests, and a verification tax are overwhelming unpaid maintainers. Projects are closing their gates. If your stack depends on open source, upstream project health is now a board-level concern.
France ordered every ministry to submit a Microsoft transition plan by autumn 2026, while Education just signed a €152M contract through 2029. The obstacle isn't political will. It's twenty years of legacy software nobody budgeted to rewrite.
Scientists from CERN built an encrypted email service in 2014. Twelve years later, Proton is a full open-source workspace (every app audited, every byte encrypted), taking on Google and Microsoft at 100 million users.
Germany built an AI tool for planning approvals, won 'Best AI Use in Government Services' at the World Government Summit, and published the full codebase under Apache 2.0. Public Money, Public Code: in practice.
Euro-Office forked OnlyOffice for digital sovereignty, and hit a licensing dispute before shipping a single release. If the legal foundation isn't as robust as the technical one, you're building on sand.
Germany's Deutschland-Stack mandates ODF as a binding standard, because open file formats, not open source software, are the non-negotiable foundation of digital sovereignty.
AI has grown the developer base 50% in three years; 53.9% of AI-generated code is tangled. Why that (and EU sovereignty mandates) demands a new Git approach.
Jan AI runs every prompt on local hardware with zero telemetry, an open-source ChatGPT alternative that shifts enterprise AI from variable cloud OpEx to fixed CapEx.