Summary As proposed, the Cloud and AI Development Act (CADA) would establish the EU Open Source Solutions Catalogue under Article 43 to centralize public-sector software for reuse, directly helping startups access high-quality, pre-vetted technology. By mandating that Union entities and public bodies publish reusable code in this connected catalogue, CADA aims to lower barriers to entry for startups, allowing them to build on existing public assets rather than starting from scratch. The proposal explicitly tracks success through Key Performance Indicators (KPIs) including "downloads by third parties," signaling a policy focus on actual market uptake. This framework enables startups to leverage public investment, reduce development costs, and compete more effectively for public contracts.

Detail

The proposed Cloud and AI Development Act (CADA) introduces a structured approach to open source that specifically targets the friction between public-sector innovation and private-sector adoption. For startups and small mid-caps (SMCs), the ability to access robust, secure, and interoperable software is often hindered by the cost of development and the lack of visibility into what public authorities have already built. CADA addresses this through a combination of transparency obligations, centralized repositories, and performance monitoring, creating a "reusable by design" ecosystem.

The EU Open Source Solutions Catalogue (Article 43)

The cornerstone of CADA’s open-source strategy for startups is the establishment of the EU Open Source Solutions Catalogue (referred to in the text as the β€˜EU OSS Catalogue’). Under Article 43(1), the Commission is empowered to provide and maintain this catalogue as a centralized hub to access software made available for reuse by Union entities and public sector bodies.

Crucially, Article 43(2) mandates that the EU OSS Catalogue shall be hosted on the Interoperable Europe portal and shall be "accessible electronically free of charge." This free access is vital for startups, which often operate with limited budgets for licensing or procurement. By ensuring the catalogue is free, CADA removes financial barriers to discovering and utilizing public-sector technology.

Furthermore, Article 43(3) gives the Commission the power to decide, based on objective and relevant criteria, whether to connect existing national or entity-specific catalogues to the central EU OSS Catalogue. This creates a federated but unified search experience, allowing a startup in one Member State to easily discover and reuse software developed by a public body in another, fostering cross-border innovation and preventing the fragmentation of the digital single market.

Lowering Barriers Through Mandatory Reuse (Article 42)

For the catalogue to be useful, it must be populated. CADA ensures this through Article 42, which imposes a conditional obligation on Union entities and public sector bodies. When these bodies decide to 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 the EU OSS Catalogue.

This provision transforms isolated public-sector codebases into discoverable assets for the private sector. For startups, this means:

  1. Reduced Development Costs: Startups can integrate or fork existing public solutions rather than building foundational components from scratch. This accelerates time-to-market for new digital services.
  2. Increased Trust: Software released by public entities often undergoes rigorous security and compliance checks. By reusing this code, startups can leverage a higher baseline of trust and compliance, which is particularly valuable when bidding for public contracts later.
  3. Interoperability: Because these solutions are often built to meet public-sector interoperability standards (aligned with the Interoperable Europe Act), startups can build products that are more likely to integrate seamlessly with other government systems, reducing integration friction.

Monitoring and KPIs: Third-Party Downloads

CADA does not just mandate publication; it aims to measure impact. While the specific KPIs for the overall regulation are outlined in the Legislative Financial Statement (Section 1.3.4), the text highlights the importance of tracking the uptake of open-source solutions. One specific indicator mentioned for Objective 4 (protection of public order and resilience) is the "Number of public sector solutions released as open source in the repository, and their downloads by third parties."

This KPI is significant for startups because it signals a policy focus on actual usage, not just compliance. The EU is incentivizing public bodies to release code that is usable and valuable to the market. For startups, this creates a clearer signal of where public investment is flowing and which technologies are being prioritized for external adoption. The metric of "downloads by third parties" serves as a proxy for market validation, helping startups identify which public tools have traction and are worth building upon.

Supporting Startups and SMEs

The proposal explicitly recognizes the role of smaller entities in the ecosystem. Article 33 sets an objective for Member States to ensure that at least 25% of their procurement for cloud computing services and AI systems be awarded to innovative SMEs. By lowering the barrier to entry through open-source reuse (via Article 43), CADA indirectly supports this procurement goal. Startups that build on the EU OSS Catalogue can demonstrate innovation and reduce their total cost of ownership, making them more competitive bidders for these public contracts.

Additionally, Article 44 establishes a network of Open Source Programme Offices (OSPO Network) to facilitate cooperation and the exchange of best practices. This network can serve as a channel for startups to engage with public bodies, understand their needs, and identify opportunities for collaboration or commercialization of open-source solutions. The OSPO network is designed to promote the sharing and reuse of open-source software by public sector bodies, creating a feedback loop where private innovation informs public procurement.

What this means for you

For cloud service providers, data-centre operators, and startups aiming to serve the public sector, CADA’s open-source provisions offer a strategic opportunity to differentiate your services and accelerate growth.

  1. Offer Catalogue-Integrated Solutions: Develop or partner with startups that build on software listed in the EU OSS Catalogue. By offering services that are pre-aligned with public-sector reusable assets, you reduce integration friction for your public-sector clients and position yourself as a "sovereign" and interoperable partner.
  2. Leverage Free Access: Ensure your development teams are aware of the free access provisions in Article 43(2). Use the EU OSS Catalogue to source secure, compliant components for your own infrastructure or customer-facing applications, reducing your R&D costs and avoiding vendor lock-in.
  3. Prepare for Interoperability: Since the catalogue is hosted on the Interoperable Europe portal, familiarity with these standards will be a competitive advantage. Position your services as interoperable with the open-source solutions found in the catalogue, ensuring seamless integration with future public-sector digital services.
  4. Engage with the OSPO Network: Consider engaging with the network of Open Source Programme Offices established under Article 44. This can provide early insights into public-sector needs and potential partnerships with startups that are leveraging these open assets. The network is intended to facilitate the exchange of information and best practices, which can be invaluable for startups navigating the public procurement landscape.
  5. Track the "Downloads" KPI: Monitor the "downloads by third parties" metric as a leading indicator of market demand. If a specific public-sector tool sees high download numbers, it signals a ripe opportunity for startups to build commercial value-added services around that technology.

Common misconceptions

  • Misconception: CADA forces all public-sector software to be open-sourced.
    • Reality: Article 42 applies only to software that public entities voluntarily decide to make available for reuse. It does not mandate that all public software must be open-sourced, but it ensures that when it is, it is done in a discoverable, standardized way via the EU OSS Catalogue.
  • Misconception: The EU OSS Catalogue is a commercial marketplace.
    • Reality: The catalogue is for free reuse of software under open-source licences. It is not a platform for selling proprietary software. However, startups can build proprietary services on top of these open-source foundations, creating commercial value while adhering to the open-source licence terms.
  • Misconception: Startups cannot use public-sector code for commercial products.
    • Reality: As long as the software is released under an appropriate open-source licence, startups can freely use, modify, and integrate it into commercial offerings. The licence terms will dictate any specific requirements (e.g., attribution, share-alike), but commercial use is generally permitted under standard open-source licences. The KPI of "downloads by third parties" explicitly anticipates and encourages this commercial uptake.
  • Misconception: The catalogue is only for large corporations.
    • Reality: The framework is explicitly designed to lower barriers for startups and SMEs. By providing free access to vetted, high-quality code, CADA levels the playing field, allowing smaller players to compete with larger incumbents who might otherwise have the resources to build everything in-house.

Related

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