DJI FlightHub 2 Guide: Managing Multi-Site Drone Operations in Canada
Structure one organization across multiple sites, aircraft and docks. Standardize projects, roles, routes, alerts, mapping, security, integrations, resource quotas and Canadian operating procedures.
Multiple projects, sites, drones and docks
FlightHub 2 creates the most value when an organization uses it as a shared operating system—not just a live-view page. Build one governance model, separate sites into controlled projects, standardize route templates and alerts, and measure whether drone data reaches the people who must act on it.
What DJI FlightHub 2 manages
DJI FlightHub 2 is a cloud-based drone operations platform for remote control, flight planning, scheduling, livestreaming, mapping, analysis, automated workflows, fleet records and third-party integration. DJI also offers an on-premises version as software-only deployment or an all-in-one appliance.
Virtual Cockpit and live coordination
Operators can remotely control compatible aircraft, manage multiple drones, use FlyTo tasks, view AR overlays, share live annotations and display multiple livestreams.
Routes, schedules and task libraries
Teams can create reusable routes, schedule flights, assign tasks, manage geographic constraints and standardize collection across sites.
Media, mapping and Analyzer
Flight results can be uploaded, organized, reconstructed into 2D or 3D outputs, compared over time, annotated and measured inside the platform.
Triggered and periodic workflows
FlightHub 2 can connect alerts, FlyTo tasks, aircraft actions, cloud reconstruction, analysis and report generation into repeatable automated workflows.
OpenAPI and FlightHub Sync
RESTful OpenAPI supports custom integration, while FlightHub Sync provides low-code file, status, notification and livestream-forwarding connections.
Roles, logs, alerts and records
Custom project roles, flight records, user actions, alerts and dashboards help organizations supervise activity across multiple sites.
Not a universal fleet platform: DJI states that FlightHub 2 does not connect drones from other manufacturers. Its current supported-device list also excludes DJI Mavic 3 Multispectral.
Design one operating model before adding the tenth site
Multi-site programs fail when every location invents its own naming, routes, permissions, data folders and escalation rules. A scalable FlightHub 2 structure separates corporate governance from site execution while preserving local operating control.
Own subscriptions and policy centrally
The organization should own the FlightHub plan, device-binding strategy, global roles, naming standard, data policy, integration and audit process.
Use a project as the controlled operating boundary
Create separate projects for locations or mission families that need distinct users, routes, devices, data visibility or client access.
Standardize route and checklist templates
Use repeatable naming, route design, alert thresholds, annotations and report formats so data from Vancouver, Calgary and Toronto can be compared consistently.
Recommended project name: CA-ON-TOR-SITE01-ROOF-INSPECTION. Include country, province, city or region, site identifier and mission type. Avoid personal names and informal labels such as “Main Project” or “New Dock.”
Bind devices correctly before the free resources are activated
FlightHub plans and entitlements are bound to the organization—not to an individual account. DJI’s current policy also states that initial device-binding quotas are granted only once and are not reallocated when a device is later moved to another organization.
Confirm the permanent owning organization
- Use the legal or operational entity that will own the program
- Avoid binding production devices to a temporary dealer or pilot workspace
- Confirm administrators and recovery contacts
- Record serial number, site, owner and activation date
Separate administration from flight authority
- Organization administrator
- Program or regional manager
- Mission planner
- Pilot or remote operator
- Maintenance technician
- Analyst, viewer or client guest
Review users by event and schedule
- Approve access before assignment
- Use least privilege by project
- Remove contractors when work ends
- Review inactive users quarterly
- Preserve logs during incident review
Free onboarding quota: DJI currently states that an eligible organization receives 100GB storage, 5,000 livestream minutes and 3,000 mapping images for three months when the first qualifying device is bound. Confirm the live entitlement before activation.
Current FlightHub 2 device support
DJI’s current supported-device list includes its dock families, major Matrice platforms and selected Mavic 3 Enterprise aircraft and Zenmuse payloads. Always verify the exact aircraft, controller, payload and firmware combination.
DJI Dock 3, Dock 2 and Dock
Dock systems enable scheduled and remotely supervised workflows, remote status, charging, route execution and automated data upload.
Matrice 400 and Matrice 4 families
DJI Matrice 400, Matrice 4 Series and Matrice 4D Series support modern FlightHub 2 remote, AI, mapping and automated workflow features.
M350, M30 and Mavic 3 Enterprise
DJI Matrice 350 RTK, Matrice 30 Series and Mavic 3 Enterprise Series remain supported, subject to the exact configuration and firmware.
Zenmuse H30, H20, S1 and V1
FlightHub 2 supports current and established multisensor, spotlight and speaker payload workflows on compatible aircraft.
Mavic 3 Multispectral
DJI specifically excludes Mavic 3 Multispectral from the current FlightHub 2 Mavic 3 Enterprise support statement. Plan M3M data workflows separately.
Not supported
DJI states that FlightHub 2 does not connect aircraft from other manufacturers. Mixed-fleet organizations need an integration strategy outside FlightHub 2.
Manage real-time missions without losing local accountability
Remote control and camera operation
Compatible devices can be controlled through a browser with mouse and keyboard. Use this for authorized remote tasks, incident response and dock operations—not as a substitute for SOPs.
Coordinate more than one live aircraft
FlightHub 2 supports synchronized multi-drone control, automatic swap tasks and one-click return-to-home for multiple aircraft on supported configurations.
Rapidly direct a compatible drone to a point
An operator selects a destination and FlightHub 2 plans a route. Use FlyTo only within approved operational boundaries and after checking route hazards.
Annotations, sharing and multi-view
Teams can annotate shared maps, assign areas, generate livestream links and display multiple feeds for coordinated situational awareness.
Weather, device and mission exceptions
Build an escalation process around FlightHub alerts. An alert without an owner, response timer and closure rule is only a notification.
Reduce—but do not eliminate—site visits
Operators can inspect compatible dock and aircraft status remotely. Physical inspection, cleaning, repairs and site security still require field service.
Human-in-the-loop: DJI states that FlightHub 2 Copilot actions require explicit human confirmation and can be paused. The accountable operator remains responsible for the operation, even when the platform plans or recommends an action.
Build a controlled route library for every site
A route is an operating configuration, not merely a line on a map. Multi-site teams should control route ownership, version, payload settings, weather limits, emergency sites, expected output and revalidation triggers.
| Route field | Required standard | Revalidation trigger |
|---|---|---|
| Name | Region, site, asset, mission and version | Any approved scope change |
| Aircraft and payload | Exact model, lens, camera mode and accessory | Hardware, firmware or payload change |
| Altitude and speed | Mission-specific collection and safety values | Regulatory, obstacle or output change |
| Camera settings | Resolution, overlap, zoom, thermal range or exposure logic | Output specification change |
| Weather limits | Wind, precipitation, temperature and visibility | Seasonal or site-risk review |
| Emergency actions | RTH, alternate landing, lost link and abort points | Site layout or communication change |
| Data output | Folder, naming, model type, report and recipient | Business-system or client change |
| Approval | Owner, reviewer, effective date and expiry | Scheduled review or incident |
Create once, adapt carefully
A corporate template should standardize naming, payload, collection logic and outputs. Each site still needs a local route and safety review.
Never overwrite a production route silently
Retain the previous approved version, record changes and require review before the new route enters a schedule.
Watch the real world change
New cranes, towers, vegetation, buildings, RF sources and population patterns can invalidate an older route even when no one edited it.
Turn flights into repeatable business outputs
Standardize file metadata and retention
Organize images and video by project, date, site, route, asset and mission. Define what is retained, exported, shared or deleted.
Create comparable models across time
Automated upload and cloud reconstruction can support construction progress, stockpile, infrastructure and site-change workflows.
Measure, compare and report
Analyzer supports visual site review, annotations and volume calculations using fitted planes, design files and multi-phase comparisons.
Focus attention on what changed
Use repeated collection and change detection to identify progress, anomalies or asset changes rather than manually reviewing every image.
Deliver the result without exposing the whole project
Use controlled sharing links, reports or integrated systems according to the client’s access and privacy requirements.
Push outputs into the workflow of record
Use OpenAPI or FlightHub Sync to connect media, models, annotations, status and event notifications to GIS, inspection or work-order systems.
Use AI to narrow human attention—not remove accountability
Search live video by text or image
Compatible workflows can use text or reference images to find objects in Virtual Cockpit and generate alerts for operator review.
Query collected images and video
Multimodal search can help teams find objects or anomalies across media and generate operational reports.
Attach detection to repeatable routes
Apply supported algorithms to patrol tasks so detections, locations, timestamps and imagery are recorded for review.
Alert → FlyTo → aircraft action
A trigger can create an automatic or manually confirmed dispatch workflow for public safety, emergency response or site patrols.
Collect → model → measure → report
Drag-and-drop automation can connect recurring collection, reconstruction, analysis and report delivery.
Integrate specialized detection
DJI currently limits third-party onboard or cloud algorithm integration to supported newer platforms including Dock 3, Matrice 4 and Matrice 400.
Validation requirement: test detection accuracy, missed detections, false alerts, lighting, weather and site-specific backgrounds before using an AI result to trigger a response. Keep a human approval point where the consequence is material.
Choose cloud or on-premises based on policy—not fear or convenience
DJI states that FlightHub 2 data for users outside mainland China is stored on AWS servers in Virginia, United States or Frankfurt, Germany. DJI also states that FlightHub 2 holds ISO/IEC 27001 and ISO 27701 certifications and offers private on-premises deployment, including isolated intranet environments.
Use SSO, MFA and least privilege where available
- Centralize account ownership
- Use custom project roles
- Separate administrators from operators
- Review contractor and dormant access
Document where data can be stored
- Confirm public-cloud region and contract terms
- Assess cross-border and sector requirements
- Evaluate on-premises for sensitive environments
- Record export and integration destinations
Minimize unnecessary personal information
- Define lawful and approved capture purposes
- Avoid unrelated homes, people and licence plates
- Use retention and deletion rules
- Control livestream links and media sharing
Segment docks and operator workstations
- Use managed business networks
- Monitor loss, latency and account changes
- Protect routers and cellular accounts
- Restrict integration credentials
Retain flight and user records
- Export records according to the selected plan
- Investigate abnormal user and aircraft actions
- Preserve incident evidence
- Review permissions and routes periodically
Private control adds private responsibility
- Size compute, storage and backup
- Patch and monitor the environment
- Provide identity and network integration
- Budget implementation and support
Recommended public-sector gate: complete architecture, privacy, security, data-flow and retention reviews before loading operational data. A certification does not automatically satisfy an organization’s own policy.
Standard vs Business vs Enterprise vs On-Premises
DJI’s current public comparison uses four tiers. Pricing should be confirmed through DJI or an enterprise dealer because package structure, online-device licences and add-ons can change.
On smaller screens, swipe the table left to compare plans.
| Plan | Best fit | Current headline resources | Multi-site considerations |
|---|---|---|---|
| Standard | Trials, small teams and basic evaluation | Free; 5GB storage; 5 accounts; limited advanced features | Use to validate workflow, not as the assumed long-term national plan |
| Business | Operational teams needing professional features with finite quotas | 2,000 livestream minutes/month; 500GB storage; 3,000 mapping images/month; unlimited accounts | Good for moderate multi-site programs if quota consumption is measured and add-ons are planned |
| Enterprise | Heavy-use, government and larger fleets | Complete feature set; most resources broadly available; online-device and mapping entitlements are package-specific | Plan device concurrency, dock-camera minutes, mapping volume and licence expansion before rollout |
| On-Premises | Private infrastructure and stricter data control | Software-only or AIO; up to 200 devices; each AIO supports up to 20 devices; infrastructure-dependent capacity | Requires internal hosting, security, backup, operations and support ownership |
Viewer time multiplies consumption
DJI calculates total watch time across all viewers and all supported livestream uses. Ten people watching a 30-minute feed consume 300 livestream minutes.
Business quota rolls only once
DJI states that unused Business livestream and mapping quotas can roll into the next month only, then expire if unused.
Existing data remains accessible
When storage entitlement expires, DJI says existing files remain accessible, but additional data cannot be uploaded until capacity is restored.
Plan-binding rule: activation codes bind to an organization. Confirm the production organization before activation and document who owns renewal, quota monitoring and licence expansion.
FlightHub 2 can manage the operation—but it does not make the flight legal
Standard operations still require the correct pilot and aircraft
Use the applicable Basic or Advanced framework for VLOS missions, including registration, pilot certification, airspace approval and declared capability where required.
Lower-risk BVLOS under defined conditions
Transport Canada’s Level 1 Complex pathway permits certain lower-risk BVLOS operations in uncontrolled airspace below 400ft and in qualifying population environments.
The operator needs an organizational safety system
Level 1 Complex operations must be conducted under an RPAS Operator Certificate with accountable management, training, SOPs, maintenance responsibility and safety-risk processes.
Operations outside the prescribed categories
More complex BVLOS, aerodrome operations, higher altitude, hazardous payloads and other missions outside Basic, Advanced or Level 1 Complex may require an SFOC-RPAS.
Each site still needs local validation
A centrally approved FlightHub template does not replace the site survey, route assessment, weather review, population review and local operating authorization.
ADS-B is not a complete Detect and Avoid solution
Airspace awareness tools support the operator but do not alone satisfy every DAA, crew or risk-control requirement for a remote operation.
Core rule: a FlightHub route, schedule, AI alert or automatic dispatch must remain inside the operator’s approved operational volume, aircraft declaration, weather limits, airspace permission and emergency procedures.
Roll out FlightHub 2 in five controlled phases
Design
Mission, sites, governance, compliance, devices, data and success metrics.Pilot
One site, a small user group, controlled routes and measured quota consumption.Standardize
Templates, naming, roles, alerts, reporting, security and operating procedures.Scale
Add sites in waves with acceptance testing, training and support readiness.Optimize
Use KPIs, automation, AI and integrations to improve decisions and cost.| Workstream | Pilot acceptance criteria | Scale requirement |
|---|---|---|
| Organization | Correct production organization and administrators | Documented ownership, renewal and recovery |
| Projects | One site with approved structure and naming | Reusable project template and regional boundaries |
| Users | Role matrix tested | Joiner, mover, leaver and periodic access review |
| Devices | Compatible hardware and firmware validated | Asset inventory, spares and service process |
| Routes | Versioned and approved route library | Route review and change-control standard |
| Network | Bandwidth, latency and failover tested | Site monitoring and outage escalation |
| Data | Outputs reach the business owner | Retention, integration and archive design |
| Operations | Normal and emergency SOPs exercised | Training, recency, RPOC or SFOC governance |
| Quotas | One month of real consumption measured | Plan and add-on forecast by site growth |
| Security | Identity, privacy and architecture approved | Logging, incident response and annual review |
KPIs for a national or multi-site drone program
Avoid vanity metrics: flight count, total distance and stored images can rise while business performance worsens. Measure usable outputs, response time, uptime, avoided mobilization and verified actions.
Estimate monthly livestream, mapping and storage demand
Enter an expected multi-site operating pattern. The calculator estimates resource use only; it does not calculate subscription price or confirm plan eligibility.
DJI calculates livestream use from total watch time. Multiple viewers multiply consumption. Mapping-image and storage estimates depend on actual route settings, image size, video, reconstruction and retention practices.
Plan a FlightHub 2 multi-site deployment
SpeedyDrone Canada can help scope compatible DJI Enterprise aircraft, Dock 3 systems, accessories, FlightHub 2 planning, training and deployment partners. Send your number of sites, aircraft, docks, mission types, mapping volume, livestream demand, security requirements and Canadian operating model.
Include: organization type, provinces, sites, aircraft, docks, payloads, VLOS/BVLOS goal, FlightHub tier, cloud/on-premises preference, SSO/MFA need, mapping images, livestream viewers, integrations, target go-live date and procurement process.
DJI FlightHub 2 FAQ
What is DJI FlightHub 2?
DJI FlightHub 2 is a cloud-based enterprise drone operations platform for remote control, route planning, scheduling, livestreaming, mapping, analysis, automation, fleet records and integration.
Can FlightHub 2 manage multiple sites?
Yes. Organizations can create separate projects, assign devices and users, manage routes and data, and use dashboards and records across multiple locations.
Which DJI devices are supported by FlightHub 2?
DJI’s current list includes Dock 3, Dock 2, Dock, Matrice 400, Matrice 350 RTK, Matrice 30 Series, Matrice 4 Series, Matrice 4D Series and Mavic 3 Enterprise Series, excluding Mavic 3 Multispectral, plus selected Zenmuse payloads.
Can FlightHub 2 connect non-DJI drones?
No. DJI states that FlightHub 2 does not support drones from other manufacturers.
Does FlightHub 2 support Mavic 3 Multispectral?
No. DJI’s current supported-device statement specifically excludes Mavic 3 Multispectral from the Mavic 3 Enterprise Series support list.
What are the current FlightHub 2 plans?
DJI currently lists Standard, Business, Enterprise and On-Premises. Features, quotas, online-device limits and pricing vary by tier and purchased package.
How does FlightHub 2 livestream usage work?
DJI counts total viewing time. If three people each watch a 20-minute livestream, the organization consumes 60 livestream minutes.
What free resources come with a newly bound enterprise device?
DJI currently states that an eligible organization can receive 100GB storage, 5,000 livestream minutes and 3,000 mapping images for three months when initially binding a device.
Can a FlightHub 2 plan be moved between organizations?
Activation binds the plan to the organization. DJI also states that free device-binding quotas are not reallocated when a device is later moved to another organization.
Where is FlightHub 2 cloud data stored?
DJI states that data for users outside mainland China is stored on AWS servers in Virginia, United States or Frankfurt, Germany.
Does FlightHub 2 support on-premises deployment?
Yes. DJI offers software-only and all-in-one on-premises options, including deployment inside an isolated intranet.
Does FlightHub 2 support SSO and MFA?
DJI lists Single Sign-On and Multi-Factor Authentication as secure-login features. Confirm availability and configuration for the selected tier or deployment.
What bandwidth does FlightHub 2 require?
DJI recommends at least 50Mbps for FlightHub 2 and FlightHub 2 On-Premises. Actual requirements rise with simultaneous livestreams, mapping uploads and user count.
Does FlightHub 2 authorize BVLOS flight in Canada?
No. Canadian BVLOS operations must fit the applicable Level 1 Complex or SFOC-RPAS pathway and may require a Level 1 Complex pilot, an RPOC and an aircraft safety declaration.
What is the best project structure for multiple sites?
Use one controlled organization and separate projects by site or mission family when users, devices, routes, data access or client visibility differ.
Where can I request FlightHub 2 support in Canada?
Contact SpeedyDrone Canada with the planned sites, aircraft, docks, mission types, security requirements, integrations and intended operating category.
- DJI Enterprise: FlightHub 2 features, plans, automation, AI and integrations
- DJI Enterprise: FlightHub 2 FAQ, devices, cloud locations and quotas
- DJI Enterprise: FlightHub 2 user guide and data-security documentation
- DJI Enterprise: FlightHub 2 tutorials
- DJI Enterprise: Dock 3 and FlightHub 2 remote workflow
- Transport Canada: Level 1 Complex and lower-risk BVLOS
- Transport Canada: RPAS Operator Certificate
- Transport Canada: Special drone operations and SFOC-RPAS
- SpeedyDrone Canada: DJI Dock 3
- SpeedyDrone Canada: DJI Enterprise solutions
- SpeedyDrone Canada: Enterprise contact and quote request
This article is general planning information, not legal, aviation, cybersecurity or privacy advice. Features, plans, quotas, pricing, supported devices, cloud locations, firmware and regulations can change. Confirm the current DJI documentation, Transport Canada requirements and organization-specific policy before deployment.
