CUSTOM GCS
The operator is the last mile. We build the software they actually use.
What we build
Ground control, built around your operator
Every capability we deliver has to surface somewhere a crew can act on it. We build custom ground control software on open source foundations — branded QGroundControl builds, TAK integrations, and purpose-built plugins — so the aircraft and the operator are designed together rather than bolted together.
- QGroundControl
- TAK
- MAVLink & MAVSDK
- Qt / C++
- Python
- Docker
Custom QGroundControl Builds Branded builds, custom operator UI, and mission widgets.
QGroundControl is open source, which means we can change anything about it — and hand you a build you can keep changing. We strip what your crews do not need, add the widgets they do, and brand it as yours rather than shipping a generic tool with your logo pasted on.
Platforms integrated
- Branded builds and custom theming
- Custom operator UI and layouts
- Mission planning widgets
- Purpose-built plugins
- Live telemetry and status displays
- In-app warnings and diagnostics
- Windows, Linux, and Android targets
TAK Integration Pushing aircraft, sensors, and detections into a shared operating picture.
When a crew already runs TAK, the aircraft should appear there rather than on a second screen. We publish vehicle position, sensor state, and detections into TAK so air assets show up alongside everything else the team is tracking.
What we integrate
- Vehicle telemetry into TAK
- Sensor and payload state
- Detection and contact reporting
- Operator tasking workflows
- Alongside or instead of QGroundControl
Handhelds & Controllers The hardware crews actually carry into the field.
Ground control software is only as good as the device it runs on. We target the controllers your crews already own, including the constrained ones, and make sure the build fits the screen and the input method rather than assuming a laptop.
Platforms integrated
- Herelink
- UXV
- H16
- Android devices
- Windows devices
- Linux devices
- Custom QGC builds per device
Link Awareness & Telemetry Making link state something the operator can see and the aircraft can react to.
Most fly-aways start with a link the operator did not know was degrading. We surface link quality, bandwidth, and failover state in the GCS, and wire the autopilot so the aircraft behaves sensibly when the link goes rather than waiting to be told.
Datalinks supported
- Doodle Labs
- Microhard
- DTC
- Herelink
- Mobile 4G/5G — Telit, Sierra, Quectel
- Link state surfaced in the GCS
- Autopilot failsafe behaviour
Autopilot firmware and onboard behaviour are covered on the Custom Autopilots page.
Need a GCS your crews will actually use?
Tell us the devices your operators carry and what they need on screen. We will come back with a scope and a build plan.