A useful open-source robotics page should answer a visitor’s first question in five seconds: what can I try safely, with which official project, and what record should I keep? It should not hide the starting point behind a product pitch or imply that popularity proves safety.
This guide maps mature UAV and UGV ecosystems to jobs. It links to official repositories and documentation, then adds a UAMKT evidence layer that records the exact release, scenario, result, unresolved issue, and human decision. GitHub stars and forks are cited only as public adoption proxies as of 25 September 2026. They are not website traffic, downloads, active installations, or performance evidence.
Choose the job first
| Job | Official starting point | What to preserve |
|---|---|---|
| Simulate an aircraft | PX4 Simulation or ArduPilot SITL | Exact release, simulator, vehicle model, configuration, logs |
| Plan and review a mission | QGroundControl User Guide | Application version, operating system, plan export, operator findings |
| Find ROS packages | ROS Index | ROS distribution, package version, dependencies, component license |
| Set up UGV navigation | Navigation2 Setup Guides | Robot model, world or map, plugins, tuning, result |
| Test a synthetic world | Gazebo Sim | Simulator release, model and world sources, asset licenses |
| Study a modular autonomous-vehicle stack | Autoware Universe | Package graph, interface boundary, supported release, unresolved gaps |
PX4 documents software-in-the-loop and hardware-in-the-loop simulation and provides a Docker-based path across aircraft and rover models. ArduPilot SITL runs vehicle software without hardware and documents Copter, Plane, Rover, and Sub paths. QGroundControl leads the user through download, interface orientation, first-flight preparation, and operation. Nav2 organizes adoption around first-time robot setup, configuration, plugins, tuning, APIs, and migration. Autoware exposes a modular package structure rather than presenting the stack as one opaque application.
Treat popularity as a discovery signal, not proof
The most visible public GitHub signals in the reviewed set are ArduPilot at 15,921 stars and 21,440 forks, and PX4 at 12,693 stars and 16,069 forks as of 25 September 2026. QGroundControl, ROS 2, Navigation2, Gazebo Sim, and Autoware Universe also show substantial public repository activity. Those figures help prioritize what a new visitor is likely to encounter; they do not establish traffic, download volume, field performance, regulatory approval, or suitability for a specific mission.
The practical benchmark is the shape of the onboarding journey. Mature ecosystems expose a clear install or simulation path, task-oriented documentation, version and migration information, searchable packages or modules, and a contribution route. UAMKT applies those patterns without copying the upstream code or branding.
Keep the UAMKT layer separate
An evidence overlay should be easy to remove without changing the upstream flight or navigation project. Pin the upstream version, preserve its notices, inventory every dependency and asset, and keep UAMKT schemas, dashboards, synthetic scenarios, and review records in a visibly separate layer. This protects attribution and makes updates, security review, and license decisions auditable.
For CBRN research, the public boundary is narrower. Publish only glossary, interface descriptions, schemas, synthetic data, simulants, surrogate-surface scenarios, and human-review records. Do not publish live-agent procedures, chemical recipes, doses, flow or pressure settings, thermal setpoints, actuator commands, autonomous-release logic, target selection, or controlled vulnerabilities.
Free starter map
Download the UAV/UGV Open-Source Starter Map. It contains an air/ground decision guide, official upstream links, an adoption-signal snapshot, synthetic tabletop briefs, and a blank simulation evidence record. It contains no third-party source code and no hardware-control logic.
Then use UAMKT Open Studio to compare browser tools, source packages, book companions, licenses, and public release boundaries.
Falsification gate
This approach fails if visitors cannot reach a first action in five seconds, if the download cannot be verified, if an upstream link or license is stale, or if GA4 records page views but no tool starts, downloads, or qualified contacts. Review Search Console queries and GA4 events at D+7, D+14, and D+28; revise the landing query and first action before adding more content.
