Brave1 is Ukraine's state-sponsored defence technology ecosystem, established in 2023 through a joint initiative of the Ministry of Defence of Ukraine and the Ministry of Digital Transformation (Mincifra). Its purpose is to connect technology companies — primarily startups and SMEs — with the Ukrainian Armed Forces and other security sector organisations that need their products. For defence software vendors, understanding how Brave1 works is essential for any commercial engagement with the Ukrainian defence sector.

The platform operates as both a marketplace and an accelerator. It provides a structured pathway from vendor registration through demonstration, evaluation, and ultimately procurement — with the distinctive feature that this entire process is designed to operate at a pace that matches operational requirements rather than bureaucratic timelines.

What Brave1 Is: The Institutional Structure

Brave1 was created by a joint order of the Ministry of Defence and the Ministry of Digital Transformation. The operational management is led by a coordinator who reports to both ministries and works with a team drawn from both the government and the private sector. The dual sponsorship is significant: it means that Brave1 has both procurement authority (through the MoD) and digital governance authority (through Mincifra), which gives it the cross-cutting mandate needed to move technologies quickly through the Ukrainian bureaucracy.

The participating institutions include the General Staff of the Armed Forces of Ukraine, the State Special Communications Service, the Security Service of Ukraine (SBU), the State Border Guard Service, and the National Police. This breadth means that a technology accepted into Brave1 has potential customers across multiple security sector organisations, not just the armed forces.

Brave1 is explicitly not a traditional government procurement body. It does not issue tenders or manage contracts in the conventional sense. Instead, it provides a validation and introduction function: companies that pass through the Brave1 evaluation process are introduced to military units and agencies that can then contract with them through existing procurement mechanisms. Brave1 accelerates the introduction and validation stage; the procurement itself happens through normal (though often expedited) channels.

The DOT-Chain: How Accelerated Procurement Works

The Ukrainian defence procurement reform that underpins Brave1's effectiveness is the DOT-Chain (Digital Operations Technology Chain). DOT-Chain was introduced to allow defence technology procurement to bypass the standard state procurement framework (ProZorro) in certain categories of defence technology, enabling contracts to be concluded in days rather than months.

Under DOT-Chain, a military unit that has identified a technology need can initiate a procurement process directly with a vendor, with Brave1 providing a validation certificate that satisfies the accountability requirements that would otherwise require a full tender process. The certificate attests that the vendor's product has been evaluated against defined military requirements and found suitable. This is not a blanket exemption from accountability — it is a pre-qualification mechanism that allows the formal procurement step to proceed on a compressed timeline once the technical evaluation has been completed.

The practical effect is that a software vendor that enters the Brave1 process and successfully completes evaluation can be under contract with a military unit within weeks of completing that evaluation. Compared to the 18–36 month timelines typical in Western European defence procurement, this represents a fundamentally different operating model for software vendors.

Vendor Registration: Steps and Requirements

The Brave1 vendor registration process begins at the platform's official portal. The registration requirements are designed to be accessible to startups and SMEs, not just established defence contractors. Key requirements include:

Company registration in Ukraine. The primary requirement for Brave1 participation is that the vendor be registered as a legal entity in Ukraine. Foreign companies that have established Ukrainian subsidiaries or representative offices are eligible. Pure foreign companies without a Ukrainian legal presence are generally not eligible for direct participation, though they may engage as partners of registered Ukrainian entities.

Technology readiness level (TRL) of at least 6. Brave1 is not a research programme — it is focused on technologies that are ready for operational deployment or close to it. A TRL of 6 means the system prototype has been demonstrated in a relevant environment. Pure research-stage technologies are not appropriate for the Brave1 pathway.

Security screening. Given the sensitive nature of military technology, vendors undergo a security screening process conducted by the SBU. The depth of this screening varies with the sensitivity of the technology involved. Software companies working on command and control, intelligence, or communications systems should expect a thorough screening that includes review of beneficial ownership, key personnel backgrounds, and technology supply chain.

Technical documentation. Vendors must provide technical documentation sufficient for military evaluators to assess the product's capabilities and integration requirements. For software products, this typically includes architecture documentation, API specifications, security certification documentation, and performance benchmarks.

Demo Days: How to Get There and What to Show

Brave1 organises regular Demo Days — structured events at which registered vendors demonstrate their technologies to military users and procurement officers. Demo Days are the primary mechanism through which vendors make the transition from the registry to active evaluation by potential military customers.

Getting to a Demo Day requires submitting a demonstration request through the portal, which is reviewed by the Brave1 coordination team. Successful applicants are allocated time slots and assigned evaluators from the relevant military structures. The evaluation criteria at Demo Days are heavily weighted toward operational utility rather than technical specification compliance — evaluators want to see the system performing realistic tasks under realistic conditions, not completing a scripted requirements checklist.

The most common mistake vendors make at Brave1 Demo Days is demonstrating their system in optimal conditions. Military evaluators have seen many systems that perform flawlessly in controlled demonstrations and then fail in the field. Demonstrating your system's behaviour when connectivity is degraded, when operated by an untrained user, or when data inputs are incomplete is more convincing than a perfect demo. Evaluators are specifically looking for operational robustness, not laboratory performance.

Key insight: Brave1 is not a procurement agency — it is a validation and introduction mechanism. The value of a Brave1 certificate is not that it guarantees a contract; it is that it removes the evaluation burden from individual military units, allowing them to procure from validated vendors with confidence. Understanding this distinction is essential for setting the right expectations about what Brave1 participation delivers.

After a successful Demo Day evaluation, the vendor receives a Brave1 validation recommendation that can be used to initiate procurement conversations with military units. The Brave1 team actively facilitates introductions to relevant units and agencies based on the technology's profile. This matchmaking function is one of the most valuable practical aspects of the programme — vendors do not have to navigate the opaque Ukrainian military organisational structure independently.

For software vendors considering the Brave1 pathway, the realistic timeline from initial registration to first contract is approximately three to six months for companies with a mature product and good documentation. Companies with products still in active development should expect a longer process. The key bottleneck is not the administrative steps but the availability of evaluators and the scheduling of Demo Days, which are oversubscribed given the volume of companies seeking validation.