· 2 min read

Open Source doesn’t fail on the code. It fails at 2am.

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.

Open Source doesn’t fail on the code. It fails at 2am.
Open Source doesn’t fail on the code. It fails at 2am.

So I built the directory of who to call. Five providers, live now.

Open source rarely fails on the code. It fails on the phone call you can't make when something breaks at 2am.

That's the gap I've spent the last months closing.

The software is the easy part. It's free, it's auditable, you can walk away from it any time. The hard part is finding someone accountable to deploy it, run it, and pick up the phone when it matters.

Without that, "digital sovereignty" stays a slide in a strategy deck. Nobody stakes a hospital or a school district on software with no one to call.

So today I'm opening the Service Provider layer of OpenTechHub: a directory of verified companies that build, host, and support open source, so the organizations that want out of vendor lock-in have somewhere to turn.

Five providers are live at launch. Each one earned it. Let me introduce them:

Four are in Europe, one is in India, and that mix is deliberate. When software is genuinely open, auditable, self-hostable, and yours to leave whenever you want, where it was built matters far less than how it was built. A tool made on those principles in India can serve a European hospital as well as a local one. So this map won't stop at Europe.

To each of the five: thank you for betting on this early, when it was still a promise and a pitch. You made the directory real. And to everyone who talked it through with me, tested it, and pushed back: you know who you are. This doesn't happen without you.

If your company builds, hosts, or supports open source, a few slots in the free pilot are still open. Learn how to get listed here.

The tools to run an organization without surrendering control already exist. What has been missing is the map of who can help you use them. That is what I am building.

Read next

A roller conveyor in a dim warehouse carries a long row of identical new cardboard boxes. Among them ride a few old, crumpled boxes patched with tape, one in sharp focus at the center.
Article Open Source Digital Sovereignty

The fix is out. Is it in?

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.

Kai A. Hartung
Kai A. Hartung
· 2 min read
A long till receipt listing licences, cloud, add-ons and contractors, torn off just below the word TOTAL.
Article Open Source Digital Sovereignty

The bill nobody can add up.

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.

Kai A. Hartung
Kai A. Hartung
· 6 min read
Mock AI model page labelled "Open Source" but marked "not an open release," with a locked, disabled "Request access" button and a "Sold via a private cloud" sticker.
Article Open Source Digital Sovereignty

Open in name only.

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.

Kai A. Hartung
Kai A. Hartung
· 2 min read