Defence programmes
Ministries & armed forces
Joint field trials, concept-of-operations work and training for the teams who will run Radax units.
The problem
03 / Why we exist
The edge got crowded, contested and cheap to attack.
01
Separate domains
Air, land and sea systems are bought, flown and briefed apart. Nothing they see is shared by default.
3 vendors · 3 radios · 3 screens
02
Fragile links
Most autonomy stops being autonomous when the datalink drops. In a contested spectrum, it drops first.
Link loss = mission loss
03
Scarce people
Crewed platforms and trained operators are the most expensive thing in the field, and the hardest to replace.
1 operator per vehicle
The solution
04 / One team, three domains
Autonomous units that work as one crew.
Radax builds the vehicles and the software between them. RDX-A, RDX-L and RDX-S share one track through core, keep working when links fail, and leave people in charge of every decision that counts.
Proof
05 / In the field, not on slides
Tested where it is hard.
From Arctic sea trials to desert range days, every Radax unit is flown, driven and dived by the people who will rely on it.
Autonomous field hours
Programmes in trial
Mission time with links jammed
Units per operator
Partners
06 / Who we build with
Built with the people who field it.
We work alongside defence programmes, integrators and research labs across allied nations, from first brief to sustainment.
Industry
Primes & integrators
Open, documented interfaces so core can sit beside the sensors, radios and C2 systems you already own.
Research
Labs & universities
Shared work on resilient networking, perception in bad weather and safe human–machine teaming.
How we work
07 / Brief to field
In the field in 90 days.
We don’t sell a catalogue. We start with your mission and put working units in front of your team fast.
01
Brief
Two days with your operators to map the mission, the terrain and the threats. We leave with a trial plan, not a proposal deck.
02
Field trial
A Radax team and a mixed set of units on your range within 90 days. Your people fly, drive and dive them from week one.
03
Integrate
core connects to your radios, sensors and C2 through open interfaces. Nothing is locked in, and your data stays yours.
04
Sustain
Over-the-air updates, spares and training on a fixed schedule, with engineers who know your deployment by name.
A
People in charge
Units propose. Operators approve. Every lethal or irreversible decision stays with a person.
B
Secure by design
End-to-end encrypted links, signed software and hardware roots of trust on every unit.
C
Works when jammed
Units keep a local copy of the shared picture and carry on with the last approved plan when links fail.
D
Open interfaces
Documented APIs and standard message formats, so core fits next to what you already run.
FAQ
08 / Straight answers
Questions we hear first.
Are Radax units armed?
+
What happens when the network is jammed?
+
Can core work with systems we already own?
+
Who can buy from Radax?
+
How fast can we run a trial?
+