Products
DJI FlightHub 2 comparison guide: Public Cloud vs On-Premises vs AIO
Compare DJI FlightHub 2 Public Cloud, On-Prem, and AIO. Discover setup, data security, and customisation differences to find the best fit for your drone ops.
In this article, you'll learn:
The core differences between FlightHub 2 Public Cloud, On-Premises, and AIO.
Which version offers the best data-sovereignty control.
How each model handles security, integration, and scalability.
Deployment options for mobile and enterprise environments.
How heliguy™ - an accredited FlightHub 2 On-Premises provider - supports installation, training, and long-term management across the FlightHub 2 ecosystem.
DJI FlightHub 2 Public Cloud vs On-Premises vs AIO: Which version is right for your organisation?
Quick summary
DJI FlightHub 2 connects drones, pilots, and mission data in one secure platform. It comes in three forms:
Public Cloud: Fast start-up and fully hosted by DJI. Ideal for teams who want quick deployment and collaboration without managing complex IT infrastructure or needing to adhere to strict data mandates.
On-Premises: Maximum control and customisation for organisations needing full data ownership, local hosting, and deep IT integration.
AIO (All-in-One): Secure, portable, and ready-to-deploy server. Combines On-Prem security with plug-and-play simplicity for rapid, field-ready operations. The perfect bridge between Public Cloud and On-Premises.
As of 2025, FlightHub 2 has powered over 2 million missions and logged more than 400,000 operational hours across 85 countries.
Choose your version based on data sovereignty, IT infrastructure, and operational mobility.
heliguy™ is a FlightHub 2 provider and has DJI-accredited technicians to deliver the On-Premises version.
What is DJI FlightHub 2?
DJI FlightHub 2 is an enterprise-grade management platform for mission planning, fleet monitoring, and data analysis.
It centralises livestreaming, mapping, annotation, and collaboration — allowing multiple teams to manage DJI Enterprise drones and DJI Dock operations through a unified interface.
Core capabilities:
Multi-drone livestreaming with role-based access.
Real-time maps and collaborative annotations.
Real-time remote operations.
Comprehensive flight planning.
End-to-end data analysis.
Mission planning and DJI Dock management.
Intelligent algorithms and a Multimodal Large Language Model (LLM).
Centralised device and user administration.
Integration and extensibility via API and SDK for custom workflows.
Localised cloud-modelling module, built on DJI Terra’s core modelling engine (doesn’t support LiDAR point clouds, multispectral reconstruction, contour lines, DEM, cluster reconstruction).
DJI FlightHub 2 On‑Premises and FlightHub 2 AIO aim to match and provide an identical user experience to the Public Cloud - although there are some small variations, which we’ll explore later.
But the key differences between the Public Cloud version and the On-Premises/AIO solutions are where they run, how they’re maintained, how they integrate, and how data is controlled.
How does data security differ between DJI FlightHub 2 versions?
Data sovereignty is one of the crucial differences between the DJI FlightHub 2 solutions - and can be a key driver in deciding which is best for you.
DJI FlightHub 2 Public Cloud data security
Data stored in DJI’s cloud infrastructure: ie Amazon Web Services servers in Europe and the U.S.
Data is encrypted in transit and at rest.
Certified for ISO/IEC 27001 security compliance and ISO 27701 privacy compliance. This ensures users’ data privacy and personal information is properly managed and protected.
Offers robust data security: Perfectly suited to teams who do not have strict sovereignty mandates.
DJI FlightHub 2 On-Premises
Install in a completely isolated environment, providing an additional layer of data security and offering secure local deployments.
Data never leaves your network; total control over storage, access, and encryption.
Integrates with enterprise-grade security: SSO, SIEM, PKI, and air-gapped modes.
Designed for users who require private intranet deployment and complete control over their data.
DJI FlightHub 2 AIO
Shares On-Prem’s control model with additional hardware-level security features, including storage isolation with RAID 1 mirroring, one-click system recovery capabilities, and expandable storage support.
Secure by default, with predictable patching and lifecycle management.
Ensures data reliability while enabling flexible capacity scaling based on operational requirements.
How do the deployment options differ between DJI FlightHub 2 options?
The different DJI FlightHub 2 solutions provide varying deployment environments.
DJI FlightHub 2 Public Cloud
DJI-hosted SaaS (software as a service) with elastic scaling and global access.
You access it as a service — no need to install or manage your own physical servers or private cloud.
Ideal when you need to onboard quickly, collaborate with external partners, or run multi-site programmes without building infrastructure.
DJI FlightHub 2 On-Premises
You deploy FlightHub 2 into your infrastructure (physical servers, private cloud, or public cloud), catering for the needs of users with varying network requirements.
You own the network pathing, storage classes, backup strategy, certificates, logging, and patch cadence.
Enables air-gapped or bandwidth-constrained environments and strict east-west controls.
On-Premises supports up to 200 devices (more than AIO).
Deploy DJI FlightHub 2 On-Premises in the following ways:
Server type | Benefit |
|---|---|
Physical server | Deploy on traditional physical or bare-metal servers to maximise computing resources, streamline maintenance, and simplify system architecture. |
Private cloud | Deploy on-premises or in hybrid cloud environments for efficient resource orchestration, easy operation, and enterprise-grade reliability. |
Public cloud | Use as a SaaS solution, eliminating the need for an on-premises server rooms or server maintenance. |
DJI FlightHub 2 AIO (All-in-One)
A vendor-supplied appliance: Pre-installed FlightHub 2 On-Prem + tuned hardware.
Reduced integration friction: Sensible defaults, hardened image, streamlined updates.
Deployable in fixed sites or mobile command units; good for rapidly establishing secure local operations.
Removes the need for complex IT infrastructure, while retaining the security of FlightHub 2 On-Premises.
Each AIO supports up to 20 devices (including DJI Enterprise drones and DJI Docks) simultaneously.
Deploy DJI FlightHub 2 AIO in the following ways:
Deployment type | Benefit |
|---|---|
In-vehicle deployment | Paired with DJI Dock 3 or drone platforms, AIO provides a complete mobile deployment solution. It can operate without network connectivity, making it ideal for scenarios like emergency response. |
Server room deployment | Equipped with multiple network interfaces, the AIO device supports stable 24/7 operation and seamless integration into existing server room networks. |
Office deployment | The AIO device is compact and lightweight at only 3.008 kg, with low power consumption. Low-noise operation makes it suitable for office environments. |
Can you customise DJI FlightHub 2 for your workflows?
FlightHub 2 isn’t just about deployment options — it’s about how each environment can adapt to your workflows and systems.
Each edition offers its own level of flexibility and custom development potential, from simple API connections to full enterprise integration and bespoke automation.
DJI FlightHub 2 Public Cloud
Offers limited API access, webhooks, and standard integration points.
Limited customisation beyond approved integrations.
DJI FlightHub 2 On-Premises
Abundant APIs for deep custom development for bespoke tools, dashboards, and automation.
Supports internal extensions like telemetry ingestion, AI/ML pipelines, and data routing.
Build a tailored drone management system, designed for your needs, and integrate with existing software infrastructure.
DJI FlightHub 2 AIO
Mirrors On-Prem extensibility within a contained environment.
Suitable for localised automation without full infrastructure overhead.
Custom development capabilities: Deep dive
The table below highlights the custom development features of FlightHub 2.
Standard, Pro, and Enterprise are mentioned - these are packages of the Public Cloud version. We’ll come to this later.
Standard | Pro | Enterprise | On-Premises | AIO | |
|---|---|---|---|---|---|
Front-end Components | No | No | No | Yes | Yes |
OpenAPI | No | Yes (limited support) | Yes (limited support) | Yes | Yes |
FlightHub Sync | No | Yes | Yes | Yes | Yes |
Algorithms and large models | No | Yes, except for large models | Yes, except for large models | Yes | Yes |
Single sign-on | No | No | Yes | Yes | Yes |
MQTT Bridge | No | No | No | Yes | Yes |
What are DJI FlightHub 2 frontend components? DJI FlightHub 2 frontend components include flight route creation, flight route editor, virtual cockpit, and project/map. These components support custom themes and styles.
What is OpenAPI on DJI FlightHub 2? DJI FlightHub 2 OpenAPI is an open platform based on RESTful specifications, designed to provide developers with the ability to interact with third-party cloud platforms and DJI FlightHub 2.
What is DJI FlightHub 2 Single Sign-on?
Single Sign-On (SSO): OAuth 2.0 support enables unified authentication, allowing users to seamlessly switch between platforms with a single login.
What is MQTT Bridge and what does it bring to DJI FlightHub 2?
The MQTT Bridge provides MQTT bridging and forwarding functionality, supporting the forwarding of dock's MQTT information to third-party systems through FlightHub 2 On-Premises version, offering a collaborative task solution for third-party systems and FlightHub 2 on-premises version in industry scenarios.
What is DJI FlightHub Sync?
DJI FlightHub Sync enables integration between public or On-Premises versions of FlightHub and third-party cloud platforms, allowing synchronisation of files, livestreams, device telemetry, and other data.
The main features of DJI FlightHub Sync are as follows:
Feature | FlightHub 2 Public Cloud (Pro and Enterprise only) | FlightHub 2 On-Premises/AIO |
|---|---|---|
Livestream forwarding | Supported | Supported |
File synchronisation | Supported | Supported |
Device information synchronisation | Via telemetry data | Via MQTT Bridge |
Third-party OAuth | Not supported | Supported |
Integration settings | Coming soon | Coming soon |
What are the current feature differences between DJI FlightHub 2 Public Cloud and DJI FlightHub 2 On-Premises?
DJI FlightHub 2 Public Cloud benefits from automatic updates from DJI - and the On-Premises version and AIO are continuously updated alongside this.
This helps to keep the main features aligned with the latest public cloud version.
But there are some differences, as outlined in the table below.
Function | Public Cloud | On-Premises (including AIO) |
|---|---|---|
Interface customisation | No | Yes |
Third-party account login | Yes (via Enterprise SSO) | Yes (via OAuth) |
Map data | Yes (Included by default) | Yes (Requires custom import) |
Elevation data | Yes (Included by default) | Yes (Requires custom import) |
Automatic post-flight mapping | No | Yes |
Smart change detection | Yes | No |
Live weather and ionosphere data display | Yes | No |
One-click Dock diagnostics | Yes | No |
SMS alerts for critical faults | Yes | No |
eSIM data usage warnings | Yes | No |
One-Click damage assessment | Yes | No |
GEO Zones unlocking | Yes | No |
Real-time Speaker Broadcasting | Yes | No |
LLMs
DJI FlightHub 2 can support Multimodal Large Language Models (LLMs) for object detection and media search - but it isn't one size fits all.
Public Cloud: Integrates LLMs.
On-Premises: Must be procured and deployed by the user, while access to online Multimodal LLMs requires user-side integration.
AIO: Does not include a built-in multimodal LLM, but locally deployed multimodal LLMs can be integrated to enable related functions.
4G Enhanced Transmission
DJI FlightHub 2 supports 4G Enhanced Transmission in both Public and On-Premises versions, improving drone transmission quality in weak SDR signal conditions.
Public Cloud | On-Premises (including AIO) | |
|---|---|---|
4G dongle requirement | Yes | Yes |
SIM card type | Regular SIM | Dedicated APN card from local operator |
Usage method | Plug and play | Deploy localised 4G enhanced transmission services |
Charging model | Only SIM card data required. No extra charge for enterprise drones. | Included in the FH2 On-prem licence. Can also be purchased separately |
Use thresholds | Low | High, professional services required |
Maximum access device | Unlimited | Limit depends on the purchase package |
Dock and remote control availability | Yes | Yes |
Which drones are compatible with DJI FlightHub 2?
DJI FlightHub 2 Public Cloud, DJI FlightHub 2 On-Premises, and DJI FlightHub 2 AIO are all compatible with the following products in the DJI Enterprise ecosystem.
DJI Docks: DJI Dock 3, DJI Dock 2, and DJI Dock.
Drone platforms: DJI Matrice 400, DJI Matrice 350 RTK, DJI Matrice 30 Series, DJI Matrice 4 and Matrice 4D Series, DJI Mavic 3 Enterprise Series (excluding DJI Mavic 3 Multispectral).
Payloads: Zenmuse H30 and Zenmuse H30T, the Zenmuse H20 and Zenmuse H20T, the Zenmuse S1, and the Zenmuse V1.
DJI FlightHub 2 package comparison
DJI FlightHub 2 comes with multiple packages, including the Public Cloud that offers Standard (Free), Pro, and Enterprise options, as well as recharge and space upgrade packages, tailored to different user needs.
The On-Premises versions offer deep customisation, and options to bolt-on additional devices.
Package | Offering |
|---|---|
Standard (Free) | Free to use, with limitations on features and resources. Ideal for evaluating core capabilities. |
Professional | Unlocks most features with no limit on online device numbers. Resource quotas apply, requiring the purchase of a recharge/upgrade package if depleted. |
Enterprise | Includes all features with unlimited use of most resources. It offers a very large quota for mapping images and restricts the number of devices that can be online simultaneously. |
On-prem | Deep customisation. Livestream minutes, storage space, and mapping images are all unlimited. The number of simultaneous online devices is limited, but can be expanded up to 200. |
AIO | Deep customisation. Livestream minutes and mapping images unlimited. Data storage location can be customised (ie local storage only). Hardware storage is 3 × 2TB SSDs: 1 for system, 2 for data (RAID 1 data mirroring). Each AIO can connect and support up to 20 devices. |
When resource quotas run out in Standard or Professional versions, recharge/upgrade packages can supplement resources.
These bolt-on packages are:
Livestream Recharge Package
Mapping Recharge Package
Storage Space Upgrade Package
Meanwhile, On-Premises and AIO offer their own packages. These are:
On-Premises:
Basic Package (1 Device): Up to 1 device online.
Device Expansion Package (+ 1 Device): Adds 1 additional device online.
Device Expansion Package (+ 5 Devices): Adds 5 additional devices online.
Upgrade Validity Extension Package (1 Year 1 Device): Extends software upgrade validity; Basic package includes 1 year free upgrades.
DJI FlightHub 2 AIO
DJI FlightHub 2 AIO (1 Device): Up to 1 device online.
Device Expansion Package (+ 1 Device): Adds 1 additional device online, up to 20 devices.
Device Expansion Package (+ 5 Devices): Adds 5 additional devices online, up to 20 devices.
heliguy™ DJI FlightHub 2 support
heliguy™ can help you start and scale with FlightHub 2, including FlightHub 2 On-Premises.
Our Assistant Operations Manager, Kevin Morton, is a DJI-certified FlightHub 2 On-Premises Delivery Engineer, having completed his training with the DJI Delivery Engineer team. heliguy™ also has accredited DJI Dock 3 technicians.
We offer guidance from the initial consultation to getting your server up and running, and provide on-going technical support.
Contact our specialists today.
DJI FlightHub 2 summary and decision guide
With Public Cloud and On-Premises solutions, DJI FlightHub 2 offers sector-wide versatility for drone programmes.
In summary:
Choose Public Cloud if you: Need to start quickly, share access broadly, and don’t have strict sovereignty mandates.
Choose On‑Premises if you: Must keep data inside your network/country, integrate with enterprise tooling, or operate offline/air‑gapped. Achieves fully-localised management, operation, and maintenance, ensuring the security of your business. It handles more devices than AIO, can use more powerful hardware, and is designed for scalability.
Choose AIO if you: Want On‑Prem security and control but prefer a plug‑and‑play deployment (fixed site or mobile unit). It is ready out of the box, greatly reducing the hardware and software installation and deployment costs.
Expert insight: Heliguy’s FlightHub 2 Specialist, Kevin Morton, explains how to choose between the three deployment models.
"Choosing the right FlightHub 2 deployment really depends on how your organisation operates. Public Cloud is fantastic for teams that prioritise rapid rollout and seamless collaboration. On-Premises gives total control for those with strict data and security requirements, while AIO strikes a perfect balance — offering on-prem peace of mind without the heavy IT lift. It’s about aligning your workflow, compliance needs, and long-term scalability with the right architecture.
At heliguy™, we help clients match these options to their mission profiles — from initial consultation and deployment through to training, support, long-term fleet integration, and server support.
And heliguy™ can support you from start to finish. Contact us.
