▪ Agents
Distribution and agency
Regional exclusivity by class and territory, dealer certification and demo fund.
Discuss distribution▪ Partners Partnerships, offsets and technology transfer
Build it where you need it.
In several of our markets the question is not whether the equipment works — it is whether it can be produced locally, under your control, with your engineers. Ukraine holds intergovernmental agreements that allow exactly that: technology transfer without assignment of intellectual property, with use and re-export control.
▪ 01 Five models
Pick the one that matches your obligation, not ours
-
Licensing
A production licence for defined SKUs in your jurisdiction. You manufacture; we supply documentation, test benches and engineer certification.
Best fit: national localisation targets
-
Joint venture
A shared entity with a local ownership share, satisfying offset and local-content requirements directly.
Best fit: GAMI, Tawazun, Barzan programmes
-
OEM and integration
Our modules inside your platform or C2 architecture, with an interface specification and a compatibility matrix.
Best fit: prime contractors and integrators
-
Distribution
Regional exclusivity by class and territory, dealer certification, demo fund and spares pool.
Best fit: established defence agents
-
R&D co-operation
Joint development against your requirement, with foreground and background IP split defined before work starts.
Best fit: sovereign capability programmes
▪ 02 What transfers and what does not
Stated before the first meeting, not during the third
| Item | Licensing | Joint venture | OEM | R&D co-op |
|---|---|---|---|---|
| Assembly documentation | Yes | Yes | Partial | Yes |
| Test bench and QC methodology | Yes | Yes | Partial | Yes |
| Engineer certification | Yes | Yes | Yes | Yes |
| Firmware source | No | Escrow | No | Negotiated |
| RF design files | No | Negotiated | No | Foreground only |
| Right to export from your territory | Defined per agreement | Defined per agreement | No | Negotiated |
| Ownership of background IP | Stays in Ukraine | Stays in Ukraine | Stays in Ukraine | Stays with originator |
▪ 03 Localisation context by market
The targets your programme is measured against
| Market | Authority | Target | Current | Route |
|---|---|---|---|---|
| Saudi Arabia | GAMI | 50% of military spend by 2030 | 24.89% (end-2024) | Licensing or JV |
| United Arab Emirates | Tawazun · EDGE Group | Offset obligations per contract | ~18% (2023) | JV or OEM into EDGE |
| Qatar | Barzan Holdings | Programme-specific | — | JV or licensing |
| Poland | PGZ · SAN programme | ~60% local content | In programme | OEM sub-supply |
| Australia | GWEO | Sovereign guided weapons capability | In programme | R&D co-operation |
| South Korea | DAPA | Domestic content requirements | In programme | Licensing |
▪ 04 How a partnership starts
The site opens the door; the deal is closed in the room
-
Partner profile
Country, capabilities, existing contracts, offset obligations. Ten minutes, no NDA needed yet.
-
Indicative model
We come back with which of the five models fits, what transfers and what does not, and the legal basis.
-
NDA and data room
Technical packages, localisation terms, royalty model and production requirements.
-
Negotiation offline
Terms, volumes and schedule are agreed in person. Nothing about this stage happens on a website.
▪ 05 What partners ask first
Including the uncomfortable ones
Yes. We issue a proforma or commercial invoice, a supply contract and a specification, plus an end-user certificate template where the class requires one. For EU buyers VAT is handled as a reverse charge against a valid VAT number. Documents are generated online — no account manager needed to get them.
▪ 06 Partner profile
Start with a profile, not a pitch
Tell us the country, the obligation you are working against and the capability you already have. We reply with an indicative model — which of the five fits, what transfers, and on what legal basis.
- First response
- 2 business days
- Indicative model
- Within 10 business days
- NDA
- Before any technical package
- Data room
- After NDA, access logged
Reference