This page is for the person who adds cameras to the wall: the real-time crime center or control-room admin, or the integrator who runs the VMS. The goal is a drone's live picture sitting next to the fixed cameras your room already watches, inside the system you already run. Nebli adds the drone feed; it does not replace your VMS.
The path has three legs.
That is how a DJI drone ends up as an RTSP camera: the DJI app sends RTMP to Nebli, and your VMS pulls RTSPS from Nebli.
| Setting | Value |
|---|---|
| Address | The full RTSPS address from Nebli: rtsps://rtsp.nebli.ai:8554/egress/<id>. Enter it whole; the server address alone returns 404. |
| Port | 8554, already in the address |
| Transport | RTSP over TCP. UDP is refused. |
| Encryption | TLS 1.2 or later, publicly trusted certificate. No SRTP. |
| Video | H.264 |
| Sign-in | Basic, one username and password per drone |
Your VMS needs to open an RTSPS address (RTSP over TLS), or to tunnel RTSP over HTTPS. Nebli does not serve plain RTSP.
To test from a computer before you touch the VMS:
ffmpeg -rtsp_transport tcp -i "rtsps://<username>:<password>@rtsp.nebli.ai:8554/egress/<id>" -f null -A wrong or missing credential returns 401. An unknown drone returns 404.
Any VMS or player able to pull RTSPS over the internet can add a Nebli drone feed as a generic RTSP camera. Nebli does not use a vendor plug-in or a driver for your VMS, so the test is the protocol: can your system open an RTSPS address, with TCP transport and H.264, from an address on the internet?
When the drone lands or the stream stops, your VMS keeps showing the last frame for up to five minutes. If the video comes back in that time, it carries on in the same session. After that the session ends, and the VMS reconnects when the drone streams again.
People who are not at the VMS can watch the same flight on a private link that opens in any browser, with a PIN. And a pilot always flies the aircraft. Nebli never flies on its own.
Each drone has its own credential. Replace password issues a new one, and the old one stops working at once. Disconnect ends the drone's credential, so the VMS can no longer pull it. Archiving or suspending a drone, or deactivating the organization, ends its credential too.
Connecting a VMS needs the Enterprise plan or the video-egress trial. The video your VMS pulls is counted each month; nothing stops or caps it.
Not by itself. The DJI app streams to Nebli using its custom RTMP option, and your VMS pulls the drone's live video from Nebli over RTSPS (RTSP over TLS). On Enterprise, each drone appears in your VMS as one more RTSP camera.
No. The drone is added as a generic RTSP camera. Any VMS or player able to pull RTSPS over the internet can add it.
Yes. The DJI app's connection is outbound, so it works over a hotspot, LTE or Starlink. Nebli fills small gaps and recovers on its own after a full drop.
More than the app's label suggests. On our Matrice 4E bench test, the "1.5M" setting sustained 9.5 to 14 Mbps of real upstream traffic, H.264 at 720p.
No. It gets live video only. Record in your VMS; flights recorded in Nebli stay on its Flights page.
Yes. A private link opens in any browser, with a PIN, and there is nothing to install.
No. PX4 and ArduPilot aircraft, and any RTSP or RTMP camera, connect to Nebli too. This page covers DJI.
A pilot always flies the aircraft. Nebli never flies on its own.
We and our providers use cookies, only if you agree, to measure how our site is used and how our ads perform, and to show our ads to people who have visited our site. You can change your choice any time in Cookie settings.
Choose which cookies we may use. Necessary cookies are always on; the others stay off unless you switch them on. You can change your choice at any time.
Keep the site working and remember your choice.
Keep the site working and secure, and remember your cookie choice. They do not track you.
Cookies: nb_consent (your cookie choice, 12 months); nb_cc (your country, so we know whether to ask, 1 day).
Measure how the site is used, including session recordings.
Google Analytics 4 (Google) and PostHog (PostHog, Inc.) count visits and record which pages are viewed and how the site is used, including session recordings kept for 30 days, so we can improve it. Data is sent to the United States. Cookies: _ga, _ga_* (up to 2 years); ph_* (up to 1 year).
Measure which of our ads bring sign-ups, and show our ads to people who visited our site.
Google Ads, loaded through Google Tag Manager (Google), and our own campaign cookie measure which of our ads and campaign links lead to visits and sign-ups. Google Ads is also used to show our ads to people who have visited our site. We do not use them to show you other companies' ads. Data is sent to the United States. Cookies: _gcl_* (up to 90 days); hover_attr (up to 90 days).