Free browser tools for evidence-first drone operations.
Start with reference coordinates, a mission record, a CSV log, or a boundary audit—not a black-box claim. UAMKT Open Studio turns supplied operation data into reviewable evidence while keeping routes, actuators, chemicals, and legal decisions outside the public toolchain.
Publish in evidence order.
Each release begins with recorded or simulated data and a human review record. Vehicle, pump, valve, chemical, and dose control remain outside the public toolkit.
- LIVE · v0.1.0 · Apache-2.0 source
Hull Mark Mapping Workbench
Plot local ship-side reference points and intended line segments, screen measured samples with transparent deviation statistics, and export a human-review record.
- LIVE · v0.1.0 · Apache-2.0 source
Mission Companion
Build a preflight and postflight evidence package from manual inputs, then export canonical JSON and an evidence-index CSV.
- LIVE · v0.1.0 · Apache-2.0 source
Spray Log QA
A browser-only CSV quality-assurance dashboard for route traces, coverage gaps, boundary proximity, and JSON review reports.
- LIVE · v0.1.0 · Apache-2.0 source
No-Spray Guard
A browser-only audit of supplied boundary-distance, altitude, speed, and spray/flow state values. Findings link back to their CSV source rows.
- BETA · Stage 0 · open record
Drone Disposal Decision (Korea)
Classify reporting and deregistration paths in-browser, then export a non-certifying EoL intake record. No government submission, transport, or recycling.
What each layer gives you.
| Layer | Default | License / note |
|---|---|---|
| Flight stack (multirotor) | ArduPilot Copter | GPLv3 — derivative firmware must be shared |
| Flight stack (alt) | PX4 | BSD-3-Clause — permissive, vendor-friendly |
| Flight controller | Pixhawk (Cube / 6X class) | Open-hardware reference design |
| Ground control | QGroundControl / Mission Planner | Open-source GCS, cross-platform |
| Comms | MAVLink | Open messaging protocol, well-documented |
Five tools, five explicit data boundaries.
| Tool | Accepted input | What it does not do |
|---|---|---|
| Hull Mark Mapping | Local control points, target segments, and measured samples | No pixel transform, 3D reconstruction, flight planning, class/legal or dimensional acceptance |
| Mission Companion | Manual mission fields and evidence references | No native log parsing, route planning, or authenticity validation |
| Spray Log QA | Documented UAMKT CSV schema | No ArduPilot BIN or PX4 ULog parsing; no coverage certification |
| No-Spray Guard | CSV with precomputed geofence_distance_m | No polygon engine, legal distance prescription, or actuator control |
| Drone Disposal Decision | Manual business-use, weight, and prior-reporting answers | No government submission, legal ruling, transport, recycling, or certification |
GPLv3 vs BSD-3-Clause is a shipping decision.
ArduPilot is GPLv3: if you modify the firmware and distribute the aircraft, you owe the modified source under the same license. For most build-it-yourself and research programs this is a feature, not a constraint — it keeps the stack auditable end to end.
PX4 is BSD-3-Clause: permissive, which is why it shows up in commercial vendor stacks. You can keep modifications closed. The trade is that the audit story is weaker, because you can no longer assume the shipped firmware matches the public tree.
- Research / internal builds → ArduPilot is usually the cleaner default.
- Commercial product with closed firmware → PX4’s license fits better.
- Either way: pin the exact commit, and keep the build reproducible.
Figures and configurations on this page are illustrative, drawn from public open-source documentation (subject to verification). Operation in the Republic of Korea requires national airworthiness rules, KC radio-frequency certification, and expert validation. All build content is published only after export-control and dual-use review. Open-source components are governed by their own licenses (ArduPilot: GPLv3, PX4: BSD-3-Clause). This page is not legal or export-control advice.