Make any drone autonomous.
What we build
A drone is two computers that barely talk to each other. One is the autopilot, which is excellent at holding an attitude and following a waypoint and has been for fifteen years. The other is whatever small Linux board someone bolted on to do the interesting work, and that one is usually a pile of scripts. We build the software for the second computer, and the ground software that makes it useful: an onboard agent, a browser-based ground control station, the same agent in a ground-station role, and a workstation profile for the operator's machine.
The result is an open compute layer rather than a product line. Install the agent on a supported ARM64 board, plug it into a flight controller, and you get video and telemetry over a long-range radio link, mission planning, on-vehicle perception where the hardware supports it, and an extension system so a payload vendor can ship a driver and a panel without asking us for permission. Typical first-party stacks give you a closed app and a supported accessory list. We give you the source and a capability model.
WHY OPEN SOURCE
Because the alternative does not survive contact with a customer
Flight software you cannot read is a liability
Anything that can command an aircraft should be auditable by the person responsible for that aircraft. If a safety behaviour surprises you, you should be able to go and read why, not file a ticket.
Fleets outlive vendors
A fleet bought this year will fly for a decade. GPLv3 means the software cannot be withdrawn, re-licensed against you or quietly moved behind a subscription. Worst case, you fork it.
Hardware moves faster than any one team
New boards, new accelerators, new radios, new payloads land constantly. A closed compatibility list is always behind. An extension system and 20 board profiles in a public repository are not.
It also disciplines us. Every claim on this site has to survive someone reading the repository that backs it, which is why maturity labels on these pages say In Development when something is in development. A status surface that reports a known-false value is a bug we fix, not a quirk we document.
FACTS
The short version
- Founded
- 2026
- Headquarters
- Bangalore, India
- Software license
- GPL-3.0
- Public repositories
- 6
- Autopilots supported
- ArduPilot, PX4, Betaflight, iNav
The platform is designed for a global audience and tested against the way regulators everywhere actually work. Compliance exports target the ICAO-shaped generic record first, with jurisdiction-specific templates layered on top for authorities including the FAA, EASA, CASA, DGCA, the CAA, Transport Canada and the JCAB.
THE LICENCE STANCE
GPLv3, on purpose
Not a permissive licence with a commercial edition bolted on, and not an open-core split where the useful half is proprietary.
The agents, the ground station, the extension monorepo and the Android app are GPLv3. The MCP server is MIT, because a protocol adapter that other tools embed is more useful permissive. The documentation is dedicated to the public domain. There is no paid edition of anything, and no feature that switches on when money changes hands. We charge for hosting we run and engineering time we spend, and that is the entire commercial model.