Critical analysis, migration playbooks, and governance guides. Curated insights for decision-makers building the sovereign open enterprise.
Almost four years after a free fix shipped, about one in eight Log4j downloads was still a vulnerable version. Now AI has bank regulators counting the days. Why private copies slow the fix down, what the banks' new alliance changes, and the question to ask your IT team.
The Dutch government has a Linux desktop on trial, no new money for its digital autonomy plans, and no total for what it pays Microsoft. Leaving shows up as line items someone must sign for. Staying hides in budgets nobody adds up.
Germany spent public millions on a "Sovereign Open Source" AI, then gated it and let a vendor sell it. Switzerland and the Netherlands show the difference: real openness is a mandate, not a label.
The year's most hyped AI model arrived with 40 million dollars and a wall of attention. Within days, open versions you can download and run yourself already existed. Here is what the celebration missed, and why it matters for digital sovereignty.
A new fee finally asks companies to pay for the open source they profit from, then hands them a legal way not to. Why it runs on goodwill, bills hardest the ones least able to dodge it, and what a working funding model still has to solve.
When you leave a proprietary vendor, you inherit the jobs it used to do: governance, legal, security, and giving back. Use our new free tool, the OSPO Roadmap, to map those jobs, track where you stand, and name who owns each. No login. Live now.
An office suite just set an all-time download record for what it left out. LibreOffice 26.8 hit 1,031,162 installs in a week with no AI, and a million people were escaping the feature Microsoft keeps adding to yours. In rented software, the next change is never yours to make.
Open source rarely fails on the code. It fails when something breaks and no one is accountable to call. Today I'm opening OpenTechHub's Service Provider layer: a directory of verified companies that build, host, and support open source, so anyone leaving vendor lock-in has somewhere to turn.
What pays back the most asks the least of your engineers. The most valuable way to contribute to open source
Most companies quietly maintain their own private copies of open source software, and the upkeep costs far more than anyone puts on the books. The Linux Foundation measured the bill. Contributing your changes back is the cheaper path, and this is why forking almost always loses.
Open source is not the opposite of paying for software. Four business models hide behind one label: foundation-run, open core, source-available, and support-funded. Buy a stack and you inherit all of them. What breaks on day two, and the four questions to ask before you sign.
Microsoft built a sovereign German cloud and locked itself out of it. Customers left anyway. The real premium was never just the money, it was capability, and Europe is now writing its cloud sovereignty law around a gap it never closed.
A frontier open model now runs on a desktop. It writes five words a minute. I tested a smaller one on my own machine and it ran slower than someone reading aloud. Running these models yourself is real. It is a fire escape, not a workplace, and there is no third state between working and gone.
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.