The functionality is nearly identical — the same mission planning, Virtual Cockpit, mapping, fleet management and DJI Dock integration. The core difference is where the data lives. With the cloud version, data is stored on DJI's AWS infrastructure in Europe. With On-Premises, everything stays within your own network. The On-Premises version also adds the MQTT Bridge, which isn't available on the cloud platform. For most organisations without strict data mandates, the cloud version is simpler and faster to deploy. For organisations with sovereignty, compliance or offline requirements, On-Premises is the correct choice.

The AIO is a pre-installed hardware device that brings On-Premises security and local data control to organisations that don't have the server infrastructure or IT capacity to deploy the software-only version. It arrives ready to use — connect it to your network, and you have a fully functional, locally hosted FlightHub 2 platform, including a GPU-accelerated 3D modeling engine that generates 3D models from drone imagery in under 5 minutes on site. It's the right choice for teams that need On-Premises capability but want plug-and-play simplicity.

Yes. The On-Premises version is designed to run in fully closed, air-gapped networks with no external internet connectivity. All operations — mission planning, live video, data storage, Dock management — are handled internally. Some peripheral features such as offline maps and live weather data may have limited functionality since they require external data sources, but core operational capability is fully offline.

FlightHub 2 On-Premises can be deployed on physical/bare metal servers, virtualised infrastructure (VMware or Hyper-V), private cloud environments, or your own public cloud account. A single IT engineer can complete deployment in one day under DJI's recommended conditions. Minimum server specifications should be confirmed with our team, as requirements vary depending on fleet size, expected concurrent users and optional modules such as local 3D modeling.

The Basic Package includes one year of software upgrades — new features, hardware compatibility updates and security patches. The Validity Period Extension continues this coverage beyond the first year. If you don't renew, your installation continues to work but stops receiving updates. Given DJI regularly adds new aircraft compatibility, most operational programmes should budget for the extension as an ongoing cost.

Yes — DJI Dock 3 integration is fully supported on the On-Premises version, including mission scheduling, live monitoring and automated deployment management, all handled within your local network.

For the software-only version, a working knowledge of server administration is needed — the ability to deploy an application in your chosen environment. DJI says a single IT engineer can complete deployment in one day under recommended conditions. If your team doesn't have this in-house, the Deployment & Operations Staffing Services provide DJI-authorised on-site support. If you want to avoid IT complexity entirely, the AIO is the practical alternative.

Yes. The On-Premises version includes FlightHub OpenAPI (RESTful) for integration with third-party platforms, GIS systems, and enterprise IT infrastructure, plus MQTT Bridge for industry application integration. Three frontend components — Flight Routes Editor, Virtual Cockpit, and Project/Map — can also be embedded directly into your existing internal platforms with UI customisation, significantly reducing development workload for organisations building a bespoke drone management interface.