Most people who go looking for RTMP server hosting already know what they want: a box that accepts an encoder push, fans it out to a few destinations, and hands viewers an HLS playlist — without a shared platform sitting between them and their bitrate. The catch is that standing that up from a bare Linux image means an evening of compiling modules, editing nginx.conf, and guessing at buffer sizes. This is a note from our rack on how we short-circuit that: a streaming VPS with the whole ingest-and-package stack pre-installed, 10 Gbps unmetered underneath it, and root so you can tune whatever we picked wrong for your use case.
What "RTMP server hosting" actually means
RTMP is still the workhorse ingest protocol — it's what OBS, vMix, and hardware encoders speak by default over port 1935. An RTMP server's job is narrow: terminate that push, then do something useful with it. In practice "something useful" is one of three things, often all at once. Relay the stream on to other RTMP endpoints (multistreaming). Repackage it into HLS or LL-HLS so browsers and phones can play it without a plugin. Or transcode it into a bitrate ladder so viewers on bad connections still get a picture. Hosting the server yourself, instead of renting a slot on a SaaS streaming platform, means you own the ingest URL, the stream keys, the retention, and the egress bill.
The reason self-hosting has a reputation for pain isn't the software — Nginx-RTMP, MediaMTX and friends are solid — it's the assembly. You need the module built against the right Nginx version, an HLS output directory with sane fragment settings, a firewall that lets 1935 and 443 through, and enough bandwidth headroom that a restream to five destinations doesn't saturate the link. Get one of those wrong and the stream stutters under load, which is exactly when you can't afford it to.
The stack, already on the box
Our streaming VPS ships with the ingest stack pre-installed rather than leaving you to compile it: Nginx-RTMP, MediaMTX, MistServer, and Restreamer are all on the image, alongside OBS and Owncast. That covers the protocol matrix you'd otherwise stitch together by hand — RTMP, RTMPS, SRT, HLS and LL-HLS all supported out of the box. So a plain nginx rtmp server setup on a VPS becomes "point your encoder at the ingest URL and check the playlist," not "spend Saturday reading module docs."
Concretely, that means:
- Ingest — push RTMP/RTMPS from OBS or an encoder, or SRT if you're on a lossy uplink and want the error correction.
- Restream — fan a single push out to multiple destinations from one host, so your uplink carries one stream and the box does the duplication. That's the multistream VPS pattern without paying a per-destination SaaS fee.
- Package HLS — Nginx-RTMP or MediaMTX writes the HLS/LL-HLS segments, and you serve them straight off the same machine or front them with a cache.
Because you have root access, none of this is a locked appliance. Swap the HLS fragment length, add an auth hook on on_publish, drop in a transcode profile, or replace our default config wholesale — it's your kernel and your nginx.conf.
Why bandwidth is the whole game
Streaming is the one workload where the network matters more than the CPU. A restream to five destinations at 6 Mbps each is 30 Mbps of egress off a single 6 Mbps ingest — and HLS viewers add to that linearly. On a metered or oversold link, that's where the buffering starts. Every streaming VPS tier runs on 10 Gbps unmetered symmetric connectivity, so the restream fan-out and the HLS viewer pull both draw from the same fat, uncapped pipe. Symmetric matters here: ingest is upload-heavy from the encoder's side and download-heavy from the viewer's, and you want headroom in both directions.
That link doesn't sit on rented transit either. We run our own AS60982 across 13 European POPs with 15 IXs and 34+ carriers on a 400 Gbps DWDM ring, which keeps intra-EU latency under 5 ms — the difference between a low-latency HLS wall clock that holds and one that drifts. And every box carries free 1 Tbps DDoS mitigation, which for a public ingest endpoint is not optional insurance; an exposed RTMP port is a target.
Picking a tier
Sizing an RTMP host is mostly about whether you transcode. Pure relay and HLS packaging is light on CPU and leans on the network — the entry tier handles it. The moment you add a transcode ladder (one input, multiple output bitrates), CPU becomes the constraint and you'll want more vCPUs.
| Workload | What it needs | Where to start |
|---|---|---|
| Single ingest → HLS, no transcode | Bandwidth, a little RAM | Entry streaming tier, EUR 9.99/mo |
| Restream / multistream to several endpoints | Bandwidth headroom | Entry to mid streaming tier |
| Transcode ladder (multi-bitrate output) | vCPUs + RAM | Higher streaming tiers (up to 32 GB / 12 vCPU / 500 GB) |
The streaming line runs from EUR 9.99/mo up to EUR 139.99/mo, all on NVMe with the same 10 Gbps unmetered link. If your project is more general compute with occasional streaming, a plain hourly VPS can run the same stack — but the streaming tiers exist because 10 Gbps and the pre-installed toolchain are what streaming actually needs.
How Noded Can Help
We built the streaming VPS because we were tired of watching customers lose a weekend to Nginx-RTMP compilation before they'd streamed a single frame. Our image hands you Nginx-RTMP, MediaMTX, MistServer and Restreamer already installed, on a 10 Gbps unmetered box with root, deployed in a median of 47 seconds. Pick a tier, push your first stream, and tune from there — the config is yours to own. The streaming VPS page lists every tier from EUR 9.99/mo up. And if your workload is mostly general compute with the odd broadcast, our hourly VPS line runs the same stack and bills to the second, so a spin-up to test a broadcast only costs for the hours it's up.
FAQ
Do I need to install Nginx-RTMP myself?
No. The streaming VPS ships with Nginx-RTMP, MediaMTX, MistServer and Restreamer pre-installed. You point your encoder at the ingest URL and check the HLS playlist — no compiling modules or editing config to get a first stream running. Because you have root, you can still customise or replace any of it.
Can one server restream to multiple destinations?
Yes. Restreaming (multistreaming) is the core relay pattern — a single encoder push is fanned out to several RTMP endpoints from one host, so your uplink only carries one stream. The 10 Gbps unmetered symmetric link gives the egress headroom to do it without saturating the pipe.
Which streaming protocols are supported?
RTMP, RTMPS, SRT, HLS and LL-HLS are all supported out of the box. RTMP/RTMPS for standard encoder ingest, SRT when your uplink is lossy and you want error correction, and HLS/LL-HLS for browser and mobile playback.
How much does RTMP server hosting cost?
The streaming VPS line starts at EUR 9.99/mo for the entry tier and runs up to EUR 139.99/mo for the largest, all on NVMe with a 10 Gbps unmetered link. If you'd rather pay by the hour, the same stack runs on our hourly VPS line, which is billed to the second.
What size VPS do I need for RTMP?
Pure ingest and HLS packaging with no transcode is bandwidth-bound and runs comfortably on the entry tier. If you add a transcode ladder — one input, several output bitrates — CPU becomes the limit, so step up to a higher tier with more vCPUs and RAM.