dji-sdk/Cloud-API-2

DJI Cloud API 2 is an open PaaS for building vertical-industry applications on DJI drone and dock hardware. It targets software integrators and developers who need device management, live streaming, remote control and mission handling inside their own backend rather than in DJI's consumer apps. The repository bundles SDKs, frontend components, a device simulator and sample projects.

What the integration actually gives you

The main efficiency claim is a DaaS (Drone/Dock as a Service) SDK that is object-oriented and chain-callable, hiding the underlying protocol so integrators do not have to wrap it from scratch. Alongside it, independent frontend components cover the cockpit, route editor, flight records and device management/maintenance, with configurable features and themes. Server-side scenarios listed include device management, live streaming, remote debugging and control, media and route/mission management, log management, model reconstruction and private 4G-enhanced video transmission. An open-source demo shows how the interfaces are called README.

How to run a first integration

The documented path is sequential: apply for a licence, deploy the application and device-control base, bring devices onto the cloud, configure authentication, then integrate the frontend components and/or SDK. The repository links each step to its own guide — licence application, deployment, device onboarding, authentication, frontend components and SDK. Third-party downloads such as SDKs, API documents and tools are collected in a download centre downloads. Expect the backend base and authentication to be prerequisites for any device or component work, not optional add-ons.

Development without hardware, and optional AI help

A device simulator with built-in virtual devices and working-condition scenarios is documented so secondary development does not strictly depend on physical drones and docks simulator. A separate AI Plugin assists with integration and is documented on its own page AI Plugin; it is a helper for development, not a runtime component of the deployment path. Demo projects illustrate call patterns and conventions demo.

Conditions to check before committing

• A licence must be obtained through the DJI developer platform; the project describes its own licence as free and not limited by device count, but application is still required licence application.
• This is a hardware-ecosystem PaaS: its capabilities are meaningful only with DJI docks and drones, or the simulator during development. The README does not cover non-DJI hardware or third-party drone protocols.
• The code is Apache-2.0, while the product itself is described as a DJI-licensed PaaS; check the licence terms alongside the repository licence if redistribution matters.
• The documented feature set spans server, frontend and device sides; no single language runtime is stated as covering all paths, so confirm the deployment guide's requirements for your stack deployment.

The GitHub issue tracker is the stated channel for bugs and feature requests, handled by DJI technical support issues.

HotRepo's take

The repository was created in 2026-07 and had 167 stars at the single recorded trending observation on 2026-10-29, a day it gained one star. One board sample cannot establish whether interest is growing or fading.