Live UAS to command in one tap, without the proprietary encoder headache
Most drone-to-command streaming fails in two places: setup that fights the pilot, and latency that makes the feed useless. BabbarOps is built around the pilot, one tap to go live, one login to watch.
You are flying an aircraft over an active scene with one hand and trying to get the feed to command with the other. The encoder needs configuring, a link needs generating, a setting fights you, and the call is still developing underneath all of it. Ask any public safety UAS pilot what goes wrong with live streaming on a real callout and you’ll hear the same two complaints. First, the setup: encoders to configure, links to generate, settings to fight while you’re also flying. Second, the latency: a feed delayed enough that what command sees isn’t what’s happening anymore.
Both trace back to the same root cause. Most streaming tools were built for broadcast or general video, then pointed at public safety. BabbarOps was built the other way around, for the operator, for the callout.
The problem with proprietary encoder workflows
Traditional drone-to-command setups often require a specific encoder, a specific app, or a specific hardware chain to get a feed moving. That creates three failure points:
- Setup time. Configuration that has to happen before, or worse during, a time-critical launch.
- Lock in. The workflow only works with the vendor’s hardware, so the equipment you already own doesn’t qualify.
- Fragility. More components in the chain means more things that can drop mid incident.
When seconds matter, a workflow that adds steps is a workflow that fails.
How BabbarOps makes it simple
BabbarOps approaches live video as an operational problem, not a broadcast problem. Two design choices do the heavy lifting.
1. One tap to go live
A UAS or air unit starts streaming with a single action. No links to generate, no settings to configure at launch. The pilot flies the aircraft. The feed goes live on the wall.
2. One login to watch
Viewers don’t wait for a link to land in their inbox. Anyone in the agency with a need to know logs into their agency’s BabbarOps account, the same login every time, and sees every live feed from the incident. Command, patrol, leadership, and supporting units all watch the same picture without anyone forwarding anything.
Hardware agnostic by design
You already own drones, aircraft, and cameras. BabbarOps is hardware agnostic, so it works with the gear you fly today. No approved-device list to buy into.
- Keep the equipment you already own. If it streams, it can land on the wall.
- No per device license fees. Add an asset without a new invoice or a new contract.
- Grow without switching platforms. New drones, new aircraft, new cameras, same platform.
The same wall holds every vantage point
A drone feed isn’t worth much in isolation. It’s worth a lot sitting next to everything else command can see. On BabbarOps, the UAS feed lands on the same wall as helicopter video, fixed cameras, and even witness video streamed from a phone through EyesOn. One picture, every vantage point, every responder working from the same view.
For a UAS program, the test of a streaming platform isn’t whether it can stream. It’s whether it works on the worst night of the year, with one hand, mid flight, on the equipment you already own. That’s the bar BabbarOps was built to clear.
Yes. BabbarOps is hardware agnostic and works with any drone via standard streaming protocols like RTMP, RTSP, and SRT. There is no proprietary encoder and no approved device list. If it streams, it can land on the wall, with no per-device license fees.
With one tap. A UAS or air unit starts streaming with a single action: no links to generate and no settings to configure at launch. The pilot flies the aircraft and the feed goes live on the wall.
With one login. Anyone in the agency with a need to know logs into their agency's BabbarOps account (the same login, every time) and sees every live feed from the incident. Nobody has to forward a link.
No. BabbarOps live video is live-only and never retained, and the platform is not a system of record, so streaming to command doesn't create a new archive of UAS footage to secure and manage.
Sukh Bhela is a California police sergeant who has served as a UAS operator, UAS supervisor, and incident commander during critical incidents. His experience leading patrol operations and integrating drone technology into public safety responses led him to found BabbarOps, where he builds tools for live situational awareness and incident command. He writes about policing, drone operations, leadership, and the technology shaping the future of emergency response.
The views expressed here are the author's own, written in his personal capacity. They do not represent, and are not made on behalf of, any law enforcement agency or employer.
BabbarOps is an independent commercial product and is not affiliated with or endorsed by any law enforcement agency. Supported equipment and performance depend on agency hardware and network conditions.
