See, track, and act on-device
Usable today. Early access — some pieces run behind a feature flag and APIs may shift between releases.
How it works
Camera to flight stack, all on the companion
Frames flow from the camera through inference and tracking, then out as guided setpoints. Nothing leaves the vehicle.
Capabilities
A registry, not a single model
Fetch, download, and cache detection models on the companion. Models stay on the device and run locally.
Sideload your own model through the ground station. A checksum is verified before it is added to the catalog.
The agent detects the board's accelerator and available compute, then picks the matching model variant automatically.
Optical flow and monocular visual-inertial odometry hold position where GPS is unreliable or unavailable.
Hardware
Six accelerator backends
The registry carries model variants for each accelerator. Selection is automatic, based on the board and the compute it advertises in TOPS.
Vision navigation
Fly where GPS cannot
The vision navigation extension installs through the extension registry and adds optical flow plus monocular VIO.
With vision navigation, a drone holds position and navigates where GPS is unreliable, indoors, under a canopy, or near tall structures. It supports ArduPilot 4.5+, PX4 1.14+, and iNav 7.0+, with an auto-detect probe for the supported camera and compute setups.
Put vision on your drone
The model registry and vision navigation are open-source and documented on GitHub. Bring your own model or start from the catalog.
View on GitHub