DJI FlightHub
DJIdji-flighthubSync FlightHub 2 organisations, fleet, docks, tasks, routes and livestreams into records you own. Pull is proven against a live organisation; push is off until you enable it.
Including the ones that are not ready. Especially those. Thirteen adapters ship in the catalog; five you can connect today, two are shipped but unproven against a live vendor, and six are on the roadmap with nothing to connect yet. All thirteen are on this page.
Status is read from each adapter's own manifest, not from a marketing sheet. Available means configurable today. Beta and Preview mean the code path ships but has not been round-tripped against a live vendor. Planned means there is nothing to connect — and we would rather print that than a logo.
Showing 13 of 13 adapters — 5 available · 2 in preview or beta · 6 planned.
Sync FlightHub 2 organisations, fleet, docks, tasks, routes and livestreams into records you own. Pull is proven against a live organisation; push is off until you enable it.
Ingest normalised MAVLink telemetry and vehicle state from bridged autopilots, buffered across intermittent links.
Import missions, parameters and telemetry from PX4 and ArduPilot open autopilots — the vendor-neutral path into the fleet.
Pluggable weather source with Open-Meteo built in: observations, forecasts and airspace advisories. Set it to none for air-gapped sites and nothing is polled.
Fan platform events out to any HTTPS endpoint with an HMAC-signed payload — and the intake path for CAD and alarm systems.
A worker joins video rooms, runs local detection inside your boundary and emits detection events onto the platform mesh. No frame leaves the premises.
Vendor-neutral drone-in-a-box provider: dock assets, battery state, maintenance, health and dispatch.
Generic Remote ID feed provider: normalised observations, source health and replay.
On the roadmap — nothing to connect yet. It gets a place on this page precisely because it is not ready.
XProtect VMS bridge for camera inventory, recordings and analytic events.
On the roadmap — nothing to connect yet. It gets a place on this page precisely because it is not ready.
Generic surveillance provider: cooperative and non-cooperative ADS-B and radar tracks.
On the roadmap — nothing to connect yet. It gets a place on this page precisely because it is not ready.
Cumulocity IoT bridge for managed objects, measurements and alarms.
On the roadmap — nothing to connect yet. It gets a place on this page precisely because it is not ready.
ThingWorx industrial IoT bridge for things, properties and events.
On the roadmap — nothing to connect yet. It gets a place on this page precisely because it is not ready.
Insights Hub (MindSphere) bridge for assets, time-series and events.
On the roadmap — nothing to connect yet. It gets a place on this page precisely because it is not ready.
The catalog holds exactly thirteen adapters and this page will not pad the grid with near-misses. Widen the search, clear a filter — or tell us what is missing.
The platform is vendor-neutral: it speaks MAVLink, and PX4 and ArduPilot autopilots, natively, and reaches DJI hardware through FlightHub 2. What it does not do is print a per-airframe compatibility grid claiming assurance for models nobody here has flown against. That restraint is the point of this page.
Protocols and ecosystems, not model numbers. If your airframe speaks one of these, it talks to FlightStudio — the airframe badge on the shell is not the interesting part.
Exercised end to end against a live DJI organisation — connection, device inventory, completed flight tasks and telemetry tracks landing in a FlightStudio database.
Two entries, and they are dated. Every other airframe reachable over MAVLink, PX4 or ArduPilot will very probably work — we simply have not run it, so it does not get a tick here. Ask us and we will test yours during the evaluation rather than guess in public.
The systems around an operations centre are site-specific by nature: a TETRA fleetmap, a VMS estate, a CAD schema. We integrate them through a scoped operations-centre engagement rather than pretending a catalog tile can absorb them. Where a platform adapter genuinely does exist, it is named below with its own badge.
Delivered as part of a unified operations-centre build: interface design, a conformance test against your live system, and an evidence trail for the integration itself. Not shipped as a self-serve connector, because it cannot honestly be one.
TETRA and DMR talkgroups bridged to operations events, so a dispatch reaches the crew on the network they already carry.
Engagement · no shipped adapterFixed-camera estates alongside the airborne video wall, so an operator sees one scene rather than two systems.
Platform adapter: Milestone XProtect PlannedIncident intake from a computer-aided dispatch or emergency system becomes a launch proposal with airspace and risk pre-checked.
Platform adapter: Generic Webhook AvailableCommon-operating-picture and incident-command platforms fed from the same event mesh the flight record is written to.
Engagement · no shipped adapterA unified operations centre is scoped, built and handed over — the adapters above are what the platform brings to it, not the whole of it.
Unified operations centre Scope an engagementTell us the system, the protocol and the release you are on. If it belongs in the catalog we will say which wave it lands in — and if it does not, we will say that instead.
sales@teknosur.com · we answer with a wave number, not a maybe.