Cue Media Server · built by Server Room · licensed per machine

Cue streaming engine. Live video in over any protocol, out to every screen, from your own server.

Cue is the live streaming engine we write ourselves and install on your dedicated server. Encoders publish over RTMP, SRT, WebRTC or RTSP; viewers play HLS, Low-Latency HLS, DASH, or WebRTC under a second behind live. Bitrate ladders on NVIDIA or Quick Sync, DVR, live captions, FairPlay, Widevine and PlayReady DRM, server-side ads and a full IPTV service are all in the one program.

RTMP, SRT, WebRTC, RTSP and MPEG-TS inHLS, DASH, WebRTC, RTMP, SRT, RTSP outUbuntu, Debian, AlmaLinux, Rocky Linux, RHEL, CentOS, Windows Server$195/mo per server, $29.99 setup
Protocols

The patch bay

Every input can feed every output: a stream published once over SRT plays as HLS, DASH, WebRTC, RTMP and RTSP at the same moment, and a multicast feed from a head-end comes out as HLS for browsers.

In

  • RTMP / RTMPS:1935publish; Adobe sign-in or a password in the stream key; RTMPS on the TLS port
  • SRT:9998/udppublish; the stream ID names application, stream, user and password; AES keyed by the publishing password
  • WebRTC (WHIP)/app/stream/whippublish with the publishing password as the bearer token; all media on 8189, UDP or TCP
  • RTSP:554publish over TCP with Basic sign-in or ?password=
  • RTSP / RTSPS pullrtsp://IP cameras, with the camera’s own login
  • SRT pullsrt://Cue calls the sender; encrypted feeds too
  • MPEG-TSudp:// · tshttp://unicast, multicast on a named interface (bare or RTP-wrapped), or over HTTP
  • HLS pullhls://re-serve another origin, CDN-fronted ones included
  • RTMP pullrtmp://mirror another server, with its sign-in

Out

  • HLS/app/stream/playlist.m3u8MPEG-TS or fMP4/CMAF segments; Low-Latency HLS over HTTP/2
  • MPEG-DASHmanifest.mpd · index.mpdbuilt on the same CMAF segments as fMP4 HLS
  • WebRTC (WHEP)/app/stream/whepunder a second behind live; AAC sound is turned into Opus while WebRTC viewers watch
  • RTMP:1935play, with a picture cache for a fast start
  • SRTm=requestany stream as MPEG-TS on the SRT port
  • RTSP:554TCP interleaved; players that ask for UDP retry over TCP
  • MPEG-TS/app/stream/mpegtsover HTTP, or pushed to a UDP multicast group
  • Thumbnailthumbnail.jpgthe latest frame of every live stream, refreshed every 5 s

These are Cue’s default ports.

Inside the engine

What the engine does, group by group

Open a group for the detail. Everything listed here is built and has passed its acceptance test; anything only partly built is left out rather than half-claimed.

01Sources that fail over, encoders that come back
  • A pulled source can carry up to four backup addresses. Cue reads the first that answers, and goes back to a better one when it returns (checked every 30 s).
  • Viewers keep the same stream through a drop of up to 10 s: the next connection continues it with its timestamps moved on, so players do not restart.
  • An encoder that reconnects with valid credentials takes its stream name back at once, instead of waiting for the dead connection to time out.
02Adaptive bitrate on the GPU
  • One FFmpeg per live stream, fed by the engine, encodes the ladder on an NVIDIA card (NVENC) or on Intel Quick Sync through VA-API; without a usable GPU it falls back to libx264 on the processor.
  • The source is copied as the top rendition and only smaller renditions are made; keyframes are forced where the source has them, so every rendition cuts at the same moment.
  • Presets HD (720p, 480p, 360p), SD and Mobile from the interface; up to five custom renditions through the API.
  • The master playlist advertises the source at its measured bitrate, so players do not mistake it for the cheapest rendition.
  • Measured on an HPE ProLiant m710x: seven 1080p30 HD ladders in real time at once, with the processor under 35 %. Plan on six.
