/technology / software
The layer that runs the fleet.
Mission services, ground control, and the health gate every flight passes through.
Mission services
Scheduling
Missions run on defined cadences.
Execution
Sequenced flight with safety logic, ROS 2 based.
Safety logic
Enforced boundaries and degraded-mode handling.
Pre-flight
No health, no flight.
- 01
Estimator stream
Pos, Vel, Att, and Hgt flags must report a live VIO estimate before the mission can start.
- 02
Sensor fusion
Fusion and accelerometer checks confirm the camera and IMU agree with each other.
- 03
Link & power
Telemetry link and battery state are verified against what the mission needs.
- 04
Arm gating
ARM stays refused until every check passes — the drone cannot start unhealthy.
Ground control
MODE MISSION
BAT 97% · LINK OK
VEL 0.9 M/S
Flight diagnostics
Every log gets a post-flight autopsy.
PX4 Flight Doctor reads a flight's .ulg log and runs 30 diagnostics grounded in the PX4 source message definitions — vibration, EKF health, GPS, control-loop tracking, and the causal chains between them. Every finding maps to a specific PX4 parameter to change, not generic advice.
It's live and free to try, with an interactive ULog explorer and a 3D flight replay in the browser.
Analyse a log at log-analyser.app↗Integrations
Reports where your systems can read them.
Mission output exports in WMS-compatible formats. A reporting API is in development for pilot partners.
Updates
How software reaches the fleet.
Versioning and update flow to deployed fleets are handled deliberately, so operators know exactly what's running.