The software is what makes it a fleet.
A PhantomNav vessel is a proven hull and propulsion package, organised around one autonomy stack. That stack, and the discipline behind it, is what we build.
Layered, so no single failure is in charge.
Mission logic, vehicle control and safety are separate layers with separate jobs. The safety layer sits between every command and the propulsion, and the hardware stop is designed not to depend on any computer above it.
- Operator in command, with autonomy doing the hours
- Independent safety gates that can refuse to arm or move
- Failsafes that fail toward stopping, not toward going
What runs on every vessel.
Shared across all eight classes and configured, not rewritten, for each.
Open, auditable autopilot
Vehicle control is built on a widely deployed open-source autopilot, extended with our own mission and safety logic. Customers get an independent path to inspect how their vessel makes decisions.
Resilient positioning
Our navigation engine blends independent position sources and flags interference in real time. It has been evaluated against recorded real-world jamming and spoofing trial data.
Fleet operations console
One console to plan missions, watch the fleet, hand off control and keep the record. It is in production today, behind access control and multi-factor sign-in.
Modular payload pod
A common electronics and power pod carries the vessel’s compute, communications and sensor interfaces, so payloads move between classes instead of being re-engineered for each.
Redundant links
Line-of-sight radio, cellular and satellite paths are managed together, and the vessel knows what to do when a link goes quiet.
Proven in simulation first
Safety behaviors are exercised in software-in-the-loop simulation against the exact autopilot release we ship, before it goes near the water.
Evidence over adjectives.
We hold ourselves to a simple rule: no claim without the test that backs it. Designs are checked by automated gates, audited by reviewers who did not write them, and every failure we find is recorded as prominently as every success.
Automated design checks
Electrical, layout and safety rules run on every change. A failing gate is a finding, never an obstacle to work around.
A failure log we keep, not hide
Every falsified assumption stays on the record next to its fix, so partners can see exactly how the system was hardened.
Want the technical briefing?
Architecture detail, test evidence and program status are available to qualified partners under the appropriate agreements.