Platform/ L0–L7

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.

Four conceptual interface panels: SenzFusion SDK with attitude and navigation uncertainty, SquadSense SDK with a three-UAV map, Vision SDK video stream, and a planner/operator route view.
ShoalOS Core PlatformConceptual interfaces
Sheet
Platform · Architecture
Layers
L0–L7
Status
Conceptual interfaces
Revised
Sheet 01SDKsPartner interface · L7

Three SDKs and an operator view

Payload setup, video, squad state and mission control in one software platform around the payload.

01 · Configure · L7 / L1

SenzFusion SDK

Configure the payload and expose navigation data to the host aircraft.

02 · Coordinate · L3

SquadSense SDK

Share position quality, link status and system health across the team.

Coming soon
03 · Perceive · L7

Vision SDK

Stream video from the payload. Edge ATD/ATR is coming soon.

04 · Operate · L5 / L6

Planner / operator view

Prepare routes, monitor team state, review outcomes and reassign tasks.

Sheet 02Software architectureRead from the foundation, L0 ↑ L7

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.

↑ Services depend on the layers below · Hardware foundation at L0

Sheet 03Across every layerL0–L7

Time, security, logging

Three concerns run through the whole stack rather than sitting in one layer.

Time

One clock

Sensor synchronisation, frame timing and consistent timestamps across the stack.

Security

Trust, enforced per layer

Keys, encryption and air-gapped deployment. The control plane manages trust; each layer enforces it.

Logging

Traceable decisions

Traceability from sensor events and navigation decisions through mission records and audit evidence.

Sheet 04WorkflowsGround · vehicle · centre

How a mission moves through the stack

Watch the flight simulation
L4 → L2

Before flight

Nav Planner exports the route. Packaging reference data and loading it onto the vehicle is coming soon.

L0 → L1 → L2

On the vehicle

IMU prediction, radar map matching and the thermal scene check produce the position fix.

Vehicles → L5 / L6

Back at the centre

Mission data feeds the applications; health, telemetry and audit records feed the control plane.

Sheet 05Security & controlYour infrastructure

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.

L6 · Control plane

Self-hosted fleet and trust

Fleet registry, health and telemetry, firmware updates, key management and audit run on your infrastructure.

Deployment

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.

Media

Encrypted evidence

OspreyVMS encrypts media at rest and in transit, with legal holds for chain of custody.

L1 → autopilot

Signed serial link

Course corrections reach the host autopilot over a signed serial link. The autopilot keeps flight control.

Logging

Audit evidence

Traceability from sensor events and navigation decisions through mission records and audit evidence.

Control

Human in the loop

Target decisions stay with the operator and the host system.

Flight simulation

See it navigate

Watch the flight simulation and follow a mission through a GNSS outage.