· 2 min read

Open Code has no Nationality.

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.

Open Code has no Nationality.
Open Code has no Nationality

Europe just started a fight over two kinds of sovereignty. The kind that builds walls, and the kind you can read, run, and trust.

Yesterday the European Commission unveiled a package of new laws meant to cut Europe's dependence on American technology. A senior EU official called it "Tech Liberation Day".

A few hours later, someone who lobbies for the big tech companies called his own industry's response to it "one of the saddest press releases I've ever worked on".

Same announcement. Two completely opposite reactions. The gap between them tells you almost everything.

So I spent yesterday reading the actual press release and the strategy documents behind it, not just the headlines. Here is what is really going on.

Start with the scale of the problem. By the EU's own reckoning, Europe gets more than 80% of its digital products and services from companies based outside the bloc. That is the hole this whole package is trying to climb out of.

For years, the official answer to that was mostly theater. "Digital sovereignty" meant renting a data center on local soil and calling it independence. This package finally drops the pretense. At its center is an open source strategy built on one simple idea: public money should buy public code. Software the state can read, run, and host itself, owned outright instead of rented from a company on the other side of an ocean. It even proposes a fund to pay the unpaid volunteers who quietly keep the world's critical software running.

Now, there is a fair objection coming, and it is worth taking seriously. Isn't this just protectionism? If Europe walls itself off and backs its own national tech giants, doesn't it split the internet into separate camps that stop working together? That worry is real. One version of "sovereignty" would do exactly that.

But it is not the only version on offer, and the difference between the two is what the next 18 months are really about.

Open source is not a wall. Open code has no nationality. Anyone can read it, run it, check it, and build on it. A government running open software it controls is free of any single vendor, and still works fine with everyone else. That is independence without cutting yourself off from the world.

Which is exactly why the lobby is unhappy. It is also the part most likely to get quietly watered down over the next 18 months, or left as a nice-sounding goal instead of a rule governments actually have to follow.

So watch for the trick. It even has a name now: sovereign-washing. A "sovereign" label slapped on the same old dependence, with nothing underneath it actually changed.

The direction is finally right. Almost all the hard work is still ahead.

So the real question for the next 18 months is not whether Europe believes in sovereignty. It is which kind wins. The kind that builds walls, or the kind you can actually read, run, and trust.

Which one are you fighting for?

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