IRL SRT Server

SRT + SRTLA/Belabox bonded live ingest for low-latency IRL streaming on your own VM.

Open sourceSLA: oss-best-effortv3.1.0Image
IRL SRT Server: low-latency SRT / SRTLA ingest gateway
IRL SRT Server: low-latency SRT / SRTLA ingest gateway

IRL SRT Server is an SRT Live Server with SRTLA/Belabox bonding built in, purpose-built for low-latency IRL (in-real-life) live streaming. Publishers ingest either direct SRT (OBS, FFmpeg) or SRTLA bonded cellular (Belabox, Moblin, IRL Pro) that aggregates several modems into one reliable stream, and players pull the live feed back over SRT, all from a server you control.

Key features

  • Direct SRT ingest for OBS / FFmpeg and other standard SRT encoders
  • SRTLA (SRT Link Aggregation) ingest for Belabox / Moblin / IRL Pro bonded cellular uplinks, reliable outdoor streaming over unreliable networks
  • SRT playback / pull for downstream players and re-distribution
  • Optional SRT AES passphrase that encrypts and gates publish and play
  • Stream routing by streamid (publish/live/<key>, play/live/<key>)
  • HTTP stats / health API (/stats, /healthz) for monitoring and NOALBS-style automatic scene switching
  • Runs the source-built, unmodified upstream image; no web console to manage

Use cases

  • IRL streamers bonding multiple 4G/5G modems for a stable outdoor feed
  • A private, low-latency SRT ingest endpoint close to your camera / encoder
  • A regional SRT relay / origin that a CDN or transcoder pulls from

Why run it on the NetActuate edge Placing the SRT ingest in a PoP near where you are streaming shortens the RF-to-server path, cuts round-trip time for SRT's retransmissions, and keeps your ingest, stream keys and stats on infrastructure you control.

Deployed from the NetActuate marketplace, IRL SRT Server boots pre-configured from your seeded values: the publisher, SRTLA and player UDP ports, the stream key and an optional generated SRT passphrase. There is no login; a co-located landing page on the management HTTP port documents the exact ingest URLs and bonding settings, and its /health path is published only after the SRT server confirms it is up and listening. Point a TLS/firewall boundary at it before exposing the stats API on an untrusted network.

Frequently asked questions

How do I deploy IRL SRT Server on NetActuate?

Use the Deploy on NetActuate button to talk to our team. We provision IRL SRT Server on a NetActuate virtual machine in the point of presence you choose, close to your audience. Each deployment runs in the single location you select.

What does it cost to run IRL SRT Server?

IRL SRT Server is open-source software and free to run on the marketplace - you pay only for the NetActuate compute (virtual-machine size and location) it runs on, at standard rates. There are no usage-based software fees.

Where can IRL SRT Server run?

IRL SRT Server can be deployed in any of NetActuate's 45+ points of presence across every continent, so you can place ingest, transcode, delivery and caching close to your contributors and viewers.

Who supports IRL SRT Server?

NetActuate operates and supports the underlying infrastructure - the virtual machine, network and edge platform. The application itself is supported by its upstream open-source project.