ShoalOS Core Platform
Eight software layers, from the payload’s sensor drivers to the partner SDKs and mission applications. Three SDKs and an operator view sit around the payload.
- Sheet
- Platform · Architecture
- Layers
- L0–L7
- Status
- Conceptual interfaces
- Revised
Three SDKs and an operator view
Payload setup, video, squad state and mission control in one software platform around the payload.
SenzFusion SDK
Configure the payload and expose navigation data to the host aircraft.
SquadSense SDK
Share position quality, link status and system health across the team.
Coming soonVision SDK
Stream video from the payload. Edge ATD/ATR is coming soon.
Planner / operator view
Prepare routes, monitor team state, review outcomes and reassign tasks.
Eight layers. Trace a workflow.
Expand a layer for its scope, or pick a workflow to see which layers it runs through.
All eight layers. Services depend on the layers below.
-
The ShoalOS Core Platform SDKs. The SenzFusion SDK configures the payload and exposes navigation data to the host aircraft. The SquadSense SDK shares position quality, link status and system health across the team. The Vision SDK streams video; edge ATD/ATR is coming soon.
Together with L0, the SDKs define the integration work required for each partner.
-
Fleet registry, health and telemetry, firmware updates, key management, audit and the operator UI.
Coming soon: mission deployment that sends the flight plan to the autopilot and reference data to the payload, then records which versions were loaded.
-
Nav Planner authors and reviews the flight plan before flight. The planner / operator view prepares routes, monitors team state, reviews outcomes and reassigns tasks. OspreyVMS handles video viewing, recording and evidence.
Coming soon: bringing the payload’s thermal video and object tracks into OspreyVMS.
-
Reference retrieval, image conversion, tiling and the mission data store.
Coming soon: a mission package that bundles the reviewed route with terrain maps, thermal reference imagery and payload configuration.
RECONN.EARTH -
Each payload shares its navigation confidence and health with the squad over a secured data link, so the team can retask around a failed sensor, drone or objective.
SquadSense -
Onboard reference cache, waypoint context, drift monitoring and fallback policy. Course corrections go to the host autopilot, which keeps flight control.
Coming soon: dynamic rerouting during the mission.
Payload hardware -
IMU motion prediction, the radar altimeter ground profile, radar map matching for drift correction and a thermal scene check against the reference scene. A position fix is accepted when radar and thermal agree; GNSS input is used to detect a contested environment.
Target hardware: an FPGA system-on-chip with fixed-timing logic and ARM cores. Timing and operating envelope not yet validated.
SenzFusion -
Drivers and interfaces for IMU, barometer, airspeed, radar altimeter, imaging radar and thermal camera, with GNSS as a check input. Autopilot interfaces cover PX4, ArduPilot and MAVLink, alongside gimbals and radio links.
OEM integration at this layer connects each vehicle’s sensors, actuators and communications hardware.
↑ Services depend on the layers below · Hardware foundation at L0
Time, security, logging
Three concerns run through the whole stack rather than sitting in one layer.
One clock
Sensor synchronisation, frame timing and consistent timestamps across the stack.
Trust, enforced per layer
Keys, encryption and air-gapped deployment. The control plane manages trust; each layer enforces it.
Traceable decisions
Traceability from sensor events and navigation decisions through mission records and audit evidence.
How a mission moves through the stack
Watch the flight simulationBefore flight
Nav Planner exports the route. Packaging reference data and loading it onto the vehicle is coming soon.
On the vehicle
IMU prediction, radar map matching and the thermal scene check produce the position fix.
Back at the centre
Mission data feeds the applications; health, telemetry and audit records feed the control plane.
Built to run on your side of the wire
Self-hosted where it matters, traceable end to end, and with target decisions kept by people.
Self-hosted fleet and trust
Fleet registry, health and telemetry, firmware updates, key management and audit run on your infrastructure.
On-premise or air-gapped
Keys, encryption and air-gapped deployment are cross-cutting. RECONN.EARTH and OspreyVMS run cloud, on-premise or air-gapped.
Encrypted evidence
OspreyVMS encrypts media at rest and in transit, with legal holds for chain of custody.
Signed serial link
Course corrections reach the host autopilot over a signed serial link. The autopilot keeps flight control.
Audit evidence
Traceability from sensor events and navigation decisions through mission records and audit evidence.
Human in the loop
Target decisions stay with the operator and the host system.
See it navigate
Watch the flight simulation and follow a mission through a GNSS outage.