Flight software
We write everything the aircraft runs
We write the flight firmware and train the detection models that ship inside it. Register an aircraft and your account shows which release it is running, and whether a newer release is published for that board.
Firmware
Match the release to your board, not to your model name.
Firmware is published per board target. A release that does not name your hardware revision is not a release for your aircraft.
Every releaseCheck the file before you flash it
Published SHA-256 checksum, in the same release row as the download button.
Scoped to a board, not to a product name
Every release lists its board target and the range of hardware revisions it supports, with the microcontroller beside the target code.
We withdraw a release instead of deleting it
The release stays in the history, marked withdrawn, and we stop serving it. If one of your registered aircraft is running it, we tell you to stop flying that aircraft until you flash a safe release.
Your download history stays on the account
Every download is recorded against your account. The firmware center shows the running total and your most recent downloads.
What each release channel is tested to
- stable
- Flown on every hardware revision the release supports before it is published.
- beta
- Feature previews. These have passed the bench and nothing further.
- dev
- Engineering builds. No test cycle has finished on one.
If your aircraft is on stable, we never point it at a beta. We offer beta and dev builds only for an aircraft already running one of them, and only on an account with access to that model's firmware. The license defines each channel and names what each one is appropriate for.
Onboard vision
Detection models trained here, shipped inside the firmware.
We train the detection models ourselves and export them to ONNX and TensorRT for the compute on the aircraft. They are distributed inside the release, which means they carry the same checksum, the same channel and the same license terms as the rest of the firmware.
Nothing we ship is a weapon detector, a person tracker or an alarm. No accuracy figure for any such class has been measured here or published anywhere, and a vendor quoting you one is quoting a number from a different product.
How the training runs goUp to 24 aircraft on an account
Record the hardware revision and the release each aircraft is running. We use that record to show you the right download, and you can attach an aircraft to a support ticket instead of describing it.
Four states, not a feed
Every aircraft shows one of four states: current, update available, recalled, or not tracked. On a recall we name the release to move to, once a safe release exists.
FAA registration and its expiry date
Store your own registration number and its expiry against an aircraft, and we flag it 60 days before it lapses.
No separate charge for firmware
Any signed-in account can download stable releases. Buying an aircraft adds the beta and dev channels for that model, and nothing about that access expires.
What we do not run for you.
There is no fleet console to buy and no staged rollout you can schedule. Firmware is a file you download and flash yourself. Nothing we ship reports home, and we have no way to send a command to your aircraft over the air.
Flashing is yours to do and yours to get right. Check the board target, the hardware revision range and the checksum first, because a release for the wrong board will brick the board you have.
Beta and dev builds carry no flight-test warranty. If an aircraft is doing work that matters, keep it on stable.
Firmware license
Talk to us
Tell us which aircraft you are running and we will tell you which release to flash.
Contact support