03Picture, sound and languages
  • A logo on the renditions: a PNG in the corner you choose, sized as a share of the picture’s height, with an opacity. On the GPU where the FFmpeg build can, on the processor otherwise.
  • Deinterlacing for interlaced sources, a volume change in dB, and a choice of which of the source’s audio tracks the renditions carry.
  • These apply to the adaptive ladder that HLS and DASH viewers watch; RTMP, SRT, RTSP and WebRTC carry the stream as it arrives.
  • A source with several audio tracks is offered with each one as a named language in fMP4 HLS, Low-Latency HLS and DASH, and viewers switch between them; MPEG-TS HLS keeps one audio track.
  • Live captions: CEA-608 carried in the video and DVB teletext pages become WebVTT subtitle renditions in HLS, which viewers switch on in the player.
04Rewind, time-shift and MP4
  • An application with DVR lets viewers go back through its window, from a fixed start time or a set distance behind live.
  • Any stretch downloads as an MP4 with its index first, remuxed without re-encoding and cut to the second you asked for (from the keyframe before it).
  • Clips saved from the interface land in the application’s media library.
05Who may watch, who may publish
  • Publishing passwords per application; Cue keeps only a hash of each.
  • HMAC-signed links that expire, optionally bound to the viewer’s address. A viewer already watching is not cut off when a link expires.
  • Allowed and blocked addresses, and the sites allowed to embed the player (by Referer).
  • Your own authorization backend, asked before a viewer starts or an encoder publishes, with sessions per user capped across protocols.
  • A viewer cap per application, counted across HLS, RTMP and the other outputs.
  • FairPlay, Widevine and PlayReady from one cbcs CMAF copy, a key per key id, on your own Apple, Google and PlayReady credentials. FairPlay and Widevine licences are answered by the server itself; PlayReady challenges arrive at /drm/playready and go on to your PlayReady licence server, which reads its keys from an authenticated CPIX 2.3 export encrypted to your certificate. All three pass the channel’s own access rules first.
  • AES-128 or SAMPLE-AES encrypted HLS, with keys that rotate while the stream runs.
06Ad breaks and events
  • SCTE-35 cues, splice_insert or time_signal, become HLS ad markers whether they arrive over SRT or MPEG-TS or inside an RTMP feed (onCuePoint and the other data messages encoders use, base64 or hex): CUE-OUT/CUE-IN, EXT-X-DATERANGE, both, or off, per application, in the source and every rendition.
  • Segments cut on the splice point (playback.hls.splice_segments, on by default wherever ad markers are): a break starts on a fresh segment in MPEG-TS, fMP4 and Low-Latency HLS, and in the MPEG-TS renditions of the ladder.
  • No cue in the feed? POST /api/v1/channels/<key>/cues with type out, in or cancel, a duration, auto_return and an event_id starts, ends or calls off a break from your scheduler.
  • Server-side ad insertion: at each break Cue asks your VAST or VMAP ad server, conditions every creative for each rendition of the ladder (frame size, codec, bitrate, frame rate, sound, segment length) and splices it into every HLS rendition and into DASH as ad periods. One decision per viewer and break, so a player that changes quality mid-ad stays in the same ad; ads stay clear inside an encrypted stream.
  • Impression, start, quartile and complete beacons fire once per viewer and ad, whichever rendition or protocol carried it.
  • Webhooks for streams and sources opening and closing, refused publishes, recordings starting and finishing. Signed, up to five receivers per application, kept and sent again until each answers.
