Solutions · Marine & Subsea Robotics
Built to run where the signal does not reach.
Operating system and fleet platform for autonomous underwater vehicles (AUVs), ROVs and offshore inspection rigs. Runs for days without connectivity, buffers every log on board, and recovers from bad updates on its own.
Autonomous robotics
Humanoid robot
Network assumption
OS update recovery
Sudden power loss
The challenges
What Admiral solves for Marine & Subsea.
No connectivity once the vehicle submerges.
Subsea vehicles run for hours or days with no radio link at all, then surface onto high-latency satellite or cellular connections for short windows.
You cannot send a technician to a vehicle offshore.
A bad OS or workload update miles offshore ends the mission. The machine has to verify every update locally and revert to the working slot on its own.
Thruster surges and battery cuts drop power without warning.
Emergency power cuts corrupt mutable filesystems and ruin mission logs unless the OS root is read-only and persistent state is written atomically.
Capabilities
Purpose built.
Runs offline for the whole mission.
Workloads execute with no cloud dependency. Telemetry, diagnostics and mission logs buffer to local storage and drain in order when the vehicle surfaces.
Updates verify themselves or roll back.
OS updates stage to the spare partition and must boot and pass health checks, or the bootloader brings the previous slot back without human intervention.
Survives hard power cuts cleanly.
An immutable, dm-verity verified root filesystem paired with copy-on-write persistent storage keeps the OS intact through sudden power loss.
The difference
With and without Admiral.
Without Admiral
- Cloud-dependent agents hang or crash once the vehicle leaves coverage
- A failed update offshore means recovering the vehicle and opening the hull
- Abrupt power cuts corrupt mutable root partitions and mission data
- Technicians spend days before each mobilisation hand-imaging vehicles
With Admiral
- Workloads run offline for days and flush buffered telemetry on surfacing
- Dual-slot A/B updates recover on their own if a new build fails to boot
- Read-only rootfs and copy-on-write storage survive hard battery cuts
- Outbound connection resumes automatically across satellite and cellular links
- Every vehicle dives with the exact signed build tested in the tank
Use cases
Where teams are using Admiral.
Autonomous underwater survey vehicles (AUVs)
Run side-scan sonar, bathymetry and seafloor mapping stacks across multi-day missions with deterministic software state on every dive.
Offshore energy and pipeline ROVs
Ship inspection models and control software to vessel-deployed ROVs over satellite links, with rollouts gated between dives.
Oceanographic buoys and surface vessels
Keep uncrewed surface vessels and sensor buoys patched, monitored and reachable over intermittent cellular and satellite backhaul.