Summary Under the proposed Cloud and AI Development Act (CADA), the European Commission would establish and maintain a centralised EU Open Source Solutions Catalogue (EU OSS Catalogue) to solve the fragmentation of public sector software. As proposed in Article 43(1), this catalogue serves as a single entry point to access software made available for reuse by Union entities and public sector bodies. Hosted on the Interoperable Europe portal and accessible free of charge, the platform would allow any public administration to search for, discover, and reuse existing open-source solutions, fostering a "one-stop-shop" for European digital public goods.

Detail

The proposed Cloud and AI Development Act (CADA) introduces a comprehensive framework to promote the use of open-source software within the European public sector, aiming to reduce vendor lock-in, enhance transparency, and strengthen technological sovereignty. A cornerstone of this strategy is the establishment of the EU Open Source Solutions Catalogue (EU OSS Catalogue), designed to address the current fragmentation where software developed by public entities is often scattered across disconnected repositories.

Establishment and Scope of the Catalogue

As proposed in Article 43(1) of CADA, the Commission shall provide and maintain an EU Open Source Solutions Catalogue. The primary function of this catalogue is to serve as a centralised catalogue to access software made available for reuse by Union entities (such as EU institutions, agencies, and bodies) and public sector bodies (including national, regional, and local public authorities).

The explanatory memorandum, specifically Recital 83, highlights the problem this catalogue aims to solve: currently, software developed by public entities is often made available in different, disconnected repositories or catalogues. This fragmentation "hamper[s] searchability, discoverability, and, ultimately, reuse." By mandating that software be made available through a catalogue connected to the EU OSS Catalogue, CADA aims to create a "one-stop-shop for open-source resources in the Union." This centralisation is intended to maximise the value of public expenditure by preventing the duplication of development efforts across Member States.

Connection to Existing Infrastructure and Free Access

The proposed regulation leverages existing EU digital infrastructure to avoid duplication and ensure seamless interoperability. Article 43(2) specifies that the EU OSS Catalogue shall be hosted on the Interoperable Europe portal, referred to in Article 8 of the Interoperable Europe Act (Regulation (EU) 2024/903). This integration ensures that solutions can be easily linked to further relevant information, training, and interoperability solutions available on the portal.

Crucially for public sector users, Article 43(2) also explicitly states that the EU OSS Catalogue shall be accessible electronically free of charge. This provision removes financial barriers to access, ensuring that even smaller public administrations with limited budgets can benefit from the collective digital assets of the Union. The free access model is designed to encourage broad adoption and the rapid diffusion of innovative public sector solutions.

How Software Enters the Catalogue: A Federated Approach

For the catalogue to be effective, public sector bodies must actively contribute, but the mechanism is designed to be flexible. Article 42 of CADA sets out the obligation for Union entities and public sector bodies: when they make software to which they hold intellectual property rights available for reuse under an open-source licence, they must do so using a catalogue or repository that is connected to, and made accessible through, the EU OSS Catalogue.

This does not mean every public body must migrate its software to a central server. Instead, Article 43(3) establishes a federated model. It allows Union entities or public sector bodies that own or maintain their own national or local catalogues to request that their catalogue be connected to the EU OSS Catalogue. The Commission shall decide on these requests based on objective and relevant criteria. This approach ensures that local or national catalogues remain the primary interface for their respective users while ensuring that the software they host is discoverable via the central EU OSS Catalogue.

Governance and the OSPO Network

To support the implementation of these obligations and ensure consistency, CADA proposes the establishment of a network of Open Source Programme Offices (OSPO Network) under Article 44. This network would facilitate cooperation on the implementation of open-source obligations, including the sharing and reuse of software. The OSPO Network would help exchange best practices on how to list, document, and maintain software in the EU OSS Catalogue, ensuring that the metadata and technical standards required for discoverability are met across different public administrations.

Promoting "Open Source First"

The catalogue is the practical enabler of a broader "open source first" approach mandated by Article 41. Under this article, Union entities and public sector bodies are encouraged to use and facilitate the reuse of open standards and components released under open-source licences when building their cloud and AI ecosystems. The EU OSS Catalogue is the tool that makes this preference actionable: by making it easier to find existing, vetted open-source solutions, it reduces the incentive to develop new proprietary solutions from scratch, thereby strengthening the European digital supply chain.

What this means for you

For public-sector procurement officers, IT managers, policy makers, and open-source advocates, the proposed EU OSS Catalogue represents a significant shift in how public software is managed, procured, and shared. Here is how you should prepare for the implementation of CADA:

1. Audit Your Current Software Assets

Public sector bodies should immediately begin reviewing their existing software portfolios. Identify software for which your organisation holds the intellectual property rights and which is already released or could be released under an open-source licence. Ensure this software is documented with sufficient metadata (e.g., licence type, functionality, dependencies) to be listed in a repository connected to the EU OSS Catalogue.

2. Connect Your Local Repositories

If your organisation already maintains an internal or national software repository, you should prepare to request connection to the EU OSS Catalogue under Article 43(3). Ensure your repository meets the technical and metadata standards required for interoperability with the Interoperable Europe portal. This will make your software visible to other public administrations across the EU, potentially saving others the cost of developing similar solutions and fostering cross-border collaboration.

3. Search Before You Buy or Build

When procuring new software or considering in-house development, the EU OSS Catalogue should become your first point of call. As a free, centralised resource, it allows you to discover existing open-source solutions developed by other public entities. This aligns with the "open source first" principle of Article 41 and can lead to significant cost savings, faster deployment times, and increased interoperability with other public systems.

4. Engage with the OSPO Network

Participate in or establish an Open Source Programme Office (OSPO) within your organisation. As proposed in Article 44, these offices will play a key role in managing open-source strategies, including how to contribute to and use the EU OSS Catalogue. Engaging with the OSPO Network will provide access to best practices, peer support, and guidance on the evolving technical standards for software sharing.

5. Prepare for Metadata Standards

To ensure your software is discoverable, you will need to provide accurate and standardised metadata. While specific technical standards are to be defined in secondary legislation or implementing acts, early adoption of common open-source metadata standards (such as those used by the Interoperable Europe portal) will facilitate a smoother transition and ensure your contributions are easily found by other administrations.

Common misconceptions

Misconception 1: The EU OSS Catalogue is only for EU institutions. Reality: As proposed in Article 43(1) and Recital 83, the catalogue is designed for both Union entities and public sector bodies across Member States. It is intended to be a cross-border tool for all levels of government, from local municipalities to national ministries.

Misconception 2: Public bodies must host their code directly on the Commission's server. Reality: Article 43(3) explicitly allows for a federated approach. National or local catalogues can be connected to the central EU OSS Catalogue. The Commission decides on these connections based on objective criteria, but the underlying infrastructure and hosting can remain local.

Misconception 3: All public sector software must be open-sourced. Reality: CADA encourages open source through Article 41 and Article 42, but it applies to software that public bodies voluntarily decide to make available for reuse. It does not mandate that all internally developed software must be open-sourced. However, if a public body does choose to release software under an open-source licence, it must do so via a catalogue connected to the EU OSS Catalogue.

Misconception 4: Access to the catalogue will be paid or restricted. Reality: Article 43(2) explicitly states that the EU OSS Catalogue shall be accessible electronically free of charge. This is a fundamental design principle to ensure equal access for all public administrations regardless of their budget.

Related

This is general information about a draft EU regulation, not legal advice.