07Delivery details that save a support ticket
  • RTMP and HTTP on one port.
  • Low-Latency DASH from the same CMAF parts Low-Latency HLS uses: availabilityTimeOffset in the manifest and the open segment sent chunked as it grows.
  • WebRTC both ways: WHIP publishing, with the publishing password as the bearer token, and WHEP playback under a second behind live. All WebRTC media uses one port, 8189, over UDP or TCP for networks that block UDP.
  • A free Let’s Encrypt certificate for the server’s name, switched on in the interface once the name points at the server: HTTPS playback on 443 and the interface on 8443, renewed by itself. The bare IP address keeps a self-signed certificate.
  • CORS headers on every playlist and segment, so web players on other domains just work.
  • Segments are served without a session, so a CDN in front can cache them; playlists are sent uncached.
  • MP3 audio carried in MPEG-TS HLS, for encoders that still send it.
08An on-demand library, not just a folder of files
  • Renditions named <id>~<N>p.mp4 are served as one adaptive master, lowest bandwidth first, each with BANDWIDTH, RESOLUTION, CODECS and FRAME-RATE.
  • Subtitle files named <id>.cc.<lang>.vtt join it as an EXT-X-MEDIA SUBTITLES group, each language under its own name.
  • A poster.jpg, a preview strip (sprite.jpg with sprite.vtt) and chapters.vtt are picked up for the player.
  • Downloads at <file>/download (with ?name= for the saved name), and plain progressive MP4 at <file>.mp4/progressive.mp4 with Range requests.
09An IPTV service on the same server
  • Subscriber lines by username and password or MAC address, with an expiry, connections at once, allowed outputs and trials; bouquets of live channels, films and series.
  • The player_api.php and panel_api.php calls IPTV player apps make, M3U and M3U_plus playlists, and XMLTV from your EPG.
  • Line addresses in MPEG-TS and HLS, catch-up TV at the timeshift addresses those apps use, Enigma2 bouquets with an install script, and the Stalker portal API that MAG boxes sign in to.
  • Who is watching, disconnects, an activity log and banned addresses; resellers who buy lines with credits; the whole IPTV setup backed up and restored as one file.
Wowza alternative, Flussonic alternative

Everything Wowza and Flussonic do, then five points where only Cue has them all

Twenty-eight capabilities are common ground: all three engines have them, so they sit lower down. The five rows above them are where the engines part ways, and only Cue answers yes to every one. The Wowza and Flussonic columns come from each vendor’s own documentation for Wowza Streaming Engine 4.11.3 and Flussonic Media Server 26.09, read in September and October 2026. A dash means the product doesn’t set out to do that.

CapabilityWowza 4.11Flussonic 26.09Cue
Where they part ways
Windows Server as well as Linux Flussonic: Linux packages, Windows only through Docker · Cue: Windows Server 2012 R2, 2019, 2022 and 2025Yes— not built inYes
A full IPTV service: subscriber lines with expiry and device limits, bouquets, the player API that IPTV apps speak, M3U and XMLTV, catch-up, Enigma2 and the MAG portal Flussonic: users, packages and M3U playlists in its IPTV plugin; MAG boxes through separate middleware— not built inBasicYes
Server-side ad insertion from VAST and VMAP, every rendition and DASH Wowza: through ad partners · Cue: each creative conditioned per rendition, DASH ad periods, one beacon per viewerPartnersYesYes
One native program, with no Java runtime to size or tune— runs on JavaYesYes
A reseller panel for selling streaming accounts to your own customers Cue: the Cue Reseller Panel, licensed on its own— not built in— not built inYes
Getting video in
RTMP and RTMPS publishing, a password per applicationYesYesYes
SRT publishing, encrypted, and SRT pullYesYesYes
WebRTC publishing (WHIP)YesYesYes
RTSP publishing and IP-camera pullYesYesYes
MPEG-TS over UDP, multicast includedYesYesYes
Relaying another server over HLS or RTMPYesYesYes
Backup sources, switched automaticallyYesYesYes
Getting video out
HLS in MPEG-TS, fMP4/CMAF and Low-Latency HLSYesYesYes
WebRTC playback (WHEP), under a second behind liveYesYesYes
MPEG-DASHYesYesYes
RTMP, SRT, RTSP and MPEG-TS playbackYesYesYes
Several audio languages, switched by the viewerYesYesYes
A viewer cap per applicationYesYesYes
On-demand files as an adaptive group, with WebVTT subtitlesYesYesYes
Working on the stream
Adaptive-bitrate ladder NVENC, Quick Sync or CPUYesYesYes
A logo on the pictureYesYesYes
Thumbnails of live streamsYesYesYes
DVR rewind and time-shiftYesYesYes
MP4 clips and exportsYesYesYes
Live captions, CEA-608 and teletext, as WebVTT subtitlesYesYesYes
SCTE-35 in, ad markers in HLSYesYesYes
Access and events
FairPlay, Widevine and PlayReady DRM, one cbcs copy for all three Cue: on your own Apple, Google and PlayReady credentials; every licence request passes the channel’s access rulesYesYesYes
AES-128 and SAMPLE-AES encrypted HLS, rotating keysYesYesYes
Signed playback linksYesYesYes
Asking your own backend who may watch or publishYesYesYes
Address and site restrictions Cue: countries through the Cue Reseller PanelYesYesYes
HTTPS with a certificate for the server’s name Cue: a free Let’s Encrypt certificate, switched on in the interfaceYesYesYes
WebhooksYesYesYes
Price and delivery

