The EU Open Source Strategy

What has changed

The European Open Source Strategy, set out as part of the wider Technological Sovereignty Package, recognises open source as a lever for sovereignty rather than an alternative to commercial software. It rests on a clear economic case: the order of EUR 264 billion spent each year on mostly non-European proprietary IT, and dependence on non-EU suppliers for over 80% of digital products, services and infrastructure.

Several commitments matter for any organisation that consumes, contributes to, or stewards open source.

Public sector as anchor customer

An open source-first principle in public cloud and AI procurement, alongside a "public money, public code" reuse expectation on software the public sector buys, and guidelines for tenders that allow open source to compete on equal terms.

Maintenance and continuity

An Open Source Maintenance Instrument for sustained funding, including a European capacity to fork projects and a contingency programme for mirroring source code and packages - addressing the funding gap that opens once a project moves past its early stage.

Stewardship and foundations

A stewardship toolkit for establishing EU foundations, support for a European Digital Public Infrastructure Steward Organisation alongside the Digital Commons EDIC, and a study into a single set of rules under which foundations could be governed across the Single Market.

Delivery through the Digital Commons EDIC

The DC-EDIC features as a concrete delivery partner across the strategy, including a target of at least 30 million active users by 2030 for open source collaboration, productivity, messaging and secure email tools.

What it leaves open

The strategy is, for most organisations, enabling rather than mandating. The single firm obligation falls on Member State governments, which must carry out sovereignty risk assessments to establish which administrative use cases require which level of sovereignty. Everything else - catalogues, accelerators, assessment tools, funding instruments - creates options and conditions rather than requirements.

Significant questions are deferred. The strongest procurement language sits within the cloud and AI scope rather than in the horizontal procurement directives, so the underlying legal uncertainty around requiring open licensing is not yet resolved. Foundation governance is routed to a feasibility study rather than settled. And the funding envelope - in the order of EUR 1 billion over seven years - is modest against the dependency it is meant to redirect. The instruments exist on paper; their governance, sequencing, and operational design are still to be built.

What implementation requires

This is the gap Open Digital works in. A commitment to open source-first procurement is not the same as a procurement process that delivers it. A maintenance instrument is not the same as a sustainable foundation that can receive and account for funding. An assessment framework is not the same as an operating model an administration can run.

For public administrations and the digital agencies acting on these commitments, the practical work now is in procurement design, governance and contributor frameworks, foundation sustainability, and the sequencing of adoption programmes so that delivery matches intent.