Dedicated RTMP listener
Assign the listen port and player buffer for the server that receives publishers such as OBS and software encoders.
RTMP INGEST AND OPERATIONS SOFTWARE
A controlled RTMP ingest point for live production
Callaba RTMP Server gives OBS, software encoders and external publishers a stable RTMP listener with a dedicated port, configurable player buffer and explicit stream-key or IP allowlists. Operate the ingest in Callaba, then connect it to playback, recording and routing workflows.
Publish once, operate the downstream workflow in Callaba
The RTMP listener is the stable ingest boundary. Packaging and downstream modules turn that accepted feed into the production output you choose.
Publisher
- OBS or software encoder
Pushes a live feed to the assigned RTMP host, port and stream name.
Accepts the publisher and applies the configured access rule.
Custom port · buffer · start/stopConnected workflows
- HLS or DASH playback
Prepared packaging directories support player delivery workflows.
- Recording
Use the accepted feed as the source for a recording workflow.
- Restream or handoff
Connect the ingest to the destination module required by production.
The RTMP server owns ingest and access control; playback, recording and routing remain explicit downstream workflow choices.
PRODUCT PROOF
The controls an RTMP operator actually needs
Use a concrete server resource instead of treating an RTMP URL as an unmanaged string. Each listener can be configured, enabled, stopped and connected to the rest of the Callaba workflow.
Publisher and receiver allowlists
Choose explicit stream-key validation or fixed-IP allowlisting when the ingest boundary must reject unknown publishers or receivers.
Lifecycle and packaging
Start or stop the server while Callaba maintains its runtime configuration and the related HLS and DASH output directories.
TWO DEPLOYMENT PATHS
Run the same RTMP product in cloud or on your infrastructure
Prove the source, access rule and output workflow in the environment that matches your operational and networking requirements.
Cloud deployment
Launch Callaba in the cloud when you need a reachable RTMP ingest point quickly and want to validate the complete workflow before sizing fixed infrastructure.
Launch Callaba in the cloudSelf-hosted Linux deployment
Install Callaba on infrastructure you control when port exposure, private networking, storage location or long-running capacity must stay in your environment.
Install Callaba on your Linux serverAUTOMATION, AFTER THE WORKFLOW
Open RTMP Server API documentationAutomate the RTMP server lifecycle when the product setup is proven
The secondary API layer can create, inspect, update, start, stop and remove RTMP server resources. Define the real ingest and access policy in the product first, then integrate those lifecycle actions into your operator tools.
RTMP Server questions
What does Callaba RTMP Server do?
It creates a stable RTMP listener for OBS, software encoders and other publishers, applies the selected stream-key or IP access rule, and makes the accepted feed available to playback, recording and routing workflows in Callaba.
Can I restrict who publishes to the RTMP server?
Yes. The RTMP server supports explicit allowed-stream rules based on stream identifiers or fixed IP addresses. These controls restrict publishers and receivers; they are not a substitute for transport encryption.
Does this RTMP Server page promise RTMPS or TLS termination?
No. The current Callaba RTMP Server product and API contract documented here is for RTMP. Do not assume RTMPS termination. Use an independently verified TLS boundary or choose Callaba SRT Server when encrypted, resilient contribution over the public internet is required.
Do I need the API to use Callaba RTMP Server?
No. Start with the Callaba product workflow and validate a real publisher, access rule and destination. Use the API only when server lifecycle actions need to be automated inside another application or operator panel.
TEST THE REAL FEED
Create the RTMP boundary your production can operate
Launch in the cloud, install on Linux, or inspect the Multiview operator experience before you automate the workflow.