Skip to content
UAVSUPER

Product updates / Remote Operations

FlightHub 2 On-Premises v1.7: an upgrade decision for IT

The August 2026 release concerns private deployment, streaming and APIs. Plan the migration around the installed environment.

At a glance
  • Dated release: On-Premises v1.7, August 2026.
  • Choose the upgrade path from the installed version.
  • Test streams, integrations and operations.

What DJI announced

DJI’s August 18, 2026 v1.7 announcement describes improved multi-core streaming and an expanded OpenAPI with more than 300 endpoints. It distinguishes the adjacent v1.6-to-v1.7 incremental upgrade from upgrades spanning multiple versions.

Treat these as dated manufacturer release details. Performance depends on the deployed resources, and a larger API catalog does not itself establish that a particular integration exists.

Reference: DJI · DJI: FlightHub 2 On-Premises V1.7 (opens in a new tab) · DJI · DJI: On-Premises OpenAPI V2.0 (opens in a new tab)
A private deployment change has three owners.
  1. 01ITEnvironment + migration
  2. 02IntegrationAPI behavior + connected tools
  3. 03OperationsStreams + mission continuity
Workflow overview

Inventory the installed environment

Record the current version, server resources, connected devices, integrations and the operational workflows that must continue. Identify who owns the change and who will accept the restored service.

Check current manufacturer upgrade instructions against that inventory. Do not choose an incremental path simply because it sounds faster. Backups and recovery steps belong to the actual deployment method.

Test operations as well as installation

TestEvidence to retain
Access and rolesExpected users can access only their required functions.
Live streamsRepresentative concurrency works on the allocated resources.
Mission and recordsExisting workflow and data access remain usable.
IntegrationsRequired API behavior is verified with the connected application.
RecoveryOwner and documented recovery procedure are known.

Define the commercial scope

Private deployment, cloud access, integration development and hardware are separate decisions. Ask which edition and functions the organization actually needs before estimating an implementation.

Use the release as an input to an IT review, not as a reason to change a working environment without a migration plan. Record the tested version and the accepted integration behavior so a later release has a clear baseline.

Sources

  1. DJI: FlightHub 2 On-Premises V1.7 (opens in a new tab)DJI · Published
  2. DJI: On-Premises OpenAPI V2.0 (opens in a new tab)DJI
Apply this readingAutonomous Remote Operations

Related reading

All resources