Summary The proposed Cloud and AI Development Act (CADA) does not establish a standalone, direct grant fund for open-source projects. Instead, as proposed, it creates a regulatory framework that mandates EU Member States to integrate open-source support into their national cloud and AI strategies and directs existing EU funding programmesβspecifically Horizon Europe and the Digital Europe Programmeβto prioritize open-source cloud stacks and hardware. While CADA itself is a legislative instrument rather than a budgetary one, it acts as a powerful policy lever that channels financial resources toward open-source initiatives to strengthen technological sovereignty.
Detail
To accurately determine whether CADA funds open-source cloud and AI projects, one must distinguish between the legislative framework of the Regulation and the financial instruments it activates. CADA (Proposal COM(2026) 502 final) is designed to strengthen Europe's cloud and AI ecosystem through a mix of capacity building, sovereignty assurance, and demand-side measures. It does not contain a specific budget line for direct grants to software developers. However, it establishes the Cloud and AI Leadership Initiatives, which are explicitly financed through existing Union programmes.
The Mandate for National Strategies (Article 7)
A primary mechanism through which CADA promotes open source is the legal obligation imposed on Member States to adopt national cloud and AI strategies. Article 7(1) requires Member States to establish these strategies within one year of the Regulation's entry into force. Crucially, Article 7(2)(g) explicitly mandates that these national strategies must include "measures to support the development of cloud computing stack technologies built upon open hardware and software to strengthen technological sovereignty and enhance the competitiveness of strategic European industries."
This provision ensures that open-source development is not left solely to market forces but is embedded in national policy. While the specific funding for these measures may come from national budgets or co-financing through EU structural funds, the legal requirement ensures that open-source cloud stacks remain a priority in national digital transformation plans. This creates a binding obligation for Member States to actively support open-source development within their territories.
Funding via Union Programmes
The financial engine for CADA's open-source objectives is found in Article 6(3), which states that the Cloud and AI Leadership Initiatives "may be supported by funding from Union programmes, including Horizon Europe and the Digital Europe Programme."
The Explanatory Memorandum accompanying the CADA proposal clarifies the strategic intent, stating that the initiative places "a specific focus on open source as a lever to boost technological sovereignty." It outlines that the Leadership Initiatives will support:
- Open Cloud Stacks: Developing secure, resilient, and performant open cloud computing stacks (as detailed in Article 4(2)(a)).
- Open-Source Foundations: Fostering the creation of open-source software foundations that support open-source components, providing governance and coordination mechanisms (as detailed in Article 4(2)(d)).
- Catalogues: Establishing a catalogue of European open cloud computing solutions developed under these initiatives (as detailed in Article 4(2)(e)).
Therefore, while CADA does not write checks directly, it directs the billions of euros available in Horizon Europe and the Digital Europe Programme toward projects that deliver open-source cloud infrastructure, middleware, and AI tools. The proposal also notes that the Cloud and AI Leadership Initiatives could continue receiving support under successive Union programmes subject to their adoption in the next Multiannual Financial Framework.
The "Open Source First" Mandate for Public Sector
Beyond funding supply, CADA creates demand for open-source solutions through procurement rules, effectively de-risking investment for developers. Article 41 requires the Union and Member States to take measures to encourage Union entities and public sector bodies to "use and facilitate the reuse of open standards and components released under an open source licence when building their cloud and AI ecosystem or stack."
Furthermore, Article 42 and Article 43 mandate that when public bodies make software available for reuse, it must be done through catalogues connected to the EU Open Source Solutions Catalogue (EU OSS Catalogue). This creates a sustainable ecosystem where publicly funded open-source projects gain visibility and adoption, indirectly supporting their maintenance and development through community usage and further public investment. The proposal also establishes a network of Open Source Programme Offices (OSPOs) to facilitate the exchange of best practices and support the implementation of these obligations.
Grand Challenges and Open Source
The proposal identifies "Grand Challenges" in Annex I that will drive funding priorities. Grand Challenge 2 focuses on "Cloud stacks," aiming to build end-to-end hardware and software cloud stacks to bridge capacity gaps. The text emphasizes building "European open cloud stacks" and notes that pilot programmes will demonstrate the capabilities of these stacks. This indicates that open-source cloud infrastructure is a central pillar of the funding strategy, not a peripheral activity. Additionally, Grand Challenge 6 on "Cooperative European Industrial Models" highlights the use of advanced confidentiality-preserving technologies and federated approaches, which often rely on open-source frameworks to ensure transparency and trust.
What this means for you
For CTOs, architects, and SMEs evaluating the practical impact of CADA, the distinction between regulation and funding is critical. The Act creates a "pull" mechanism where funding follows the policy mandate for sovereignty and openness.
1. Alignment with Funding Calls If you are developing open-source cloud or AI tools, you should align your project proposals with the operational objectives of the Cloud and AI Leadership Initiatives. Specifically, focus on:
- Open Cloud Stacks: Projects that contribute to the development of open-source middleware, data platforms, or cloud management interfaces that bridge the Union's critical capacity gaps.
- Sovereignty and Security: Emphasize how your open-source solution enhances technological sovereignty, reduces dependency on third-country providers, and meets the security standards outlined in CADA's sovereignty framework.
- Interoperability: Ensure your projects support the interoperability requirements of the EuroCloud Federation and the EU OSS Catalogue.
2. Leveraging National Strategies Monitor the national cloud and AI strategies of the Member States where you operate or plan to operate. Under Article 7(2)(g), these strategies must include measures to support open hardware and software. This often translates into national funding calls, tax incentives, or public procurement preferences for open-source solutions. Engaging with national authorities during the strategy formulation phase can position your organization to benefit from these measures.
3. Public Sector Procurement The "open source first" mandate in Article 41 means that public sector bodies will increasingly prefer open-source solutions. For SMEs, this opens up new market opportunities. However, it also raises the bar for quality, security, and maintainability. Ensure your open-source projects have robust governance, clear licensing, and active community support to meet the expectations of public buyers.
4. Participation in Open-Source Foundations CADA encourages the creation of open-source software foundations. Consider joining or establishing such foundations to pool resources, share governance, and enhance the credibility of your open-source projects. This aligns with the proposal's goal of fostering collaborative ecosystems that reduce fragmentation and increase the competitiveness of European providers.
Common misconceptions
Misconception 1: CADA provides direct grants to any open-source project. Reality: CADA does not have its own budget. Funding flows through existing programmes like Horizon Europe and the Digital Europe Programme. Projects must meet strict eligibility criteria and align with the specific operational objectives of the Cloud and AI Leadership Initiatives. Not every open-source project will qualify; priority is given to those that address strategic technological challenges, such as sovereign cloud stacks or frontier AI infrastructure.
Misconception 2: Open source is only a secondary priority. Reality: The Explanatory Memorandum explicitly states that CADA places a "specific focus on open source as a lever to boost technological sovereignty." Open source is central to the strategy for reducing dependency on non-European providers and building a resilient EU cloud ecosystem. It is not an afterthought but a core component of the regulatory and funding framework.
Misconception 3: The "Open Source First" rule applies to all private companies. Reality: The obligation to prioritize open source under Article 41 applies specifically to Union entities and public sector bodies. While private companies are encouraged to adopt open standards and components, they are not legally mandated to do so by CADA. However, public procurement preferences will likely drive market demand toward open-source solutions.
Misconception 4: National strategies are optional. Reality: Article 7(1) requires Member States to establish national cloud and AI strategies within one year of the Regulation's entry into force. These strategies must include measures to support open hardware and software (Article 7(2)(g)). This creates a binding obligation for Member States to actively support open-source development within their territories.
Related
- Why does Europe need to fund its own cloud and AI?
- Who decides which CADA projects get funding? Commission vs Member States
- What is the European Competitiveness Fund and how does CADA use it?
- What is the Digital Europe Programme and what does it fund for cloud and AI?
- What is InvestEU and can it back CADA projects?
This is general information about a draft EU regulation, not legal advice.