EU Defence · Ukraine
EDIP and the Ukraine Support Instrument: €300 Million for EU–Ukraine Defence Consortia — What Matters Before You Apply
Reviewed by Oleksandr Sobovyi, Founder & CEO of CORVUS AI — editorial responsibility statement below
On 8 December 2025, the Council of the EU gave final approval to Regulation (EU) 2025/2643, establishing the European Defence Industry Programme (EDIP). Within EDIP's €1.5 billion budget, a dedicated Ukraine Support Instrument (USI) — €300 million — gives Ukrainian defence companies a status equivalent to that of companies from EU-associated countries, rather than the status of an outside partner.
On 30 March 2026, the Commission adopted the EDIP work programme for 2026–2027 (Commission Implementing Decision C(2026) 2174 final), translating the Regulation's framework provisions into concrete calls with budgets, deadlines and participation conditions. What follows is what matters for the legal and commercial structure of an application — not a restatement of press releases.
How USI Funding Is Structured
Of the €300 million:
€260 million — Industrial Reinforcement Actions (IRA): joint EU–Ukraine production projects, capacity scale-up;
€35.3 million — BraveTechEU, implemented through a direct grant to Ukraine's Innovation Development Fund (operating arm: Brave1) without a separate EU-level call; Brave1 then distributes funds through its own competitive calls to third parties (FSTP), with grants of up to €200,000 for solutions at TRL4 or above.
The IRA funding form is a lump sum, tied to milestones (Article 125(1)(d)-(e) of the Financial Regulation 2024/2509) — not cost reimbursement. This is decisive for structuring the consortium agreement: liability for a missed milestone is allocated differently than under cost-reimbursement grants, and this needs to be set out in the agreement between participants, not left to the grant agreement with the Commission by default.
Two Open Calls
EDIP-USI-2026-LS-IRA-MAB (Missiles, Ammunition and Bombs) Topic budget €180 million, grant per project €2–30 million, deadline 13 October 2026. An optional work package for physical and cyber protection of production facilities is available — up to €500,000 on top of the main grant, tied directly to NIS2 compliance and alignment with ISO/IEC 27001 and IEC 62443.
EDIP-USI-2027-LS-IRA-CUXS (Unmanned & Counter-Unmanned Systems) Topic budget €80 million, grant per project €2–10 million, deadline 16 February 2027. Same optional protection WP — up to €200,000.
Conditions That Shape Consortium Structure
Composition. A consortium cannot be purely Ukrainian or purely EU in composition — USI's stated objective is cooperation between the Union and Ukraine (Article 22 of the Regulation). Maximum consortium size is 15 legal entities(Article 34(3)(c)).
Localisation. Costs related to cooperation with legal entities established outside the territory of Member States, the EEA or Ukraine, or controlled by a non-associated third country, are not eligible for USI funding at all — this is not a share-based cap but a condition of cost eligibility itself. Separately, for procurement actions, the 65/35 rule applies: components sourced from outside the EU and Ukraine may not exceed 35% of the estimated cost of the end product's components.
What the work programme does not cover. Intellectual property terms (foreground/background IP) are governed by the EDIP Model Grant Agreement and Annotated Grant Agreement — separate documents published alongside the call documents on the portal, not by the work programme itself. Any consortium planning joint development under IRA needs to settle its IP structure at the consortium agreement stage, before filing, not after the fact.
Why This Matters for CORVUS's Practice
The intersection of export control, IP allocation and milestone obligations under lump-sum grants creates three concrete workstreams that applicants typically miss without legal counsel:
structuring the consortium agreement around lump-sum logic — allocating the risk of a missed milestone and grant payments between EU and Ukrainian participants;
auditing the supply chain against the 65/35 rule and excluded jurisdictions before filing, not after a rejection;
settling the IP regime and technology-transfer arrangements between the Ukrainian and European sides of the consortium, in light of export-control requirements (dual-use and military lists).
Next step: for companies planning to file under MAB (deadline 13 October — under two months out) or CUXS, legal review of the consortium and IP structure needs to start now, not two weeks before the deadline. A lump-sum Grant Agreement leaves no room to renegotiate liability allocation after the fact.
What matters. What’s next.
Disclaimer
This article has been prepared by CORVUS AI for general informational and educational purposes only. It is intended to make complex legal and regulatory developments easier to understand.
It does not constitute legal advice and does not create a professional adviser–client relationship. The information should not be relied upon as a substitute for advice based on the specific facts, circumstances and applicable law relevant to your organisation or project.
The article reflects our understanding of the law and regulatory framework as of the date of publication. Legislation, case law, regulatory guidance and administrative practice may subsequently change. While reasonable care has been taken in preparing this article, CORVUS AI does not warrant that the information is complete or remains current after the date of publication. We do not undertake to update this content.
To the fullest extent permitted by applicable law, CORVUS AI excludes liability for loss arising from reliance on this article. Nothing in this article constitutes an offer or solicitation to provide regulated legal services in any jurisdiction where doing so would be unlawful.
AI-assisted preparation: This article was prepared with the assistance of AI tools. Its legal analysis, conclusions and final text were subject to human review and editorial control and were reviewed and approved prior to publication by Oleksandr Sobovyi, Founder & CEO of CORVUS AI. CORVUS AI retains editorial responsibility for the published content.
For advice tailored to your organisation, project or specific circumstances, please contact CORVUS AI.
