How To Get Started With DJI FlightHub 2 On-Premises
You may have decided that it’s time to take your drone data private and that DJI FlightHub 2 On-Premises is the right solution for your organization. The next question is: how do you get started?
FlightHub 2 On-Premises is a private deployment of DJI’s FlightHub 2 platform that can be hosted on a locally maintained server, a private cloud server, or a public cloud server. Unlike the public version of FlightHub 2, which is hosted on DJI-managed AWS infrastructure, the on-premises version gives your organization full control over where drone images, videos, and flight data are stored, as well as who can access them.
This level of control is especially important for organizations handling sensitive data or operating under strict security, compliance, or data-residency requirements. Choosing the right deployment model depends on your internal IT capabilities, security posture, and operational priorities. The sections below outline the available hosting options to help you determine which approach best fits your needs.
Locally Maintained Server
One of the deciding factors in how to get started is your team’s internal capabilities. Maintaining physical server equipment requires IT expertise in networking and systems administration, as you will need to install and configure FlightHub 2 on your own hardware and be responsible for the ongoing health of the system. This includes hardware maintenance, software updates, backups, security patching, and managing internal networking between your computers, server, and DJI equipment.
This option provides the highest level of control over your data, as everything remains within your physical environment. However, it also comes with the highest operational overhead and is best suited for organizations with dedicated IT staff and strict data residency or compliance requirements.
Private Cloud Server
A private cloud server is a middle ground between a locally maintained server and a public cloud deployment. In this model, FlightHub 2 On-Premises is hosted in a cloud environment dedicated exclusively to your organization, either through a managed service provider or within your own virtual private cloud (VPC).
This approach offers strong data isolation and control while reducing the burden of maintaining physical hardware. Your team is still responsible for configuring the server, managing access controls, and maintaining the FlightHub 2 application, but many infrastructure concerns, such as hardware reliability and scalability, are handled by the cloud provider. A private cloud server is ideal for organizations that require enhanced security and control with greater flexibility than on-site infrastructure.
Public Cloud Server
A public cloud server is a strong option for smaller organizations or teams that want to leverage the infrastructure and reliability of cloud providers such as Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform. In this setup, FlightHub 2 On-Premises runs in your own cloud account while benefiting from enterprise-grade networking, storage, and availability.
Public cloud deployments typically offer faster setup times, easier scalability, and lower upfront costs compared to physical servers. They also allow organizations to implement robust security controls, such as private networking, encryption, and identity management—without managing physical hardware. This option works well for teams seeking data control while minimizing IT overhead.
DJI All-In-One (AIO) Option
In addition to the deployment models described above, DJI also offers an All-In-One (AIO) solution for FlightHub 2 On-Premises. The AIO option combines preconfigured hardware and software into a single system designed to simplify deployment and reduce initial setup complexity.
Because the hardware and software are validated together by DJI, the AIO approach can reduce the risk of configuration issues and compatibility concerns. It may also lessen the operational burden on internal IT teams by providing a known, supported system architecture. However, adopting the AIO solution involves placing a greater level of trust in DJI’s hardware design, update process, and long-term platform support.
For organizations that want the benefits of an on-premises deployment with a more standardized and turnkey implementation, the AIO option can be worth considering. As with any infrastructure decision, it’s important to evaluate how much control, flexibility, and internal ownership your organization requires.
Deployment Options Comparison
| Deployment Option | Level of Data Control | IT & Maintenance Effort | Scalability & Flexibility | Best For |
|---|---|---|---|---|
| Locally Maintained Server | Highest – all data remains fully on-site | Highest – full responsibility for hardware, software, updates, and security | Limited by physical infrastructure | Organizations with dedicated IT teams and strict data residency or compliance requirements |
| Private Cloud Server | High – isolated cloud environment dedicated to your organization | Moderate – no physical hardware, but application and access management required | High – scalable within a controlled cloud environment | Teams needing strong security and control with more flexibility than on-site infrastructure |
| Public Cloud Server | Moderate to High – data controlled within your own cloud account | Lowest – simplified infrastructure management with no physical hardware | Very High – rapid scaling and fast deployment | Organizations prioritizing speed, flexibility, and lower upfront costs |
| DJI All-In-One (AIO) | High – on-premises data storage using DJI-validated hardware | Low to Moderate – simplified setup with reliance on DJI hardware and validation | Moderate – scaling limited to system capacity | Teams wanting an on-premises solution with reduced setup complexity and standardized infrastructure |
If you are considering taking your drone data private, Terrestrial Imaging can support you with both FlightHub 2 On-Premises licensing and experienced consulting services. Our team works with organizations to evaluate deployment options, align infrastructure decisions with security and compliance requirements, and guide the implementation process from planning through deployment.
