What will it take to build an open source Europe and how the Digital Commons EDIC can help

2026-10-14T14:00:00+00:00

The French and German ministers opened the DGE open source event.</p> </figcaption> </figure>

🔗</a>1. Build a European community</h2>
The EDIC plans to build a thriving, trusted ecosystem of open source actors, collaborating with existing open source communities and ultimately “connect[ing] deployment experience with development priorities”. That covers sharing knowledge, promoting success stories, and favouring collaboration over duplication.</p>
Whilst open source communities are used to such collaborations, the intergovernmental status of the EDIC means it could go well beyond community management and take inspiration from intergovernmental bodies in other sectors. The World Health Organization (WHO), for example, makes it easier for UN procurement agencies to make choices aligned with its quality, safety and efficacy recommendations by maintaining a list of ‘pre-qualified</a>’ medical products, as well as setting international norms and standards (such as on which medicines are ‘essential’</a> to a functioning health system). WHO also coordinates relevant actors for health emergencies, such as disease outbreaks</a>; and provides forums</a> where governments and other stakeholders can seek consensus solutions for shared challenges.</p>
Now replace “health” with “digital sovereignty” in the paragraph above and see how, beyond ensuring that the EU Member States collaborate and share experiences, the DC-EDIC could become a place of:</p>

Guidance and trust</strong>, for example by providing the tools to make appropriate choices (think pre-qualification).</p> </li>

Standard setting</strong>, by promoting best practices including the convergence towards open standards (think essential medicines).</p> </li>

Coordination</strong>, in particular around problem solving and funding (think outbreak response and governance forums).</p> </li> </ol>
Here is how the EDIC could take on these roles.</p>
🔗</a>1.1 Build a trusted ecosystem</h3>
Just as WHO provides guidance on ‘essential’ medical products, the DC-EDIC could host an index of projects and vendors that shows how each project relates to its forks and successors, and celebrates those who contribute back. We actually worked with Grist</a> to put together a proof of concept of such an index which can be found here</a> and we called Trusted Vendor Authority (TVA).</p>
🔗</a>1.2 Support the independent governance of digital commons</h3>
True digital sovereignty benefits from an independently governed commons. There are different models for doing this, but non-profit foundations such as the Python Software Foundation</a> and The Matrix.org Foundation</a> could provide a helpful starting point. These organisations provide administrative and governance support for their projects and protocol. The EDIC could:</p>

Provide guidance to Member States’ procurement on integrating governance funding into their framework, or advise law makers on the importance of the same</p> </li>

Create or support the creation of a home for essential but small open source projects that lack this kind of foundational oversight</p> </li>

Provide guidance on best practice in open source governance</p> </li>

