For vehicle makers

Integrate ShoalOS into your vehicle

We supply the navigation payload and the mission software around it. You keep the vehicle, the customer relationship and certification.

Discuss your integration See the engagement path
A rugged machined navigation payload enclosure with a camera window, a sensor panel and a circular connector, on a workshop bench.
Navigation payloadConcept render
Sheet
Partners · OEM integration
Interfaces
PX4 · ArduPilot · MAVLink
Fit
Build or retrofit
Revised
Sheet 01ScopeComponent supplier

What we supply

A self-contained navigation subsystem and the software around it. Your airframe and autopilot stay as they are.

01 · Payload

Payload + SDK

GNSS-independent navigation as a self-contained subsystem. Your airframe and autopilot stay as they are.

02 · Software

Mission software

Planner and operator tools, with SquadSense and Vision functions around the payload — coming soon.

03 · Fit

OEM integration

Best suited to defence drone makers with modular platforms and accessible payload interfaces.

Roadmap Coming soon

Terminal Guidance System with Automatic Target Detection and Recognition (ATD/ATR).

Sheet 02Engagement pathBuild · Test · Deploy

From prototype to pilot programme

Three stages, each with a clear output, before any scale-up decision.

  1. 01 · Build

    Prototype development

    Integrate sensors and compute on your airframe, and set up the imagery software.

  2. 02 · Test

    Run a controlled POC

    Integrate the payload. Measure accuracy, latency, power, weight and safe fallback on the host aircraft.

  3. 03 · Deploy

    Run a pilot programme

    Review acceptance results. Agree deployment scope, support, commercial terms and a scale-up decision.

[01] Delivery
Partner-led delivery through OEMs, integrators and defence manufacturers.
[02] Fit
Fitted at build or retrofitted onto existing airframe programmes.
[03] Supply
Component supplier for the SenzFusion payload, SDKs, mission software and reference imagery.
[04] One path
One integration path per partner, covering payload, SDKs, licences, imagery and deployment.
Sheet 03Security & controlAcross every layer

Built to stay on your infrastructure

The control plane manages trust; each layer enforces it. Decisions on targets stay with people.

L6 · Control plane

Self-hosted control plane

Fleet registry, health and telemetry, firmware updates, key management, audit and the operator UI.

Deployment

Air-gapped deployment

RECONN.EARTH runs in the cloud, on-premise or air-gapped; OspreyVMS is self-hosted, on-premise or air-gapped.

Encryption

Encrypted media, managed keys

OspreyVMS media is encrypted at rest and in transit. Keys are managed by the control plane.

Vehicle link

Signed serial link

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

Logging

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.

Sheet 04InquiryIntegrations · pilots · retrofit programmes

Discuss your integration

Integrations, pilots and retrofit programmes.

What happens next

  1. 01
    BuildPrototype developmentSensors and compute on your airframe; imagery software set up.
  2. 02
    TestControlled POCAccuracy, latency, power, weight and safe fallback measured on the host aircraft.
  3. 03
    DeployPilot programmeAcceptance review, deployment scope, support and commercial terms.

Organisation type
Airframe type, autopilot, payload interfaces and when you would like to start.

Do not include classified, export-controlled or other sensitive information. Describe your platform at an unclassified level; we will arrange an appropriate channel for anything further.