Sea domain
Autonomous surface and undersea systems sharing the same Flowstate core — and the same payload modules — as our aircraft.
Land domain
Ground systems that inherit the air picture rather than rebuild it, and carry the aircraft forward instead of waiting on it.
Autonomy core
Perception, decision and control on board. No cloud, no dependency, no link required.
Flowstate
Works
Airframe to firmware, taken in-house from concept through CFD, qualification and flight test.
Capability
Type to filter · Enter to open · Esc to close
Mission
Capability that arrives in a decade deters nobody. We build aircraft that fly this year, on hardware and software we own end to end.
The gap between what a defence programme promises and when it arrives has become the capability gap. Requirements are written against a threat, and by the time the system is fielded the threat has iterated three times.
The answer is not a better requirement document. It is owning enough of the stack that you can change the product in weeks, and building things small and cheap enough to be fielded in numbers rather than protected as assets.
Four commitments. Each one is checkable against what we have shipped.
Airframe, structure, avionics and autonomy in-house. When flight test finds a problem, the person who can fix it is in the building.
Prototypes in the air in months. A design that has not flown is an opinion, and we would rather be corrected by a flight line than by a review board.
Every platform runs the same autonomy stack. Adding an aircraft makes the picture richer rather than adding another system to manage.
A person authorises every engagement, and can abort after commit. Autonomy governs how the aircraft flies, not whether it strikes.
Where it goes
HADI is flying today. Sea and land systems follow, inheriting the same autonomy core rather than rebuilding it — so a contact held in the air is a contact the surface and ground pictures already hold.
We hire people who would rather fly a prototype this year than brief one for five.
Open roles