Every dock flight in FlightHub 2 leaves a trail: live video, photos, flight logs, maps of your site. On the cloud version, that data sits on AWS in Virginia or Frankfurt, according to DJI's FlightHub 2 FAQ. DJI lists no Australian region. For a utility, a mine, a council or a security contractor, that is often where the conversation stops.
FlightHub 2 On-Premises is DJI's answer: the same platform installed on a server you choose. That can be hardware in your comms room, DJI's own appliance, or an instance in AWS Sydney. We set it up as a service.
Three places to run it
| Option | What it is | Suits |
|---|---|---|
| FlightHub 2 AIO | DJI's desktop appliance with the software preinstalled: Intel Core Ultra 7, 64 GB RAM, an NVIDIA RTX 2000 Ada and three 2 TB SSDs. DJI rates each AIO for up to 20 devices | A single site that wants a ready built unit. Quoted through dealers, including us |
| Your own server | Ubuntu 22.04 or 24.04 on x86. For version 2.0, DJI asks for 16 cores, 64 GB RAM and a 1 TB SSD for about 20 docks, and about double that for 50 | Organisations with a data centre and an IT team to run it |
| Public cloud | DJI publishes a public cloud deployment guide for AWS and Azure | Fleets across several sites, or no server room |
All three run the same software; the choice is who looks after the hardware. On DJI's FlightHub 2 comparison, the On-Premises version (AIO included) has no livestream minute, storage or mapping image quotas, unlike the cloud plans, and scales to 200 devices per deployment.
Why AWS Sydney
AWS's Sydney region keeps the data in Australia with no hardware to buy, cool and replace. DJI asks for a static IP and at least 100 Mbps symmetric for internet facing installs, and its cloud guide budgets about 5 Mbps per concurrent live stream.
DJI's cloud guide starts at a c5.4xlarge (16 vCPU, 32 GB), or a g5.8xlarge with a GPU for Terra reconstruction, and adds memory past 10 docks. DJI's version 2.0 server spec asks for 64 GB for about 20 docks, so we size from that: the same 16 vCPU with more memory. Storage is provisioned IOPS, with a system disk of at least 500 GB and a data disk from 2 TB, grown with your flight media. Cost comes from the instance (more with a GPU for Terra), that storage, and data out for live video.
Licences
On-Premises is licensed per device. DJI sells a Basic Package covering one device with a year of upgrades, expansion packs of one or five more devices, and upgrade extensions. Terra reconstruction and 4G transmission are licensed separately, and in version 2.0 they must sit on the same server as FlightHub 2. DJI does not publish prices, so we quote them with the deployment.
The licence is bound to one server through a fingerprint file, and moving it needs DJI's approval. Changing the instance later can mean re-licensing through DJI, so we size it with headroom up front.
What DJI still touches
On-Premises keeps your flight data on your server. It is not a disconnected product, and you should know where it reaches out:
- Licence and activation. The licence is generated on DJI's developer site, and activation uses a phone browser that reaches DJI's activation service while scanning a code from the server.
- Setup and time. Installation, container images, elevation data and time sync need outbound internet access.
- Maps. On-Premises uses offline map tiles. The package ships with a sample map of Shenzhen, so you need Australian base maps you are licensed to use before your pilots see anything useful.
DJI lists ISO 27001 for FlightHub 2's design, development and operational services. A server you run sits under your controls, not DJI's, so your security team assesses it. We hold no certification for it.
What works on it
Version 2.0 (14 October) adds Dock 4 with the Matrice 5TD, over HTTPS only. Dock 3, Dock 2, the original Dock, the Matrice 4E and 4T, Matrice 400, M350 RTK and Mavic 3 Enterprise remain supported. Earlier On-Premises versions cannot be upgraded to 2.0 with DJI's visual tools. An OpenAPI and MQTT bridge are there for linking into your own systems. Copilot is not supported yet, and AI features such as Change Detection Pro need a vision language model you host yourself, which means a GPU instance. If you are choosing between docks, our Dock 4 and Dock 3 comparison covers the hardware.
A private server changes where data sits. It does not change your CASA approvals for dock or BVLOS flights.
Two ways we run it
We host and manage it. Your FlightHub 2 runs in AWS Sydney on infrastructure we look after: patching, monitoring, backups and upgrades are ours, so your team just flies.
We deploy it in your account and hand over. We build it in your own AWS Sydney account, train your staff, and hand over admin access and a runbook.
Either way, the build is the same:
- Size the instance and storage for your dock count and media retention
- Supply the On-Premises licences and expansion packs
- Lock security groups to the ports DJI lists, and set up the domain, the TLS certificate and its renewal
- Schedule EBS snapshots for backups (DJI's built in backup is not available for its cluster edition, which needs three or more nodes for high availability)
- Load your base maps, activate the licence, bind docks and aircraft, and check live streams end to end
If you already run FlightHub 2 in the cloud and the data question has come up, that is the conversation to have before the next dock goes in.