User manual
Live
The Live cluster gathers the live room, broadcasting, channels, public events, recordings and the guide to getting your drone's video onto the network. There is one house rule: minutes are counted on the channel that broadcasts, never on the viewers. Ten people watching cost the same as one.
Channels and the RTMP key
A channel is a video source, and it comes in two types: Drone (RTMP/SRT) or Bodycam (browser). How many channels you can have is set by your plan.
Every drone channel has a stable RTMP address with its key appended. You configure it once in the flight app or the encoder and it stays valid until you regenerate the key. If you do regenerate it — there is a dedicated action, with a confirmation — the old key stops working instantly and you have to update the drone or the encoder. A bodycam has no key to regenerate, because it publishes from the browser.
The How to stream dialog gives you the address ready to copy, along with the endpoint for publishing from the browser. On DJI drones connected via the Cloud API, actions appear to start and stop the live stream from the platform, with the quality selectable between Adaptive, Smooth, Standard (720p), HD (1080p) and Ultra HD: out in the field nobody types anything. Those actions only appear if the DJI integration is enabled on the installation and there is a remote controller paired.
Managing channels and keys is reserved to Owners and Admins; pilots broadcast from the Go live page.
Stream your drone
Not every drone can send RTMP on its own. The Stream your drone page lets you pick the channel and shows you three ways, each with the address ready to copy.
Way 1 — Native RTMP from DJI Fly. In DJI Fly you open the flight view, go into the settings, choose Transmission, then Live Streaming and Custom RTMP, paste the address and start. It works on the recent range: Mini 3, Mini 4 Pro, Mini 5 Pro, Flip, Air 2S, Air 3 and 3S, Mavic 3, Mavic 4, Avata, Neo. It does not work on the Mini 2, Mini SE and older models: for those, go to the third way. On resolution the guide is precise: with the RC 2 controller and its built-in screen the stream goes out at 720p, whereas with a controller plus a phone you get 1080p.
Way 2 — HDMI from the remote controller. If you have an RC Pro or a smart controller with an HDMI output, you need a USB capture card (around 15 euros). The computer sees it as a webcam: from there you broadcast from the Go live page by picking it as the source, or from OBS using the RTMP address.
Way 3 — screen-cast app. On the phone attached to the remote controller you install Larix Screencaster, add an RTMP connection with the channel's address, start the screen capture and go back to the pilot app. To be clear about it: Larix is a third-party app (Softvelum), the free version has a per-session time limit and Premium is paid. In exchange it works today, on any drone, with no extra hardware.
The bodycam is the phone
From the Go live page, or from the channel's dialog, every bodycam channel shows a button and a QR code. Point your phone at the code and the browser becomes a bodycam: no app to install, rear camera, the screen stays awake while you broadcast, and it reconnects automatically when the 4G wavers.
The link is signed and valid for eight hours, and it opens without a login: it is meant to be handed to whoever is in the field. Owners, Admins and Pilots can use it. The GPS position is sent at most once every fifteen seconds, and positions older than twenty-four hours are deleted.
The control room
The Live ops room puts all of the organization's channels on a tiled wall that refreshes itself every eight seconds: when a channel goes live the player attaches, when it stops it detaches. At the top you read the minutes left and how many channels are broadcasting. If your session expires the wall tells you so and offers you the link to sign back in, instead of making everything look offline.
Below a bodycam tile you get the last position received in the past hour, with its time and accuracy, and a link that opens it on OpenStreetMap. Your organization's logo stays overlaid on the video.
If a channel is set as the primary live channel on a mission template, its sessions join the active mission's dossier by themselves.
Inviting viewers
Every channel has its own invited viewers: a personal link for each, with a name, an optional email and an optional expiry. The guest watches from the browser, without an account. If you leave the option on, they get a notice when you go live — with a limit of one message every ten minutes, so as not to become a nuisance.
An invitation can be revoked and reactivated whenever you like; once revoked, the link opens nothing. For the client or the control room it is, quite simply, a link.
Event mode and the public page
For weddings, races and public events there is event mode, available on the Ops plan. You compose the event with a title, a subtitle, a date and time, a featured source, any other sources and the color: the public page comes out branded, with a countdown before and a closing message after, in your organization's language.
Delivery to the audience is over HLS, which holds up at scale. Viewers can pick their view, and you can give each source a name that means something — "Church", "Backstage". With directing on, the audience instead follows the source you put on air from the director console, with a switch that lands in about six seconds; the console's previews are internal and do not consume the GB allowance.
The QR table cards print in one click: an A4 PDF with eight cut-out cards, in your logo and your color.
Encrypted recordings
Sessions can be recorded, and the files are encrypted with a key belonging to your organization: a new symmetric key for each file, itself protected with your organization's RSA key. Nobody can open them without it. For each recording you get the channel, the start time, the size, the linked mission and the SHA-256 fingerprint of the plaintext content.
The download decrypts on the fly as it goes: a plaintext copy never lands on disk. Deletion is irreversible and it tells you so beforehand.
Minutes and credits
Minutes are consumed only while a channel is broadcasting, counted when the session closes. Watching costs nothing: viewers do not enter the count, and that is a product decision, not a technical detail.
Every new organization receives a one-off 60 welcome minutes if it registers a UAS operator code, 15 minutes without. If you add the code later the difference is topped up, once only. Welcome minutes do not expire.
Your plan adds a monthly allowance of live hours and a number of channels; packs you buy add to the plan and do not expire at month end.
On what happens when minutes run out, the whole truth needs telling. A new broadcast will not start: authorization is refused and the panel says the minutes are gone. And a broadcast already running is closed, but not abruptly: there is a five-minute grace beyond the remaining balance, then publishing is interrupted and Owners and Admins are notified. The one exception is a public event stream that started while there was headroom: that is never cut off halfway.
For events the allowance is in GB delivered, not in minutes, and it is the only line that can go negative, precisely so an event in progress is never switched off. Beyond the credit limit, or after some days in the red, event mode stays suspended for new events until you top up — and the audience, in the meantime, simply sees "offline", never billing details.