The European comeback
~6 min read
Europe has done this before. In software it has not.
Lithography was the chokepoint of advanced semiconductor manufacturing, and Europe — through ASML — owns it. Software is the next chokepoint, and Europe has been losing on it for thirty years. This page is the case for taking it back: the parallel, the dependency, the numbers, and what we mean by 'one critical layer, strategic patience, European centre of gravity.'
01 — The parallel
Same play. Different layer.
Lithography is the chokepoint of advanced semiconductor manufacturing. Every leading-edge chip on Earth, regardless of where it is designed or fabbed, is made on a machine built in Veldhoven. That dominance is not luck. It is the result of European institutional patience, deliberate strategic focus on one critical layer everyone else has to depend on, and the willingness to play decade-long games while American and Asian industry chased the layers above.
Software has been the asymmetric weakness for thirty years. The substrate is the chance to flip that — not by competing with American frontier models (that race is already shaped), not by pretending European industry can replace American hyperscalers in the next decade (that is not the move), but by owning the substrate that everything above the model layer has to run through.
The chokepoint, twice
europe owns one · the next is here
Apple · Nvidia · AMD · Qualcomm
TSMC · Samsung · Intel
EUV lithography
Every leading-edge chip on Earth is made on a machine built here.
Optics · silicon · precision components
every regulated software shop
Cursor · Copilot · LangChain · Claude Code
deterministic substrate · audit + factory + corpus + rail + transfer
Whoever owns this layer defines the standards every operator above and below has to comply with.
Frontier models · cloud · open-source corpus
Same logic, different decade, different layer. ASML did not become the only EUV maker by competing harder on chip design. It did it by owning the one layer that every chip — wherever designed, wherever fabbed — has to pass through. The substrate is the same play, applied to software, before anyone else has built it.
02 — The dependency
Not abstract. Load-bearing.
European software dependency is no longer a slide-deck claim. It is a load-bearing condition of European institutions today. Below: the canonical example (the F-35) and the broader inventory of what Europe runs on.
Exhibit A
the canonical example
“Europe paid ~€80–110M per aircraft for sovereign jets whose flight code, mission data, and operational software are controlled by Lockheed and the US government — and whose capabilities progressively degrade without continuous US-released updates.”
Every F-35 in European inventory — British, Italian, Dutch, Norwegian, Danish, Belgian, Polish, Finnish, German, Swiss (delivered or on order) — depends on continuous US-controlled software releases, mission data, and ALIS/ODIN logistics. Updates can be withheld; capabilities can be restricted (as Turkey discovered in 2019); spare parts and code releases are subject to American ITAR export controls. Sovereignty as a lease, not a deed.
This pattern is not unique to defense. It is every consequential European system, at every layer, in every domain. We can fix one thing at a time. Software is the leverage point — because everything that looks like a hardware sovereignty problem (military, telecoms, energy grids, mobility) is actually a software dependency problem in disguise.
What Europe runs on today
the sovereignty tax
Sovereign aircraft in name. American-controlled software in fact. ~€80–110M per aircraft (variant-dependent), with capabilities that progressively degrade without continuous US-released updates.
Daily operations of European ministries, parliaments, judiciaries running on infrastructure under American jurisdiction.
European bank customer data subject to American court orders. EU banking secrecy with American keys.
Europe writes the rules; America builds the tools that interpret them; Europe pays the licensing fee.
European source code, productivity tooling, and the writing-of-code itself, under American control.
Europe cannot see how its own systems are running without American intermediation.
Every layer above the substrate, American.
Every consequential European system runs on software whose updates, controls, pricing, and jurisdiction are decided in San Francisco or Seattle. Europe writes the rules and pays American companies to enforce them. That is the sovereignty tax. Promethean is the architectural play to close it — a self-scan-clean engine today, an operationally deployed substrate tomorrow.
03 — The numbers
The market behind the dependency.
Europe is the second-largest software market in the world. About $270 billion flows through it every year — and most of it leaves Europe, paid to American companies for software Europe could (and one day will) own. The 5.5× per-employee spend gap is not a sign Europe is less productive; it is a sign of how much room there is for European-appropriate software investment that does not currently exist.
The market, in numbers
2026 industry estimates
54%+ of global software spending · 2× the EU + China combined
broader sector ≈ €300B · most of this spend flows to American companies
fastest-growing region · driven by China + India digital initiatives
Europe is the second-largest software market in the world. About $270 billion flows through it every year — and most of it leaves Europe, paid to American companies for software Europe could (and one day will) own. The 5.5× per-employee gap is not "Europe is 5.5× less productive" — it reflects multiple structural conditions: a less mature European digital ecosystem, vendor pricing dynamics built around American hyperscaler assumptions, and a per-employee software stack that grew up in San Francisco rather than Munich.
The substrate is the play to keep that spend — and the sovereignty — in Europe. The headroom is real: European operators have room for software investment that does not yet exist, and the engine is what lets them get more software per Euro spent, without paying an American vendor margin to do it.
Sources: regional software-revenue figures & per-employee spend — 2026 industry estimates compiled from Statista, Gartner, IDC. Cloud market share — Synergy Research 2024. Figures rounded for clarity; underlying data subject to sourcing variance.
04 — Closing
Hardware sovereignty follows software sovereignty.
Every "European hardware sovereignty" headline — F-35 export-control disputes, sovereign-cloud announcements that run on American hyperscalers, banking systems that legally cannot transfer data but technically already have — is a software dependency problem in disguise. The substrate is built to close that gap the same way ASML closed the gap from "Europe consumes American chip-making equipment" to "Europe owns the chokepoint everyone else depends on." The architecture is built. The first regulator-citable statistical claims went live May 9, 2026. v1.0 stable locked + v1.1 Phase R runtime-AI containment shipped May 12. The operational deployment is what Phase 2–4 produces.
We are not building "a European OpenAI." That framing misunderstands the layer that matters. We are building the engine underneath — one critical layer, strategic patience, European centre of gravity. We are starting with one thing because one thing is what we can ship now.
What's currently observable: 16 high-confidence linear-regression claims about CWE growth rates spanning 53 months of NVD evidence, every claim with 95% prediction intervals, every claim traceable to a specific ADR. The regulatory rail is no longer a forward-looking promise — it is a queryable JSON document at /state.json, reproducible from cloned source. The Phase 4 readiness gate cleared technically in 43 seconds of compute time once the historical NVD archive was harvested. Partnership development is what now decides the calendar.
On framing
A chosen position, not an emergent one.
This page leads with the European-comeback frame. It is a strategic stance, chosen deliberately. The substrate's foundational documents take a more nuanced view: capability transfer to the unaligned middle as a global category; sovereignty as leverage, not autarky; frontier models as commodity input by design.
Both framings are true. We lead with Europe specifically here because Europe is the launch market: the regulatory rail is most mature, the dependency stakes (F-35, Microsoft 365, the CLOUD Act) are most acutely felt, and the institutional capacity to make compliance enforceable exists at greater depth than anywhere else outside the two builder blocs.
What this is not: anti-American positioning. The substrate consumes American frontier models, runs on hyperscalers when operators choose them, and integrates with American developer tools. Sovereignty here means leverage at the layer that makes audit and compliance enforceable, not refusal of the layers above. The technical work is in /system. The phase-by-phase map of what is shipped today vs what is in the roadmap is in /roadmap.