Receive contribution feeds
Bring SRT video from cameras, encoders, or remote production locations into Callaba.
SRT contribution and routing software
Callaba SRT Server
Callaba SRT Server is a cloud-based and self-hosted SRT server solution for receiving SRT contribution feeds, monitoring transport health, and routing live video into multiview, recording, restreaming, and playback workflows.
Looking for the protocol explanation? Read the informational SRT server guide.
Visible product workflow
One SRT contribution feed, multiple production paths
Callaba receives a live SRT feed, exposes transport health to operators, and routes the input into the production workflow you select.
Core capabilities
Operate the SRT feed as a product workflow
Start with the live-video job itself. Automation remains an optional second layer.
Monitor transport health. Keep operational visibility on the incoming transport while the feed is live.
Listener and caller ingest pattern
In the standard ingest path, Callaba runs the SRT listener and the external encoder or source connects as the SRT caller.
Route one input onward
Use the same contribution feed in multiview, recording, restreaming, or playback workflows.
Choose cloud or self-hosted operation
Callaba Cloud: Launch Callaba in the cloud and configure the SRT workflow from the product interface. Self-hosted on Linux: Install Callaba on your own Linux infrastructure when you need direct environment control.
Use cases
Built for live production boundaries
Use Callaba where a reliable SRT contribution feed must enter an operational video workflow.
Remote contribution
Bring a venue or field feed back to a production environment.
Production monitoring
Place incoming video in Multiview so operators can watch the live signal.
Workflow distribution
Pass the received input to recording, restreaming, and playback paths.
Deployment
Choose cloud or self-hosted operation
Both paths run the same product workflow; choose the operating model that fits your team.
Callaba Cloud
Launch Callaba in the cloud and configure the SRT workflow from the product interface.
Self-hosted on Linux
Install Callaba on your own Linux infrastructure when you need direct environment control.
Install on LinuxOptional automation
Explore SRT server API documentationUse the API after the product workflow is clear
The interface is the primary path for evaluating and operating Callaba SRT Server. The API can then automate repeatable configuration and control tasks.
Callaba SRT Server questions
What does Callaba SRT Server do?
It receives SRT contribution feeds, exposes transport health to operators, and routes live video into Multiview, recording, restreaming, and playback workflows.
Can Callaba SRT Server run in the cloud and on my own infrastructure?
Yes. You can launch Callaba in the cloud or install it on your own Linux infrastructure and operate the same SRT product workflow.
Is the API required to use Callaba SRT Server?
No. The product interface is the primary path for setup and operation. The API is an optional second layer for repeatable automation.
Where can a received SRT feed go?
The same received feed can continue into Multiview, recording, restreaming, and playback workflows that you configure in Callaba.
Start with a real feed
Evaluate Callaba SRT Server in your deployment model
Launch in the cloud, install on Linux, or inspect the live Multiview experience before you automate anything.