media server logo
PricingAPI docsStart in the cloud for free

Live video routing control layer

Jun 04, 2026
Iurii Pakholkov

Written by Iurii Pakholkov

Founder of Callaba. Building cloud video tools for SRT, RTMP, WebRTC, NDI, live routing, monitoring, recording, and production workflows.

Release: Callaba 8.4

Live video routing · multiview · failover · recording · delivery

Browser-based hub to receive, route, monitor, failover, record, and deliver live video for live sports teams, remote production crews, corporate event teams, OTT teams, AV integrators, and broadcast engineers.

  • See every source
  • Know what is live
  • Switch to backup
  • Record the feed
  • Deliver to the right destination
Try live video routing Open multiview demo See deployment options
Live sports teamsKeep the program feed, backup feed, replay path, and delivery output visible during the match.
Remote production crewsReceive venue feeds over SRT, check status in the browser, and route sources to the right production tools.
Corporate event teamsMonitor presenters, backup sources, recording, and delivery without depending on one local control room.
AV integrators and OTT teamsGive clients a repeatable control layer for ingest, monitoring, failover, recording, playback, and delivery.

Event control view

Live
Program feedSRT · 8.2 Mb/s · audio present · RTT 42 ms
LIVE
Backup feedSRT · 6.9 Mb/s · checked 00:02 ago
READY
CDN outputHLS · recording active · delivery healthy
OK
Remote guestWebRTC · packet loss 0.8% · watch closely
CHECK

Main feed status: unstable bitrate detected. Backup is ready and already monitored.

Switch output to backup

Quick answer

Use Callaba when your live video workflow needs more than SRT or RTMP transport. Callaba becomes the control layer around the stream: receive it, preview it, check status, route it, prepare backup, record it, and deliver it to production tools, web players, CDNs, remote operators, and API workflows.

For teams that need control during a live event

The main problem is not always sending a stream. The harder problem is operating the stream when people are watching. Callaba is built for teams that need a clear browser view of sources, routes, backup state, recording, and delivery.

Live sports productionUse one place to receive venue feeds, keep backup ready, record the event, and deliver to production or OTT outputs.
Remote production crewsGive off-site operators a browser view of incoming feeds, audio, bitrate, failover, and delivery state.
Corporate events and webinarsRoute presenters, backup feeds, recordings, playback, and web delivery without rebuilding the workflow during the show.
AV integratorsBuild client workflows that are encoder-agnostic, cloud-ready, and easier to support during live jobs.
OTT and media teamsControl ingest, monitoring, recording, playback, and delivery around live channels or event streams.
Broadcast engineersSee source state, network stats, backup readiness, and routes without jumping between separate tools.

Why the control layer matters

Transport solves one part of the job. It moves video from one place to another. But the pressure starts when the event is live and the team needs to answer operational questions in seconds.

How it works

Callaba sits between contribution sources and production or delivery outputs. The same live feed can be previewed, routed, recorded, switched to backup, sent to multiview, delivered to a player, and controlled through API logic.

Operator visibility

During a live event, source names are not enough. Operators need visual confidence and technical status: is the feed live, is audio present, is the route stable, is recording active, and is the backup ready?

CAM 1
Program feed · live · 8.2 Mb/s
CAM 2
Backup feed · ready · 6.9 Mb/s
REMOTE
Guest feed · WebRTC · stable
OUTPUT
CDN preview · recording active
Incoming bitrate8.2 Mb/s
AudioPresent
RTT42 ms
Packet loss0.02%
RecordingActive
BackupReady

Failover during the event

Backup should not be an idea that appears after the main stream fails. For live production, the main and backup path should be planned before the show. Callaba helps keep that logic visible to the operator.

Key capabilities in business language

The value is not only that Callaba supports protocols. The value is that teams can control what happens around the live stream without being locked into one encoder, switcher, player, or cloud design.

Connect cameras and encoders without protocol lock-in

Receive SRT, RTMP, WebRTC, HLS, and other inputs depending on the workflow.

SRTRTMPWebRTCHLS
Understand in seconds which source needs attention

Use preview, bitrate, audio state, RTT, packet loss, uptime, and route state to find issues fast.

