streaming · every product · one page

Streaming at Server Room. Start with the question.

A radio station, a live channel, a library people press play on, one big date, delivery to viewers far from your origin, a channel that needs several renditions, or a whole machine on an unmetered port: each is its own product here, with its own page. This one is the map. It says what each product is for and hands you to the page that owns the details and, where there are any, the plans. Nothing is priced here.

Platforms we run↓ Machines you rent
we run it

Platforms we run. You broadcast; the server is ours.

Five products on machines we own, on our own network. You get a login and an address to send to, not a root password, and the page for each one holds its plans.

Internet radio

Where does my radio station live?

On an Icecast server we own in New York or Bucharest, run from the Radio tab of your dashboard, for Icecast and SHOUTcast encoders alike. On Platinum the radio CDN serves its listeners and its encoder from the nearest of five cities. The radio page holds the three plans and the full comparison of what each one allows, with Auto DJ, syndicated programs, podcasting and podcast ads on the paid two. Two pages beside it describe the servers themselves: what Icecast is and how a station on ours is put together, and the same for SHOUTcast, a DNAS 2.6 server the owner switches the station to from the control panel, on any plan.

Internet radio hosting→ Icecast, the server SHOUTcast, one switch away Radio CDN, on Platinum Podcast hosting, free plan included
Live video

Who receives my live stream, and where does it sit?

Wowza origins we own in New York and Bucharest, announced by our own network. You push RTMP from OBS, vMix or a hardware encoder, viewers play HLS, and the page names every part of that path: the machine, the city, the network, and the published limit of each plan. It also says at exactly which point a channel has outgrown a share of a server and should move to a whole one.

Live video streaming→
Video on demand

Where do my video files go, and how do people play them?

A hosting platform for the files rather than the feed: upload them, organize them, and hand out a player that works on every device, with transcoding and viewing analytics built in. Live is not this; this is the library. The plans are on that page.

Video on demand→
Event streaming

One date, a large audience, and no second take?

Live event streaming for webinars, conferences and town halls: RTMP or SRT in, delivery across more than one region, and an uptime SLA behind it. Built for the day the audience is ten times the usual and the stream cannot stop.

Live event streaming→
Video CDN

I already have an origin; who carries it to the viewers?

A managed video CDN: edge servers on both sides of the Atlantic sit between your origin and the audience, so a stream from one machine reaches viewers far from it, and the delivery is ours to run rather than yours. Traffic and viewer allowances are by plan, on that page.

Video CDN→
you run it

Machines you rent, and the software that goes on them.

When a platform's limit is the problem, the answer is a machine of your own: root, the whole port, and whichever engine you choose. None of these five pages is priced here. The port is priced on the 10 Gbps page and its neighbors, the machine on the price list, and the software on its own page.

Dedicated streaming serverthe whole machine

What does a whole server for streaming get me?

A whole physical machine, an unshared and unmetered port, and your choice of software on it: Wowza, Flussonic, Nimble, Cue, or whatever you install yourself as root. Nobody shares the port and nobody counts the traffic, so it can run at full speed all month. That is the one page here that answers “dedicated streaming server”, and it carries no price: the port and the machine are each priced on their own pages.

Dedicated streaming servers→
Wowza hosting

I hold a Wowza licence. Where does it run?

On a dedicated server built to Wowza Streaming Engine’s published requirements, with your own licence on it: root, an unmetered port, five cities, and the machine priced as the order page opens it. Our own Wowza licence line closes on 15 November 2026; the engine we install and run is Cue. That page walks the day from the order to the first viewer, and sizes the port for your audience.

Wowza hosting→
Transcoding server

One channel in, several renditions out, without buying processors for it?

A dedicated machine whose GPU does the encoding: the channel arrives, the card decodes it once and encodes every profile in hardware, and the processor stays out of it. Flussonic, Wowza and FFmpeg all drive it. The whole machine is yours at one flat monthly figure, which that page states.

Video transcoding servers→
Cue streaming engine

Can I change the engine without changing everything that points at it?

Cue is the live streaming engine we write ourselves and install on your dedicated server. It answers the way Wowza does, the same RTMP sign-in, the same playlist paths, the same REST API that MediaCP drives, and the way Flussonic does for channels imported from it, so encoders, player URLs and the panel stay where they are. The page says why run it instead of Wowza or Flussonic, what it costs, and how it is ordered.

Cue streaming engine→
Cue reseller panel

Can I sell streaming to my own customers from my own server?

A white-label streaming control panel installed on your machine: you sign up resellers and their customers, hand them live channels, TV stations, on-demand libraries and radio stations, and the server enforces every limit you sold. It answers MediaCP’s API, so the billing modules written for MediaCP keep working.

Cue reseller panel→

Not sure which one?

Tell us two things: what goes in (a microphone, an encoder, a folder of files, a channel you already run somewhere else) and who watches (how many, where, and whether it ever stops). That is enough to name the product. The chat answers at any hour, and the guides cover every encoder we have met.

Read the guides