UNITE–Brave NATO: who can bid, and who can deliver the technology?

Complex law. Clear action.

Reviewed by Oleksandr Sobovyi, Founder & CEO of CORVUS AI — editorial responsibility statement below.

4 November 2026 · Defence procurement and Ukraine

The NATO Communications and Information Agency (NCIA) plans to issue its UNITE–Brave NATO solicitation on 18 November. For a company considering the €10 million first round, the first document to read is the bidder list published in June. By the time NCIA updated its procurement timetable in October, national authorities had already nominated the Allied companies and the Ukrainian expression-of-interest window had closed.

One joint project, two routes to funding

NATO and Ukraine announced €10 million between them for the first competition, with equal contributions. NCIA is procuring innovation contracts from Allied companies. On the Ukrainian side, Brave1 runs a grant competition in which the Ukrainian developer submitted the expression of interest on behalf of both partners. The €10 million is the aggregate first-round figure. The amount available to an individual partner depends on the challenge.

That distinction also matters when assessing technical fit. NCIA’s April announcement mentioned counter-drone systems, air defence and secure frontline communications. The subsequent Brave1 call specified categories including protection against FPV drones, counter-Shahed systems and electromagnetic support for signals intelligence. A communications supplier assessing its fit should identify the particular published challenge its product would help the team deliver. Secure communications did not appear as a standalone category in the Ukrainian call.

What the November timetable means

NCIA’s advice to contact national delegations was relevant when nominations were being sought. Amendment 2, dated 22 June, records the outcome. Section 2 directs readers to Annex B for the companies nominated by their national authorities and closes the first round to additional nominations. Brave1’s conditions also require the Allied partner to appear in that annex. On the Ukrainian side, access to the full application stage depends on the developer’s inclusion in the register of qualified participants.

The NCIA procurement record, updated on 13 October, gives 18 November 2026 as the planned solicitation date, 8 December 2026 as the planned closing date and 15 March 2027 as the planned award date. These dates concern the NCIA procurement. They provide no basis for assuming that either the Allied nomination process or the Ukrainian qualification stage has reopened.

What the partners need from their cooperation agreement

Brave1 requires a cooperation agreement and asks the partners to identify their respective technical contributions, including their percentage shares. It also requires the Ukrainian developer to deliver at least two samples of the joint development, with technical documentation, to military units. These requirements raise a practical question for both partners. Does the developer have the rights and permissions needed to deliver what the team has promised?

Consider an Allied supplier contributing a sensor and a Ukrainian developer integrating it into a counter-drone system. The supplier may own the hardware design while licensing the firmware from a third party. Recording each partner’s percentage contribution leaves open who may copy the documentation, share firmware with a test facility or modify it when a field trial identifies a fault.

The agreement should identify the existing technology each party brings, the rights it can grant and who may use improvements and test results. Before either partner shares technical files or dispatches a prototype, the team should map the items, recipients, destinations and intended use, then determine which export-control checks, authorisations or third-party consents apply. The delivery schedule should name the party responsible for obtaining each permission and allocate the cost of delay, failed acceptance tests and rework.

For an external legal adviser such as CORVUS AI, this is a potential mandate from a participating company. The starting point is to verify the Allied entity against Annex B, confirm the Ukrainian developer’s qualification status and review the actual cooperation agreement. The adviser’s fees, access to technical material and responsibility to its client require separate agreement. For a qualified team preparing its bid, the most useful document may be a short schedule linking each promised deliverable to the partner that owns it, the permission needed to release it and the party responsible if it cannot be delivered.

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.

NCIA procurement record · RFP-42534805 · Brave1 competition conditions