User manual
Live streaming
The house rule: minutes are counted on the channel that broadcasts, never on viewers. Ten people watching cost the same as one.
Channels
A channel is a video source: a drone or a bodycam. The number of channels depends on your plan; the included monthly minutes are consumed only while a channel broadcasts. Every new organization starts with 60 welcome minutes to try everything. When minutes run out, a broadcast won't start (one already running is never cut off): you top up with a higher plan or with packs, which never expire.
Streaming from the drone
Every drone channel has a stable RTMP address with its own key (?key=…): you paste it once into the manufacturer's flight app and it stays valid until you regenerate the key. On DJI enterprise drones connected via Cloud API the live starts with one click from the platform: the address reaches the remote controller by itself — nobody types anything in the field. SRT, WHIP and RTSP are supported too.
The bodycam is the phone
From the Go live page (or the channel's modal) the operator points the phone at a QR: the browser becomes a bodycam — no app to install, the screen stays awake, automatic reconnection, GPS position visible in the room. The link is signed and expires by itself.
The live room
All mission feeds — drone and people on the ground — in a single ops room, with WebRTC latency and the bodycams' position on the map. If the channel is linked to an active mission, the session joins its dossier by itself.
Inviting viewers
Every channel has its own invites: personal, revocable links with an expiry. The guest watches from the browser without an account and, if you want, gets an automatic notice when you go live. For the client or the control room it is just a link.
Many viewers, same quality
How can a live stream hold ten or a hundred viewers without degrading? Because the field transmits only once. The drone (or bodycam) sends a single stream to our media server in Europe: that is the only leg travelling over the field's mobile network, and it doesn't change whether one person is watching or a hundred.
Distribution happens on the server: every viewer receives an identical copy of the original stream, using our infrastructure's bandwidth — not the drone's. This is not a group video call, where every extra participant forces more compression and quality drops for everyone: it is one-to-many distribution, like television. The quality a viewer receives is exactly what the field sent, always.
- Live room and invited viewers: WebRTC delivery with low latency (about one second), for real-time decisions.
- Public events: segment-based HLS delivery, which scales to hundreds of viewers and is CDN-ready — at the cost of a few extra seconds of latency, irrelevant for an audience.
The only real limit is the field connection: if the drone's 4G sustains 5 Mbps, everyone sees those 5 Mbps — at any headcount. Which is also why we can afford to never count viewers in the price.
Public events
For weddings, races and public events there is event mode (Ops plan): a branded public page with a countdown, HLS delivery that scales to hundreds of viewers, QR table cards printable in one click, multiple views with names you choose and the director console — the audience follows the source you put "on air". GB delivered to the audience have a monthly allowance and dedicated packs.
Recordings
Sessions are recorded encrypted with a key belonging to your organization: nobody can open them but you. You download them from the panel, decrypted on the fly.