Financially support the governance of projects which are key to Europe’s digital resilience</p> </li> </ul>
However, few users realise that this independence needs sustainable funding to last.</p>
🔗</a>1.3 Train decision makers and buyers in open source procurement</h3>
Procurement is one of the biggest hurdles the ecosystem faces: decision makers need to understand why open source matters, how to buy it, and why the best way to keep open source free is to financially support the upstream developers. The EDIC could become the reference source of guidance for different types of buyers, covering what open source brings to sovereignty, privacy and cost savings (backed by the evidence described below), and matching solutions with buyers’ needs.</p>
🔗</a>1.4 Identify challenges that all Member States share</h3>
All Member States need to solve the same issues, which makes the DC-EDIC the obvious place to find joint solutions and fund them together (see pooled funding below).</p>
🔗</a>2. Open access to funding</h2>
The institutions who can most benefit from switching their technology stack to free and open source software – governments, health insurers, civil society organizations – are often resource-constrained and might struggle with operational, cost, and expertise hurdles. The DC-EDIC can help in four ways:</p>
🔗</a>2.1 Fund and guide migration to open source</h3>
The EDIC should provide operational guidance to organisations switching to open source and, through the European Sovereign Tech Fund (EU-STF)</a>, provide financial support or even seconded experts to help them migrate. The EU-STF is one of the first two projects tackled by the DC-EDIC and was kicked-off in June as a pilot.</p>
🔗</a>2.2 Fund usability, security and compliance so digital commons can scale</h3>
Open source projects that fail to displace their vendor-locked equivalents usually stumble on the same hurdles: their usability cannot compete, or they cannot shoulder security and compliance requirements (CRA, accessibility, audits…). Promotion and ecosystem management matter too, but a user-friendly commons can grow organically without them, as VideoLAN’s VLC shows. Usability, security and compliance work could be funded by existing programmes, but it also fits squarely within the EU-STF and the DC-EDIC mission. On security, the EDIC could even play the role WHO’s pathogen surveillance network plays for outbreaks, coordinating how Member States spot and respond to vulnerabilities in the commons they share.</p>
🔗</a>2.3 Support the development of full stack solutions</h3>
For most end-users, technology that works ‘out of the box’ lowers barriers to entry. France’s LaSuite</a>, Germany’s OpenDesk</a> and the Netherlands’ MijnBureau, replacements for Microsoft 365 that use Matrix clients as their communications components, are good examples. The recent Horizon Europe calls on the creation of an Open Internet Stack will also help; the EDIC could use the European Sovereign Tech Fund to support the creation of similar projects.</p>
🔗</a>2.4 Pool funding across Member States</h3>
A true common is used across most of the Member States, which share similar needs, and may all want to fund its support or development. But no open source project can align the procurement processes of a dozen public administrations, in practice, it is lucky if funding from even one gets through. By acting as a crowdfunding platform for governments, the DC-EDIC could pool these resources.</p>
🔗</a>3. Sustain the components everyone depends on</h2>
Open source infrastructure is, as the EDIC recognises, chronically underfunded. Just as WHO’s essential medicines list tells health systems what they cannot do without, the EDIC could list the digital commons Europe depends on and make sure they are funded. Beyond the governance support described above, it could tackle two additional challenges.</p>
🔗</a>3.1 Fund guardianship</h3>
Matrix is a good example to understand why this matters. It carries the communications of civil servants across Europe: in Germany, BundesMessenger</a> and openDesk</a> serve the public administration; in France, Tchap</a> has been mandatory for all civil servants since August 2025; Swedish agencies are leveraging the interoperability of Matrix-based apps</a>; Belgium uses BEAM</a>, Luxembourg (LuxChat</a>), Poland (Merkury 2.0</a>), and Austria’s healthcare system and Switzerland’s postal service rely on it too. All of them chose Matrix because, as an open standard, it breaks vendor lock-in. Yet only one government agency, France’s Directorate for Digital Affairs (DINUM), has joined The Matrix.org Foundation as a member to support the core specification all these national governments rely on, and only since October 2025. The DC-EDIC could close this funding gap by supporting the organisations that independently maintain specifications and protocols, promote them and keep their ecosystems diverse and alive: the backbone of any digital common.</p>
🔗</a>3.2 Help digital commons become financially self-sufficient</h3>
Most open source funding goes to new technology, yet maintaining what we already rely on matters at least as much. Funding maintenance work via grants can carry its own pitfalls: critical commons become dependent on the next round of applications to continue their work. The better goal is self-sufficiency: helping commons gather resources from their own users to fund maintenance and reduce their “bus factor” (the risk that a project stalls if a few key people leave). The EU-STF can target exactly that, for example by getting commons to set up a recurring revenue stream such as Foundation membership, alongside educating the industry on how to support the commons it uses.</p>
True digital sovereignty requires interoperability and independent standards. Those standards must be sustainably financed for both proper maintenance and continued independence.</p>
🔗</a>4. Bring deployment evidence to policymakers</h2>
The EDIC will support policymakers seeking to implement new regulation, or transition their operations to open source solutions. It can do this in four ways:</p>
🔗</a>4.1 Gather deployment data across Member States</h3>
The DC-EDIC makes it easy for all the participating Member States to compare notes on which tools and technologies they use. Much as WHO’s Global Health Observatory turns national data into shared evidence, this data is gold dust for policymakers who need to see the reality on the ground.</p>
🔗</a>4.2 Commission studies on the real cost of proprietary software</h3>
Proprietary software is expensive, but exact figures on what EU governments spend are hard to come by. One indicative data point: the German federal government reportedly spent €481.4 million on Microsoft services in 2025</a>. Evidence gathering that can identify more data points, offer a comparative analysis of long-term cost differences between using e.g. Microsoft Office vs OpenDesk (or other interchangeable tech stacks), and teasing out potential savings could help organisations make the decision to migrate or not. A calculator of migration costs and savings over time would be a useful tool for CFOs and policymakers.</p>
🔗</a>4.3 Publish policy briefs on privacy and security</h3>
Governments and regulated industries have a duty of care to safeguard the privacy and security of the data that they handle. Proprietary software solutions have not always held up their end of the bargain in meeting this duty. For example, in March 2024, the European Data Protection Supervisor found that the European Commission’s use of Microsoft 365 infringes the EU Data protection law.</a> In early 2026, France banned</a> its civil servants from using Zoom, Google Meet, Microsoft Teams and other US based platforms, in the name of data sovereignty (as mentioned above, the use of Matrix-powered Tchap was already mandated). Plenty of data exists on privacy and security, but it is rarely accessible to non-experts. Short, clear policy briefs showing which solutions can guarantee security, compared with common proprietary alternatives, would offer both guidance and reassurance.</p>
🔗</a>4.4 Create a one-stop clearing house for essential information</h3>
This would bring together the trusted index of projects and vendors described above, information that helps bridge different solutions, and normative templates and other guidance documents (on migration, for example).</p>
🔗</a>5. Run concrete projects</h2>
The DC-EDIC plans to run 100-Day Challenges that produce working open source software. This is exciting and needed. We suggest that in addition to software development projects, the EDIC runs concrete, time-bound projects to address some of the contextual pieces needed, as mentioned above: pricing studies, policy briefs, the trusted index of projects and vendors, and the list of essential digital commons that should get maintenance support. New software matters, but where the EDIC can play a pivotal role is the context around that software: governance, expertise, and guidance for adoption.</p>
🔗</a>Why the DC-EDIC should act as a beacon, not a software producer</h2>
The DC-EDIC's unique value-add is in governance, not in software production. It has the power to convene the organisations with shared needs, and distil them for the benefit of the open source community.</p>
Europe already has plenty of talented open source builders, what the EDIC can uniquely do is act like a reference point, taking on the unglamorous work that keeps everyone’s lights on. WHO does not manufacture medicines; but it provides guidance on which ones are essential, and where they can be sourced from trusted manufacturers. The DC-EDIC can do the same for digital commons: help Europe choose with confidence, set the standards worth converging on, coordinate when problems are shared, and fund the components we all depend on.</p>
Matrix’s journey from a small open standard to the backbone of government communications across Europe shows both how far digital commons can go and how fragile they remain when nobody funds their guardians. The DC-EDIC is the best chance yet to change that, and The Matrix.org Foundation is looking forward to helping.</p>
In the meantime, The Matrix Conference</a> next week (20-23 October 2026) will be a great demonstration of how far the project has come: all stakeholders in the ecosystem will be gathered in Malmö, Sweden, to show off their work, share knowledge and collaborate. The conference features no less than two full days focused on the public sector Matrix ecosystem</a>. NATO, the UN, the European Commission, as well as representatives of the majority of the countries running Matrix, which were mentioned above, will make it on stage to share more about their deployments. The Matrix Conference is the main event for the Matrix ecosystem and we are looking forward to seeing both new and old friends there! A few tickets are still available</a> but hurry before they run out!</p>

Matrix.org - Advocacy

What will it take to build an open source Europe and how the Digital Commons EDIC can help

The European Union must keep funding free software