What it costs, and how it reaches your server

Cue is its own line on the invoice, beside the server and never folded into it. The figures come from the same catalogue the checkout bills from. It is billed at its monthly price on every cycle: a longer term lowers the server’s lines, not Cue’s.

Cue Media Server, per month$195
Setup, once$29.99
Licensed toOne machine, bound when it first activates
On a 3, 6 or 12-month term$195 × the months: software takes no term discount
The line it was built onHPE ProLiant m710x, from $62.58/mo as Intel Xeon E3-1585L v5 Quad Core 3.00 Ghz · 32 GB DDR4 · 1 × NVMe-SSD 240 GB · 1 Gbps
Together, from$257.58/mo before tax
CitiesNew York, Bucharest, San Francisco, Amsterdam and Miami
  1. step 1 · order

    Configure the server

    The button opens the m710x configurator with Cue Media Server already under Software. The other lines that sell it are listed below; on any of them it sits under Software → Streaming solutions once a system it installs on is chosen: Ubuntu 20.04 or later, Debian 11 or later, AlmaLinux 8 or later and Rocky Linux 9 or later, or Windows Server 2012 R2, 2019, 2022 or 2025 at the same price. Cue has no ARM build, so our ARM machines do not offer it.

  2. step 2 · install

    Installed and licensed for you

    Once the operating system is on — for a ready server, at handover — Cue goes on with a license key issued for that machine. On Linux we run Cue’s signed installer; on Windows Server the server fetches and installs it by itself the first time Windows starts, FFmpeg included. The key binds to the machine the first time it activates.

  3. step 3 · sign in

    Open the interface

    The interface answers on port 8443 of your server, and the server’s page in your dashboard shows the license and its state. The machine is yours — root on Linux, administrator on Windows — so cue admin reset-password <name> sets a new interface password whenever you need one.

Configure a server with Cue

Your own hardware

A Cue licence for a server you already run

Cue does not have to run on our machines. The licence is sold on its own for a box at any host: you run the installer as root, and the key binds to that machine the first time Cue activates. There is no setup fee, because the install is yours.

Cue Media Server, per month$195 · order
Cue Media Server + Cue Reseller Panel, per month$244 · order
Cue Reseller Panel, alone, per month$49 · order
Setup, onceNone: you install it
On a 3, 6 or 12-month termThe monthly figure × the months: software takes no term discount

