DATUMAn open-source dispatcher console for multi-vendor BVLOS fleets.
One operator console across 8–15 aircraft and 3–5 vendor families. Pluggable telemetry adapters, a 10-aircraft physics simulator, and a SHA-256 hash-chained audit trail. MIT licensed.
Architecture
One screen. Every vendor.
Multi-vendor BVLOS operations put a dispatcher in front of 8–15 aircraft from 3–5 different autopilot families. DATUM normalises their telemetry into a single grid and keeps a tamper-evident audit log of every action.
Vendor-agnostic telemetry
Adapters normalise to a single internal schema. The grid, alert engine, and compliance log are vendor-blind — the adapter SDK is the only thing that changes per OEM.
Tamper-evident audit log
SHA-256 hash-chained and HMAC-signed compliance events. Per-flight JSON bundle verifiable without DATUM installed.
Local-first deployment
Single process, SQLite only (WAL), no external database or message broker. Telemetry stays on the operator's machine by default.
Shift-based workflow
Handoff reports, watch timer, incident lifecycle with auditor-only status transitions, SMS KPIs. The primary unit of work is a shift.
RBAC at the aircraft level
Six roles. Grants are (user, aircraft_id) tuples — an operator can have authority over aircraft A and B but not C.
Physics-based simulator
10 aircraft across three vendor classes at 5 Hz, with flight dynamics, battery decay, and link-quality wandering. Uses the same adapter interface as real hardware.
Fleet dashboard: 10 simulated aircraft (fixed-wing, multicopter, VTOL) on one screen, live alerts and weather inline.
Interested in BVLOS dispatch tooling?
Questions about the architecture, the adapter SDK, or ops-tooling problems in general — reach out directly.