DJI Dock 3 does not fly on its own. Something has to design the routes, issue the tasks, watch the flight and store what comes back. DJI's own answer is FlightHub 2. Because DJI publishes a Cloud API, third-party platforms can fill the same role — and for a lot of operators, that is the more interesting option. Here is what actually differentiates them.
1. Which mission types you can build
Any platform can do waypoints. The questions to ask are whether it supports strip and area missions with overlap-driven spacing, terrain-aware altitudes, per-waypoint camera actions, and immutable published route versions. Without versioning you cannot prove that this month's flight matched last month's.
2. How tasks are scheduled and validated
Look for three ways to trigger a task: immediately, on a schedule tied to the dock's local time, and when the dock reports itself ready after a previous mission. Then look at the preflight gate — a good platform refuses to launch when the battery, storage, aircraft health, weather readings or airspace state say it should not, and tells you exactly which check failed.
3. Live supervision that is actually usable
Telemetry, streaming video and a map, all in one view, with the ability to intervene: pause, resume, return to home, land. And crucially, a record of what happened after the fact — which task ran, what the aircraft did, and where the media went.
4. Where the data lives
This is the point where third-party platforms most often win in Europe. Flight tracks, imagery and video from a dock are operational data and, in many cases, personal data too. If keeping it inside EU datacentres under GDPR matters to your clients or your procurement process, verify it at the contract level, not just in marketing copy. We go into detail in GDPR and EU data residency for drone operations.
5. Whether you can put your own brand on it
If you sell drone services rather than fly them for yourself, the platform your client logs into is part of your product. A white-labellable platform lets you present it under your own name, colours and domain. A closed one makes you a reseller of someone else's brand. See white-labelling a drone operations platform.
6. Integration and exit
Ask what happens at the edges: can you push mission results into your own systems, export raw media and telemetry, and pull status into an existing dashboard? And can you get all of your data out if you leave? A platform without an export path is a platform you cannot leave.
7. Infrastructure burden
Some options are self-hosted, which means servers, updates, uptime and security are now your problem. A cloud service moves all of that off your plate. Neither is automatically right — but be explicit about which one you are signing up for.
A short evaluation checklist
- Waypoint, strip and area missions with versioning
- Immediate, scheduled and ready-triggered tasks
- Preflight validation with clear failure reasons
- Live telemetry, video and intervention controls
- EU data residency, stated contractually
- White-labelling: name, colours, domain
- Export and integration paths
- No infrastructure to run yourself
Timoneiro was built against exactly this list, for operators running DJI Dock 3 with Matrice 4 series aircraft in Europe.