Partners & Development

The cycle problem

Defence procurement runs on a multi-year cycle. Requirements are written, a tender runs, bids are evaluated, a contract is signed, a system is built, accepted and fielded. From first requirement to operational capability, three to seven years is normal and nobody involved considers that slow.

Small unmanned systems do not run on that cycle. A control link gets changed in weeks. A navigation mode that was jammable becomes autonomous in a firmware update. An airframe that was detectable by one method gets a component swap and stops being detectable by it.

Put those two clocks side by side and the arithmetic is unpleasant. A countermeasure specified against the threat of 2023 and fielded in 2027 is not a countermeasure. It is a capital expenditure with a documentation trail.

The gap isn’t technical. Europe can build the hardware. The gap is that the feedback loop between „this stopped working“ and „here’s the fix“ runs through a process designed for a different kind of adversary.

The model

Orionyx develops and sources drone technology together with partners in Ukraine, under contract. The arrangement is deliberate and it is structural rather than opportunistic.

Why there

Ukraine is where the loop between deployment, failure and adjustment currently runs fastest — measured in weeks, sometimes less. Development there happens in contact with an adversary that is itself adapting continuously. That is not a condition you can simulate, and it is not a condition that exists on a European test range.

What we take from it

Three things, in order of value:

• Knowledge of what’s actually flying. Not the catalogue. What is being modified, how, and what those modifications defeat. This is the input that keeps classification current.
• Knowledge of what stopped working. More valuable than knowing what works, and much harder to get from a vendor. Negative results don’t appear in datasheets.
• Hardware and subsystems that have been through that loop rather than through a trade show.

What we bring to it

A partnership that only extracts is not a partnership, and would not survive. We contribute EU market access, contract structure that holds up under European procurement, regulatory work our partners have no reason to specialise in, and the integration engineering needed to make a system fit a European operator’s control room, legal framework and audit obligations.

What our customers get

A shorter distance between an identified gap and an adjusted answer. Where a conventional supply relationship would put a change request into a queue, this one puts it into a loop that is already turning.

Image · Development

Engineering context: workbench, test setup, or subsystem under assembly. Working light, high detail, no faces, no identifiable location, no national markings. Documentary. 16:9, min. 2400px. Important: nothing that identifies a partner facility or personnel. If in doubt, use the technical detail shot from the AIR area instead, or remove this figure.

What this does and doesn’t mean

This partnership is easy to overclaim, and the field is full of people doing exactly that. So, plainly:

What it means

• Our understanding of the threat is refreshed continuously from contact, not from reporting.
• Technology we supply has been exposed to an adapting adversary before it reaches you.
• When something in our portfolio stops being effective, we tend to find out early rather than from a customer.

What it does not mean

• It is not a guarantee. A system tested against one adversary in one theatre is not thereby proven against a different adversary in a different environment. Anyone claiming otherwise is selling.
• It is not a transfer of anyone’s operational data. What flows to us is engineering knowledge, not operational information about our partners‘ activities.
• It is not an endorsement we’re entitled to trade on. The people doing this work are not a marketing asset, and we try not to treat them as one.
• It does not make us a defence manufacturer at scale. We are a small company with a specific focus. Where a requirement exceeds what we can honestly deliver, we say so.

Legal structure

This is the part most companies leave vague. We’d rather set it out, because anyone doing serious diligence on us will ask, and the answer is better given upfront.

Contractual basis

Relationships with development and supply partners are contracted, not informal. Scope, IP ownership, end-use restrictions and termination conditions are written down before work begins.

Export control

Technology transfers in both directions fall under Regulation (EU) 2021/821 on dual-use items and the Lithuanian Law on the Control of Strategic Goods. Transfers are assessed for licensability before they happen, and where a licence is required, it is obtained before rather than after. See Compliance.

Data protection

Ukraine has no adequacy decision under Article 45 GDPR. Any transfer of personal data — including something as mundane as a list of contacts — requires appropriate safeguards under Article 46, in practice standard contractual clauses together with a transfer impact assessment.

We mention this because it is exactly the kind of detail that gets waved through during a partnership announcement and then found during an audit. It is addressed in our privacy policy, and it is a question we expect from any serious counterparty.

Sanctions screening

Partners and counterparties are screened against EU sanctions lists before engagement and periodically after. This applies to suppliers as much as to customers.

For prospective partners and suppliers

If you build something relevant — sensing, effectors, subsystems, software, integration — we’re open to a conversation. What we’ll want to establish early, in roughly this order:

Question	Why it comes first
What does it do, measured how?	A capability claim without stated measurement conditions can’t be assessed, and we won’t pass it on to a customer.
Where does it stop working?	The most useful thing a supplier can tell us. A vendor who claims no failure modes has either not looked or won’t say.
What’s the export classification?	Determines whether a conversation can proceed at all, and under what licence.
Who owns the IP, and what’s licensed?	Settled before development, not during a dispute.
What’s the ownership and control structure?	Sanctions screening and end-use responsibility both depend on it.

Use the contact form with subject „Partnership“. For anything that shouldn’t travel in a web form, write encrypted — our key is at /pgp.

Get in touch