KairOS Drone Agent is the future onboard software module of the Unmanned Sport ecosystem. It connects the flight controller, video, local APIs, communications and extensions on a Linux SBC, working alongside #bezpiLOTa Mission Control and #bezpiLOTa Ground Agent.
An independent KairOS product concept; implementation, compatibility and performance require the project’s own testing.
KairOS repository ↗On this page +
An onboard layer within an open ecosystem
The ecosystem includes onboard companion-computer software, a browser ground control station and a separate ground-station node for long-range radio. KairOS itself is responsible only for Drone Agent: a Linux SBC is added to the existing flight controller with separate responsibility for communications, video, integrations and on-vehicle computing.
The target contract includes ArduPilot, PX4, Betaflight and iNav. The adjacent Mission Control should connect over USB, Wi-Fi, LAN or remote relay and combine configuration, calibration, mission planning, firmware tools, gamepad control and live video. This is an architectural plan, not a claim of completed compatibility.
Three components that can work independently
#bezpiLOTa Mission Control
Browser-based GCS for connectivity, FC configuration, flight, mission planning, firmware and video. Direct USB can work without an agent.
KairOS Drone Agent
Hybrid Rust/Python on a Linux SBC: REST, MAVLink routing, video, cloud relay and radio in Rust; AI/vision, bootstrap and plugin runtime in Python.
#bezpiLOTa Ground Agent
The same agent codebase in a ground-station profile: WFB-ng reception, local distribution and a field interface for a laptop, phone or display.
A full setup is not required. Mission Control can connect to an FC over USB for bench work. Drone Agent can use Wi-Fi or 4G without Ground Agent. Ground Agent is needed when a dedicated receive/relay node is required for a radio link, local access point, USB tethering or HDMI kiosk.
The flow from flight controller to browser
Flight Controller
ArduPilot, PX4, Betaflight or iNav controls motors, stabilization, GPS and sensors.
MAVLink / MSP link
UART or USB connects the FC to Drone Agent; direct USB can also connect straight to the browser.
Drone Agent
Routes telemetry and commands, processes camera input, serves local APIs and optional cloud connectivity.
Video / radio
A USB/MIPI CSI camera feeds the H.264 pipeline; the stream travels over LAN/WebRTC or WFB-ng.
Ground Agent
Receives the long-range link and exposes it through Wi-Fi AP, USB tethering, Ethernet or HDMI.
Mission Control
The browser combines control, mission context, video, health and logs.
Flight Controller ⇄ MAVLink UART ⇄ KairOS Drone Agent
Camera → USB / MIPI CSI → H.264 pipeline
Drone Agent ⇄ WFB-ng / LAN / 4G ⇄ Ground Agent or Browser
Ground Agent → Wi-Fi AP / USB tether / HDMI → Mission ControlWho needs a programmable onboard layer
FPV builders and pilots
Modern GCS, configuration, mission planning and video on your own vehicle.
Researchers and engineers
REST, WebSocket, SDK, simulation and extensions for reproducible integrations.
Commercial operators
Mapping, inspection and agriculture workflows with observable missions and customization.
Students and educators
Open boundaries from protocol to UI for learning and experimentation.
Hardware integrators
A unified agent layer across different SBCs, cameras, radios, sensors and flight controllers.
Target ecosystem feature map
| Component | Planned feature scope |
|---|---|
| Mission Control | WebSerial; more than 60 configuration panels; 9 calibration wizards; 7 mission pattern generators; 3D simulation; geofence and rally; gamepad/HOTAS at 50 Hz; firmware flashing; WebRTC video; demo drones; SITL; tablet-responsive dark UI |
| Drone Agent | One-line install; serial FC autodetection; H.264/WFB-ng/WebRTC; MQTT + Convex; REST :8080; setup webapp; SSH CLI; Python SDK contracts; 17 board profiles; update command |
| Ground Agent | WFB-ng RX; Wi‑Fi AP; USB CDC-NCM tether; OLED + buttons; HDMI kiosk; captive setup portal |
Licensing is defined per artifact
| KairOS artifact | How the license is established |
|---|---|
| Drone Agent core | A LICENSE file in the repository before the first public release |
| Documentation | A separate explicit statement in the documentation |
| Hardware designs | A license alongside each source-file collection |
| Extensions | License and third-party notices in every package manifest |
Until its own LICENSE files exist, the website does not attribute a specific software or hardware license to KairOS. The core, documentation, design files and extensions must receive explicit, independent legal terms.
Choose a path for your current task
Understand the data flow
Go to How It Works: connection modes, MAVLink, video, cloud relay and arm trace.
Explore Mission Control
Planned local demo mode without a real vehicle or hazardous commands.
Prepare the companion SBC
Choose an installation path and complete local Drone Agent setup.
Build a field receiver
Ground Agent hardware, installation, client paths and troubleshooting.