The live streaming and broadcast server you run yourself. One program on one Linux server takes your streams in, prepares them for every screen, records them and sends them everywhere they need to go, with a dashboard your whole team can use.
A stream is available on every output the moment it arrives, however it came in: sent over SRT, it plays in the browser, in VLC and on a set-top box with nothing to set up.
Each feature in detail: see all features.
The same program fits a church streaming on Sundays and an operator feeding set-top boxes, because every part is switched on only when you need it.
Weekly services on your own website and on Facebook and YouTube at once, recorded for later.
Conferences, concerts, weddings and funerals, with a backup encoder and ticketed links when you need them.
A channel on air all day from your own programmes, with live shows and adaptive quality.
Lessons and graduations for students only, with signed links that expire.
Many clients on one server, each with their own channel, key and account.
Town halls and announcements for staff, kept private and off public platforms.
Channels taken in over UDP, SRT or RTP and sent to set-top boxes, unicast or multicast.
Constant-bitrate SD and HD transport streams with channel names, for multiplexers and partners.
How each one comes together: see the solutions.
One command installs it on Ubuntu or Debian, gets an HTTPS certificate and starts it as a service. Re-running it upgrades, with a backup first.
Install guide →A ready image for Intel/AMD and ARM servers, with Compose files to copy, including one with a web server in front.
Docker setup →We run the server and keep it updated; your team signs in and streams. Ask us about hosting in your region.
Ask about managed hosting →Unda is not tied to one encoder or player. See what works with Unda for the equipment we have tested.
| Protocol | In | Out |
|---|---|---|
| RTMP / RTMPS | OBS, vMix, ffmpeg, most encoders and phone apps | Players (VLC, OBS, vMix); YouTube, Facebook and other platforms |
| SRT | Contribution over the internet, encrypted | Players that pull over SRT; other servers |
| HLS | — | Browsers, apps and smart TVs, with adaptive bitrate |
| MPEG-DASH | — | DASH players, with adaptive bitrate |
| UDP / RTP | Encoders, receivers and IPTV headends; multicast | Set-top boxes, multiplexers, partners; with FEC on RTP |
| RIST | Contribution with packet recovery | Partners and other servers |
| MPTS | Multi-channel feeds: choose the channels | Several channels bundled in one transport stream |
Passing streams through costs very little. What we measured on a test machine:
Making extra qualities is the expensive part: plan about one CPU core per stream with adaptive bitrate, or use a GPU.
| A typical server | |
|---|---|
| Processor | 4 cores |
| Memory | 8 GB |
| Upload | 100 Mb/s or more: about 25 viewers at 3 Mb/s |
| System | Ubuntu or Debian, or anything that runs Docker |
| Name | A domain name pointing at the server, for HTTPS |
Packages differ in live streams, team members and tools. Every one has unlimited viewers.