UAV manufacturers and integrators
Provide customers with an operator environment built around your aircraft, payload, and workflows rather than sending them into a generic ground station.
Flightdeck · Design-partner alpha · v0.1.0-alpha.1
Browser-native pilot workstation for UAVs.
Plan terrain-aware missions, operate the aircraft, monitor video and traffic, and use RTK, radio, firmware, parameter, and vehicle tools from one private operating environment.
Flightdeck is designed for UAV manufacturers, integrators, flight-test teams, and autonomy developers whose aircraft do not fit inside a vendor-controlled dock ecosystem.
01 — Evaluation profile
ArduPlane.
The current cockpit and command model are oriented around custom fixed-wing aircraft using ArduPlane.
Current alpha profile · Fixed-wing
02 — Deployment
Private per vehicle.
Each supported aircraft receives one isolated Flightdeck runtime in a self-hosted operator environment.
Self-hosted · Isolated runtime
03 — Command authority
Identity-scoped.
SPIFFE mTLS identifies production operators, while one exclusive write lease gates commands sent toward the aircraft.
SPIFFE mTLS · vehicle.write lease
04 — Links
Vehicle and media.
MAVLink vehicle traffic uses the QUIC rover link, with WebRTC carrying browser-native video feeds.
MAVLink · QUIC · WebRTC
01 / Who it is for
Built for aircraft that need their own operating environment.
Flightdeck starts with the vehicle, payload, operator, and operation rather than a universal feature matrix.
Fixed-wing and VTOL teams
Plan and inspect terrain-relative operations, understand estimated flight paths, and operate from flight instruments designed around aircraft state.
Flight-test and field engineers
Configure radios, RTK, firmware, parameters, files, telemetry, and live operations from the same workspace.
Autonomy and payload teams
Integrate perception, companion computers, camera feeds, visual guidance, and custom MAVLink interfaces without building the complete operator shell from scratch.
02 / Available today
One workspace from mission design to field support.
Each capability is built around an operator outcome, then adapted to the supported aircraft configuration.
Mission planning
Build terrain-relative surveys, inspect estimated flown paths, exchange QGroundControl plans, and resolve clearance or terrain-coverage issues before upload.
Live operation
Keep instruments, mission progress, tactical map actions, weather, and acknowledged commands in one cockpit so operators retain aircraft context.
Video and traffic
Bring multiple WebRTC feeds, ADS-B, Remote ID tracks, and radar returns into the operating picture instead of splitting attention across tools.
Field engineering
Configure SiK radios, operate a u-blox RTK base, flash ArduPilot and PX4 firmware, inspect MAVLink, edit parameters, and retrieve vehicle files without leaving the browser.
Identity and authority
Authenticate production operators with private-PKI identities and gate rover-bound commands through one exclusive, identity-scoped vehicle.write lease.
Private deployment
Run one isolated Flightdeck environment per vehicle with a QUIC rover link, retaining control of operator access, data, and deployment boundaries.
03 / Alpha boundary
Current alpha scope.
The boundary is explicit. Production identity and command authority exist today; fleet orchestration, durable audit, and broader vehicle profiles do not.
Current release
Available now
- 01Public standalone planner and selected browser hardware tools.
- 02Per-vehicle Flightdeck runtime.
- 03ArduPlane-oriented cockpit.
- 04Verified mission, fence, and rally upload.
- 05Production SPIFFE mTLS operator and rover identity.
- 06Exclusive identity-scoped vehicle.write authority.
- 07Multi-feed WebRTC video.
- 08RTK, SiK, firmware, parameter, MAVLink, and FTP tools.
- 09Traffic, Remote ID tracks, radar, wind, and forecast weather.
Product boundary
In development
- 01K8S Operator-managed provisioning, grants, and revocation.
- 02Structured operational readiness.
- 03Camera and gimbal control.
- 04Durable command, lease, and incident history.
- 05Supervised visual guidance as a product workflow.
- 06Complete takeoff-to-recovery mission semantics.
- 07Broader ArduCopter, PX4, and VTOL profiles.
- 08Country authorization and U-space provider integration.
Design-partner conversations open
Deploy one supported configuration, not another generic demo.
We start with one vehicle, one autopilot, one payload, and one operation. The engagement ends with an installed operating environment, a compatibility and acceptance report, an operator runbook, and a defined support boundary.
Discuss a Flightdeck deploymentEngagement deliverables
- 01Aircraft and autopilot integration profile
- 02Private deployment and PKI
- 03SITL or hardware-in-the-loop acceptance
- 04Operator workflow and training
- 05Contained field evaluation
- 06Known-limitations and support record
Flightdeck / Supported deployment
Bring us the operation before the specification.
Tell us about the aircraft, payload, operating environment, and outcome you need. We will identify what Flightdeck already covers, what requires integration, and what evidence is needed before field use.