DJI FlightHub 2 On-Premises 1.7 Triples Livestream Capacity

DJI has released FlightHub 2 On-Premises v1.7, and it is a substantial update for organisations running self hosted drone fleet management. The three headline changes are up to a 3x increase in concurrent livestream capacity, an expansion from 67 OpenAPI interfaces to more than 300 endpoints, and incremental upgrade packages that cut a deployment from a full reinstall to roughly 20 minutes.

For anyone running multiple DJI Docks on their own infrastructure, this is the release that removes several of the practical reasons not to.

What On-Premises Actually Means

FlightHub 2 comes in two forms. The cloud version runs on DJI's infrastructure. The On-Premises version runs on your own servers or an approved private cloud, and everything the fleet generates stays inside your network.

That includes flight logs, live video feeds, maps, 3D models and inspection data. For a police force, a water utility, a transport authority or a defence adjacent contractor, data sovereignty is frequently not a preference but a condition of being allowed to operate the system at all. On-Premises exists to satisfy that condition.

The self hosted version also gets capabilities the cloud version does not. MQTT Bridge support for integrating with existing industrial systems, offline map functionality for sites without connectivity, custom integration support and considerably broader API access.

The trade runs the other way too. Live weather information, SMS notifications, DJI Care Enterprise integration and AI powered cloud services remain cloud only, so an organisation choosing On-Premises is accepting the loss of those in exchange for control.

Three Times The Livestream Capacity

The most operationally significant change in v1.7 is multi-core livestream processing, which raises concurrent livestream capacity by up to three times.

Livestream capacity is the bottleneck that bites organisations as they scale. One dock streaming to one operator is straightforward. Six docks streaming simultaneously to a control room with several operators each watching a different feed is where systems start dropping frames, showing black screens or falling behind. DJI has also fixed livestream failures, relay and forwarding problems, black screen issues and inaccurate latency reporting in this release, which suggests the previous version was under real strain at scale.

If your deployment plan involves adding docks over the next two years, this is the change that determines whether the platform grows with you.

From 67 API Endpoints To Over 300

The API expansion is the change with the longest tail. Version 1.6 exposed 67 OpenAPI interfaces. Version 1.7 exposes more than 300, with systematic coverage across device management, flight missions, flight records, media management, map data and model data.

This is what turns FlightHub 2 On-Premises from a system you operate into a system you build on. With coverage that broad, an organisation can push flight records straight into its own asset management platform, trigger missions from an existing work order system, pull media into a document management system automatically, or feed inspection outputs into a GIS without anyone exporting a file by hand.

For utilities and infrastructure owners with mature enterprise software estates, that integration capability is often worth more than any individual feature in the interface.

Upgrades That No Longer Take A Day

Previous versions required a full reinstall to move between releases. Version 1.7 introduces incremental upgrade packages, bringing the average upgrade down to around 20 minutes.

There is a catch worth planning around. Incremental upgrades only work between adjacent versions, so v1.6.x to v1.7.x is incremental, but jumping across multiple versions still requires a full installation. Organisations that have been sitting on an older release will need to budget for the long route once, then stay current to benefit.

DJI has also added automatic network segment conflict detection, improved how configuration changes are handled in the admin console, standardised version numbering across systems and improved recovery times after configuration updates. Documentation has moved to a searchable online format with PDF export.

One planning note. Installation packages for v1.5 and older have been removed, with legacy access now available only through DJI support or authorised partners.

Situational Awareness And Integration

Beyond the headline items, v1.7 supports O4 Ground Station for signal enhancement, viewing of ONVIF and GB/T 28181 network camera feeds, and integration of Remote ID and ADS-B receivers.

The last of those matters for UK operators in particular. Bringing ADS-B and Remote ID data into the same interface as your own fleet gives a control room a single picture of what is in the airspace, which is increasingly how safety cases for BVLOS and dock based operations are constructed. Fixed network camera feeds in the same view means the drone becomes one sensor among several rather than a separate system with its own screen.

Who Should Be Looking At This

DJI is aiming v1.7 at government agencies, public safety departments, utilities, transport authorities, energy companies and any organisation with strict cybersecurity, compliance or data sovereignty requirements.

In the UK that maps onto a recognisable set of operators. Police forces and fire services running DFR programmes. Water and energy companies inspecting distributed assets. National Highways and rail infrastructure owners. Ports and airports. Organisations, in short, where the IT security team has a veto and the answer to where does the data go decides the procurement.

FAQs

What is the difference between FlightHub 2 cloud and On-Premises?

On-Premises runs on your own servers or an approved private cloud, so flight logs, video, maps and inspection data never leave your network. It also adds MQTT Bridge support, offline maps, custom integration and broader API access. Live weather, SMS notifications, DJI Care Enterprise integration and AI cloud services are available only in the cloud version.

What is new in FlightHub 2 On-Premises v1.7?

The main changes are up to 3x concurrent livestream capacity through multi-core processing, an expansion from 67 to over 300 API endpoints, incremental upgrade packages that take around 20 minutes, automatic network segment conflict detection and various livestream reliability fixes.

How long does a FlightHub 2 On-Premises upgrade take?

Around 20 minutes on average using an incremental package. Incremental upgrades only work between adjacent versions, so moving from v1.6.x to v1.7.x is quick, but skipping multiple versions still needs a full installation.

Does FlightHub 2 On-Premises support ADS-B and Remote ID?

Yes. Version 1.7 supports integration of Remote ID and ADS-B receivers, along with ONVIF and GB/T 28181 network camera feeds, so fleet and airspace awareness can sit in one interface.

Can FlightHub 2 On-Premises work offline?

It includes offline map functionality, which allows operations at sites without reliable connectivity. The platform itself runs on your own infrastructure, so it does not depend on a connection to DJI's cloud.

Final Thoughts

Version 1.7 reads like a release built from customer complaints rather than a marketing roadmap, which is usually a good sign. Livestream capacity, upgrade friction and API coverage were the three things standing between a working pilot deployment and a fleet wide rollout, and all three have been addressed in the same release. For organisations that cannot put drone data in someone else's cloud, self hosted FlightHub 2 is now a considerably more credible foundation than it was.

Planning a dock based or self hosted drone programme? Speak to the Coptrz enterprise team about DJI Dock, FlightHub 2 and the deployment behind it at sales@coptrz.com or call 0330 111 7177.