The usual failure
Requirements written around a product someone already likes.
In Kairon
You start from the effect the mission needs — observe, strike, deliver — and derive requirements from it. Products are matched afterwards, not before.
Kairon turns an operational need into graded requirements, matches them to procurable line items, and checks the origin of every declared component against your policy. A tender is held while a mandatory requirement is unmatched or a flagged origin is uncleared. An embargoed origin can't be cleared at all.
Drone programmes move faster than the paperwork behind them. Kairon puts the reasoning in the record, so a tender can be explained line by line to an auditor, a minister or a supplier.
You start from the effect the mission needs — observe, strike, deliver — and derive requirements from it. Products are matched afterwards, not before.
Origin is declared per component, classified against your policy and checked at the gate, before a tender can be issued.
Every change is attributed to the signed-in person and time-stamped in the mission's audit trail, including the justification behind each compliance decision.
Every tender line traces back to the mission need that justified it. Kairon enforces the chain as you work, rather than documenting it after the fact. An orphan is a requirement with nothing procurable matched to it, and a mandatory one holds the tender until it is matched.
Capture the mission against a shared capability taxonomy: effect, environment, threat, range, payload and urgency.
Kairon derives the requirement set from the mission. Each requirement is SHALL, SHOULD or MAY, and the grade is shown by weight as well as colour.
Requirements are matched to procurable line items. Each item carries its component bill of materials, with a country of origin and an evidence reference per component.
The gate tests four things. A SHALL with no matched line item — an orphan — holds the tender, and so does any uncleared origin flag.
The tender document is generated from the validated set and frozen as a snapshot. While the gate is held, Kairon refuses to produce one.
One person records the award and a different approving authority approves it. The award is bound to the snapshot it was issued against, and the requirements become read-only.
Kairon never assumes a component is clean. Origins are classified against your policy. A flag holds the tender until Compliance clears it with a written justification. An embargoed origin is a sanctions hard-block that no clearance can lift.
A line item with no declared components is counted undeclared — never clean — and the tender says so.
Each ministry brings its own origin policy. Kairon ships illustrative starting presets and seeds the restricted and embargoed lists from the public EU arms-embargo list.
The signed-in identity is pinned on the server. Every change is attributed to that person and time-stamped in the mission's audit trail, and nobody can relabel it afterwards.
Kairon connects to outside sources, but it never lets them pass for checked evidence.
A TED / eForms adapter brings in EU notices as untrusted records. You preview them before anything is written. Fields that TED doesn't carry, such as where something was manufactured, come in as unknown.
Simulator results attach to a requirement as modelled predictions. They are kept apart from verified evidence and never treated as proof that a requirement is met.
How simulators connect →Every customer runs a dedicated instance, on premises or in the cloud.
English by default. Other languages are added on request.
Set your own price-to-fit ratio for each mission, from the lowest compliant price to the closest capability match.
Tender snapshots and gate verdicts print as filed evidence, with nothing truncated and markings preserved.
Projector-ready type and spacing. Classification markings and disclaimers stay visible.
Figures are computed on the server from the live record.
Connect your own mission simulator, or use our partner's. Kairon hands it the mission and its requirements, and files every run against the requirement it tested.
Many customers already run their own simulation environment or test range. Connect it to Kairon, and your models and data stay on your own infrastructure.
No simulator yet? Use our partner's flight simulation, built on Unreal Engine 5.7.
A briefing on your own mission need: requirements derived, line items matched and the gate run against your origin policy.