Where We Work
A small portfolio of connected domains, not a catalogue. Sensing, decision, protection and response are parts of one system, so our programmes cover interfaces and integration, not only products. An interface is the connection that lets one system pass data or commands to another. Integration is the work of making separate systems operate as one.
Uncrewed systems
Reconnaissance, logistics, maritime, autonomous and defensive systems, and selected effects where authorised. Early work concentrates on modular airframes, secure control, navigation resilience, payload integration, maintainability and the components that can realistically be assembled or produced in country.
Counter-drone and layered air defence
Treated as an integrated system rather than a product: detection and tracking, command, electronic effects, low-cost interceptors and existing air-defence assets have to work together against mass attack.
Electronic warfare and spectrum awareness
Inseparable from drone operations, communications and force protection: spectrum sensing, interference detection, resilient navigation and data links, counter-UAS electronic effects, and tools that let a commander read the electromagnetic environment. Testing is secure and coordinated with national frequency, cyber and safety authorities.
Battlefield awareness and decision systems
An open, sovereign architecture for data fusion, mission control, machine-assisted detection and after-action analysis, connecting sensors, missions, electronic warfare and air defence to the commander, with operational data remaining under the client's control.
Missiles and longer-range precision effects
A separate track, availability first, with licensing and production negotiated separately afterwards. No capital or volume commitment is made until the manufacturer, ownership, production record, design rights, export position, integration plan and the client's own requirement have been independently verified.
Drones, counter-drone, electronic warfare, awareness and missiles are not separate catalogues. Interfaces and operational integration are funded as deliberately as the products themselves.
How a domain challenge becomes a system →A programme conversation starts with the requirement, not the contract.