Open sky, open source, today.
THE REPOSITORIES
Six repos, one platform
The ground station, the agents, the extensions, the Android app, the MCP server and the docs are each their own public repository. Star the ones you use and follow development in the open.
Ground Control Station
ADOSMissionControl
The browser ground station: fleet telemetry, mission planning, 3D simulation, the parameter editor, and the Cockpit.
Open on GitHub →Onboard, Ground & Workstation Agent
ADOSDroneAgent
One codebase, four profiles. MAVLink proxy, video pipeline, cloud relay, plugin host, and the ground-station radio stack.
Open on GitHub →First-Party Extensions
ADOSExtensions
The open extension registry: follow-me, MAVLink gimbal control, the SIYI optical pod, a FLIR Lepton thermal camera, vision navigation, the World Engine, and the extension SDK.
Open on GitHub →Native Android Ground Station
ADOSAndroidGCS
A Kotlin and Compose ground station for phones and tablets: video with a HUD overlay, flight controls, offline maps, and MAVLink over USB, WiFi, or the relay.
Open on GitHub →Model Context Protocol Server
ADOS-MCP
Read and control a drone or a fleet from an AI client, with a scope on every connection, a confirmation on anything that moves an aircraft, and an audit trail on every call.
Open on GitHub →The Docs Site
Documentation
Every guide, reference and runbook behind docs.altnautica.com, in the open alongside the code it documents.
Open on GitHub →LICENSING
Copyleft software, public-domain docs
Most of the software is copyleft so improvements stay open. The MCP server is MIT so it can be embedded in a closed AI client. The documentation is public domain.
- Mission Control
- GPL-3.0-only
- ADOS Agent
- GPL-3.0-or-later
- Extensions and SDK
- GPL-3.0-or-later
- MCP server
- MIT
- Android ground station
- GPL-3.0-only
- Documentation
- CC0-1.0
WHY OPEN
A shared compute layer beats a hundred private ones
The smart-drone compute layer has stayed first-party at every major manufacturer. Each one runs its own silicon, firmware, and SDK. That works for a single vertically integrated company, and it leaves every other drone builder starting from zero.
We publish the alternative. One open stack the whole industry can build on together, instead of each company rebuilding the same ground station, the same agent, and the same video link.
The best platforms are not the ones that win alone. They are the ones everyone else gets to build on.
CONTRIBUTE
Fork it, run it, send it back
Everything you need to build is in the open. Clone a repo, make it yours, and open a pull request when you have something to share.
Fork and build
Clone the repo, adapt it for your airframe or payload, and keep your changes in the open under GPLv3.
File issues
Report bugs and request features on the public issue trackers. Shared bugs get shared fixes.
Talk to the team
Join the Discord to ask questions, share builds, and shape what ships next.
Track every release
The changelog syncs straight from GitHub, so you always see what shipped and when.
$git clone https://github.com/altnautica/ADOSMissionControl.gitSo how does an open company make money?
The software stays free. Revenue comes from hosted cloud, hardware, and OEM support. Here is exactly how that works.