Bought alone, the panel runs SHOUTcast and Icecast radio stations, and live channels on Wowza Streaming Engine; TV stations and video on demand need Cue Media Server on the same machine.

  1. step 1 · license

    Buy the key

    Pick the engine, the panel or both, and a billing cycle. The key appears on the account’s dashboard page once the payment clears.

  2. step 2 · install

    Run the installer

    On Linux, as root: curl -fsSL -o install.sh https://releases.servcast.net/cue/install.sh, then CUE_LICENSE=<key> sh install.sh — Ubuntu 18.04 or later, Debian 11 or later, AlmaLinux, Rocky Linux or RHEL 8 or later, CentOS 7 or 8. On Windows Server 2012 R2, 2019, 2022 or 2025, in an elevated PowerShell: [Net.ServicePointManager]::SecurityProtocol = 'Tls12'; irm https://releases.servcast.net/cue/install.ps1 -OutFile install.ps1, then .\install.ps1 -License <key> -FetchFFmpeg (on 2012 R2, install Windows update KB2999226 first: FFmpeg needs it). Either one verifies our signed release first. x86-64 only.

  3. step 3 · sign in

    Open port 8443

    The installer prints the interface’s first sign-in once. The dashboard shows the key and whether the machine has activated it.

Buy a Cue licence

For streaming resellers

Cue Reseller Panel

A control panel for selling streaming, built into Cue, where your own customers sign in to their live, on-demand, TV and radio services. It is licensed per machine, like the engine.

  • Ordered with Cue Media Server or Wowza Streaming Engine, the panel and the engine carry one setup fee between them.
  • On its own it can be ordered without an engine, and then runs SHOUTcast and Icecast radio stations.
  • For a machine you run elsewhere, the panel is also licensed on its own, with no setup fee. On its own it runs SHOUTcast and Icecast radio stations, and live channels on Wowza Streaming Engine; TV and on-demand services need Cue Media Server beside it.
Cue Reseller Panel, per month$49
With Cue Media Server$244/mo ($195 + $49), $29.99 setup once for the two
On its own$49/mo, $29.99 setup once

Configure a server with Cue Media Server and the panel

Every feature of the panel
Before you order

Questions engineers ask first

How does Cue compare with Wowza and Flussonic?

On the core of a streaming engine the three are level: RTMP, SRT, WebRTC and RTSP in; HLS, DASH and WebRTC out; ladders, DVR, DRM, captions, signed links and webhooks. Beyond that, Cue runs on Windows Server, which Flussonic does not; inserts ads without an ad partner and needs no Java runtime, which Wowza cannot say; and carries a full IPTV service and a reseller panel, which neither has. The comparison table above has every row.

Which systems does it install on?

Linux: Ubuntu 18.04 or later, Debian 11 or later, AlmaLinux, Rocky Linux and RHEL 8 or later, and CentOS 7 and 8. Windows: Windows Server 2012 R2, 2019, 2022 and 2025, installed with one PowerShell command. The installer verifies our signed release on every one of them, older systems included. Adaptive bitrate needs FFmpeg: on Windows the installer can fetch the build we test with (on 2012 R2 it needs Windows update KB2999226), and on Ubuntu 18.04 and CentOS 7 and 8, whose own FFmpeg is too old or missing, a newer one is installed beside it; everything else works the same everywhere.

How does the per-machine license behave?

The key binds to the machine it first activates on; a reinstall of that machine keeps it. Cue then holds a signed license valid for seven days and renews it every twelve hours, so an outage on our side never stops your streams early. Without a valid license — the account closed, or the key copied to another machine — Cue stops publishing and playing, and the interface stays up to take a key.

Does a 12-month term make Cue cheaper?

No. Software on our servers is billed at its monthly price times the months on every cycle; the longer-term discount applies to the server’s own lines.

How do updates arrive?

Every release is signed with our release key, and the server checks each file against that signature before it runs the release’s installer. The interface tells you when a new version is out and installs it when you press Install; a release altered after signing is refused.

Other pages that answer the next question