Real-time bitrate
Illustrative live view6.2 Mb/sLive · last 60 seconds
CLOUD OR SELF-HOSTED RTMP SERVER
RTMP server hosting for OBS and live production
Receive RTMP feeds, monitor connections and route each stream to recording, playback or multiple destinations.
LIVE RTMP OPERATIONS
See every connection. Control who gets in.
Start with one sender on an unused TCP port, then watch bitrate, connection region and IP address before expanding the workflow.
Region and IP address
See where each publisher or receiver connects from and the network address it uses.
Frankfurt, DE
203.0.113.42Full publisher and receiver control
Allow only approved stream keys or IP addresses, with separate rules for publishers and receivers.
PublisherReceiver
Guest RTMP
Open connections when the workflow calls for it
Enable guest RTMP so publishers and receivers can create their own connections with any stream key—without pre-registering each key.
Guest mode enabledPRODUCT PROOF
The controls an RTMP operator actually needs
Review RTMP bitrate, region and peer IP in the operator UI.
Dedicated RTMP listener
Assign an unused TCP listen port. For the first OBS or encoder sender, create a stream with the Publisher role and use the RTMP URL and stream key configured for it.
Publisher and receiver allowlists
Use stream-key validation when admitting a publisher by its configured identifier. Choose an IP rule for a known, stable host; Receiver access is separate.
Lifecycle and packaging
Start or stop the server while Callaba maintains its runtime configuration and the related HLS and DASH output directories.
Turn a received RTMP stream into a programme when needed
Build a show from incoming RTMP streams instead of forwarding each one separately. Select the received streams in Video Mixer, combine them with prepared media, arrange scenes and mix audio. Check the next scene in Preview before taking it to Program, then publish or record the programme. Keep using direct routing when the incoming feed is already the finished show.
- Receive and check the RTMP stream.
- Choose the received stream as the AV Mixer input.
- Compose it in Preview, then TAKE the prepared scene to Program.
Technical specification
What the product supports, and what to verify
Supported behavior sits beside a practical acceptance check. The installed Callaba interface and the real source, destination, and infrastructure profile remain authoritative.
View technical specifications
| Capability | Supported behavior | Acceptance check |
|---|---|---|
| Dedicated RTMP listener | Assign an unused TCP listen port. For the first OBS or encoder sender, create a stream with the Publisher role and use the RTMP URL and stream key configured for it. | Create an RTMP Server on an unused TCP port, add a Publisher stream, then give OBS or the encoder that stream's RTMP URL and key. Confirm the incoming picture, audio and bitrate before connecting recording, playback or a Restream job. |
| Publisher and receiver allowlists | Use stream-key validation when admitting a publisher by its configured identifier. Choose an IP rule for a known, stable host; Receiver access is separate. | It is the server address, port and stream name that an encoder uses to publish. In Callaba, copy the URL and stream key from the configured Publisher stream; use an allowlist when the sender has a known stream identifier or fixed IP address. |
| Lifecycle and packaging | Start or stop the server while Callaba maintains its runtime configuration and the related HLS and DASH output directories. | 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. |
| HLS or DASH playback | Prepared packaging directories support player delivery workflows. | After Callaba accepts the RTMP feed, configure a Web Player workflow for viewer playback. Test the player URL and its access settings separately; the RTMP Server remains the ingest and access-control layer. |
| Recording | Use the accepted feed as the source for a recording workflow. | Use the accepted feed as the source for a recording workflow. |
| Restream or handoff | Use Restream when the next job is a separately configured destination. | Create an RTMP Server on an unused TCP port, add a Publisher stream, then give OBS or the encoder that stream's RTMP URL and key. Confirm the incoming picture, audio and bitrate before connecting recording, playback or a Restream job. |
Continue in the product
Set it up in Callaba. Then check the full path.
You have seen what the product does. These three guides take you into the exact controls, show what to connect next, and give you a practical check before the workflow goes live.
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
Deploy Callaba in the cloud when you need a reachable RTMP ingest point quickly and want to validate the complete workflow before sizing fixed infrastructure.
Deploy Callaba on AWSSelf-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
How do I set up an RTMP server in Callaba?
Create an RTMP Server on an unused TCP port, add a Publisher stream, then give OBS or the encoder that stream's RTMP URL and key. Confirm the incoming picture, audio and bitrate before connecting recording, playback or a Restream job.
What is an RTMP URL?
It is the server address, port and stream name that an encoder uses to publish. In Callaba, copy the URL and stream key from the configured Publisher stream; use an allowlist when the sender has a known stream identifier or fixed IP address.
How do I use OBS with an RTMP server?
In OBS, set the service to Custom, paste the RTMP URL and stream key from the Callaba Publisher stream, and start one test broadcast. Check the accepted connection and live bitrate in Callaba before an event.
Can an RTMP stream be delivered as HLS?
After Callaba accepts the RTMP feed, configure a Web Player workflow for viewer playback. Test the player URL and its access settings separately; the RTMP Server remains the ingest and access-control layer.