8.2 Mb/sAudio present0.02% loss
Send one feed to recording, live output, archive, and operators

Use the stream once and route it to multiple downstream jobs without changing the encoder.

RecordMultiviewRestreamDelivery
Automate routine video operations through API

Build repeatable event workflows, remote control panels, and internal tools around Callaba controls.

APIRepeatable eventsCustom logic
Record and use files during the show

Record live inputs and keep files available for post-event use, fast review, or workflow automation.

RecordingPlaybackArchive
Support remote operators without extra viewing hardware

Browser multiview helps teams check live sources and outputs even when they are not in the control room.

Browser multiviewRemote viewSource status

How Callaba is different from adjacent tools

Callaba is not trying to replace every tool in the live production chain. It is the control layer around contribution, routing, monitoring, failover, recording, and delivery.

Not a cloud switcherTools like vMix and Wirecast are used for production switching, graphics, scenes, and program creation.Callaba manages live video routes, source status, failover, recording, and delivery around the production workflow.
Lighter than orchestration suitesLarge orchestration and monitoring platforms can be powerful, but they may be too heavy for teams that need a focused workflow layer.Callaba gives teams a practical browser-based layer without forcing a full enterprise orchestration stack.
More than simple restreamingBasic restreaming moves video to destinations, but the event team still needs visibility and control.Callaba adds monitoring, multiview, backup logic, recording, playback, and API workflows around transport.

Deployment options

Callaba can run where the workflow needs control: in the cloud, on AWS, in private cloud, or as a self-hosted Linux setup. This keeps teams flexible instead of forcing one fixed appliance or one closed ecosystem.

CloudUse Callaba as an internet-facing workflow hub for remote contribution and delivery.
AWS setupDeploy close to your production region and keep live event infrastructure repeatable.
Self-hosted LinuxRun Callaba on your own machine or server for local, private, or on-prem workflows.
Private cloudKeep live video routing and monitoring inside your own infrastructure plan.
Deploy control layer Open API docs

The first workflow should be simple enough to test in minutes: one source, one monitoring view, one backup, one recording path, and one delivery output.

Start with one real live event path

  • 1Create ingestStart with one SRT or RTMP source from an encoder, camera, or production tool.
  • 2Open multiviewCheck preview, audio, bitrate, stream state, and output confidence in the browser.
  • 3Add backupPrepare a second source before the event and confirm it is ready.
  • 4Record and deliverRecord the feed and send it to the production tool, player, CDN, or archive path.

FAQ

Is Callaba only an SRT gateway?

No. Callaba can receive SRT streams, but the stronger use case is the full live workflow around the stream: monitoring, routing, failover, recording, playback, delivery, and API control.

Does Callaba replace a production switcher?

No. Callaba is not a cloud switcher. It does not replace vMix, Wirecast, hardware switchers, graphics systems, or creative production tools. Callaba controls routing, monitoring, failover, recording, and delivery around those tools.

What about latency?

Latency depends on the protocol, network path, region, bitrate, encoder settings, and player path. For contribution workflows, teams usually balance latency against stability. Callaba helps operators see stream health and choose the right setup for the event.

What servers do I need?

It depends on the number of inputs, outputs, recordings, transcodes, viewers, and whether the workflow runs in the cloud, on AWS, or self-hosted Linux. A simple routing and monitoring workflow can start small, while high-output or transcoding-heavy jobs need stronger instances.

Can Callaba work with different encoders?

Yes. Callaba is encoder-agnostic. It can fit into workflows built around cameras, hardware encoders, software encoders, WebRTC sources, SRT sources, RTMP sources, and production tools.

Can the workflow run in the cloud and locally?

Yes. Callaba can be used in cloud workflows, AWS deployments, private cloud setups, and self-hosted Linux installations.

Why does browser multiview matter?

Browser multiview gives operators a fast way to check incoming feeds and output state without extra viewing hardware. It helps remote teams understand what is live, what is ready, and what needs attention.

Try live video routing with Callaba

Start with one live source, check it in the browser, add routing, prepare backup, record the feed, and deliver the output. Callaba gives your team one place to control the workflow around the stream.