A customer-ready deployment deck for running FlightHub 2 on a local Linux server, with clear server, network, activation, firewall, and acceptance requirements.
FlightHub 2 On-Premises is positioned for organizations that need private deployment, controlled access, local infrastructure governance, and clearer data-residency handling. The project should be planned as a complete IT deployment, not a simple software installation.
Run the platform on customer-controlled Linux infrastructure.
Limit operators, devices, and services by corporate network policy.
Plan backups, updates, accounts, and maintenance windows before go-live.
Keep a clean record of license, ports, accounts, validation results, and support ownership.
In the standard topology, the deployed private server, terminal devices, and docks are connected through the customer network device. DNS and NTP services may be included within the private server or deployed separately according to customer IT policy.
| Node | Role |
|---|---|
| Private server | Runs the FlightHub 2 On-Premises service stack and related local services. |
| Network router | Provides routing between server, operator terminals, and dock network access. |
| Terminal device | Operator workstation accessing the web portal through browser. |
| DJI Dock + aircraft | Field operation endpoints connected through wired dock access and configured device network paths. |
The configuration below provides a practical deployment baseline and should be increased according to fleet scale, livestream concurrency, optional services, and media retention policy.
| Item | Recommended baseline | Deployment notes |
|---|---|---|
| CPU | 8 cores | Increase for larger fleets or optional service modules. |
| Memory | 32 GB RAM | Use higher memory for larger deployments. |
| Data disk | 1000 GB SSD | SSD is required. Separate OS and data disks where possible. |
| Network | At least 100 Mbps stable LAN/WAN bandwidth | Each dock requires roughly 5 Mbps for two concurrent livestreams. |
| OS | Ubuntu Server 22.04 LTS | Prepare a clean supported Linux server image. |
| Browser | Google Chrome 120 or later | Recommended for FlightHub 2 On-Premises web interface. |
An activation code is required before FlightHub 2 On-Premises can be deployed and used. It can come from an approved trial or from a purchased service entitlement.
Confirm hardware, Ubuntu version, disk layout, static IP, DNS, certificate, firewall, and access policy.
Check activation code, license scope, optional modules, firmware compatibility, and package version.
Generate server fingerprint file on the target server when required.
Create license and download installation package from official DJI channels.
Upload, extract, run checks, configure service parameters, and start deployment.
Set up organization, maps, elevation data, activation, and device binding.
Test login, telemetry, livestream, media upload, map display, and permissions.
Device-facing ports should be limited to known dock, remote-controller, LAN, VPN, or private APN ranges. Administrative services should not be exposed to the public internet.
Required for web access, MQTT onboarding, livestream, media upload, map services, and device communication paths.
Restrict deployment tool, dashboards, console, monitoring, metrics, message queue, and internal services to approved admin networks.
Deployment support can be provided during implementation, while the customer IT team remains responsible for corporate firewall, VPN, endpoint, SIEM, backup, certificate, vulnerability-management, and final compliance approval.
Keep O&M consoles, monitoring, and internal services restricted.
Confirm public CA, customer CA, or approved self-signed certificate before go-live.
Define backup path, retention period, and failure escalation before acceptance.
Do not hardcode credentials in shared documents; rotate temporary passwords.
| Category | Checklist item |
|---|---|
| Commercial | Activation code, service term, capacity, optional modules, and handover owner confirmed. |
| Server | Ubuntu 22.04 LTS, SSD data disk, CPU/RAM/storage sizing, static IP, and admin access ready. |
| Network | Ports opened, source ranges restricted, routing conflicts checked, VPN/private APN path confirmed where applicable. |
| Security | Certificate, firewall ownership, account policy, backup policy, and log retention confirmed. |
| Devices | Dock, aircraft, and remote-controller firmware compatibility confirmed against official list. |
| Validation | Login, device binding, telemetry, mission operation, livestream, media upload, and permissions tested. |
| Handover | Admin accounts, license records, backup path, update policy, and support route documented. |
“A successful FlightHub 2 On-Premises project is not only software installed on a server. It is a complete operational environment: licensed, reachable, secure, tested, and handed over with clear ownership.”
Server, package, license, domain/IP, certificates, and port rules.
Login, binding, telemetry, livestream, media upload, map display, and permissions.
Operational owner, maintenance window, escalation path, and update policy.
Use the links below to access the complete FlightHub 2 On-Premises deployment manual and the detailed Quick Start Guide. Final deployment settings should be confirmed against the actual license scope, supported firmware list, customer cybersecurity policy, and site network design.
Additional product reference: DJI Enterprise FlightHub 2 On-Premises official product page.