Delay changes the viewing experience
Your audience needs to see goals, finishes and other decisive moments close to when they happen, rather than following a feed far behind the action.
When viewers need to follow the action close to live, delay, audience access and rising hosted-platform charges all affect the decision. CreekX Media Server runs on infrastructure you control. Send a live programme feed from a browser, encoder or camera, then deliver it over WebRTC, low-latency HLS or HLS to viewers on the web and phones.
Your audience needs to see goals, finishes and other decisive moments close to when they happen, rather than following a feed far behind the action.
You stream regularly and want the software subscription tied to your server, rather than a hosted bill that increases with viewing time and audience traffic.
The stream is intended for members, ticket holders, staff or another approved audience, so public links are not enough.
You need a server that can receive concurrent feeds from encoders or cameras and deliver them in formats suitable for browsers and mobile viewers. Hardware and network capacity must be sized for the production.
Send video from an encoder, browser or camera using RTMP, SRT, RTSP or WebRTC ingest. A production using several cameras can send multiple live sources within the plan limit and the capacity of its server.
CreekX can deliver WebRTC for viewing close to live, low-latency HLS when a short delay is acceptable, and standard HLS for broader device delivery. Adaptive qualities can be created from the source when needed, subject to server capacity.
Use signed watch links, one-time viewer tokens, IP allow-lists or an approval check from your own system. Viewer logs record when a viewer connected and the device and IP address used.
Record the live stream on your server, keep video in the library and use CreekX 24/7 Channels when you want scheduled sports replays or venue programming to continue between live events.
CreekX is installed on your Ubuntu server. The Pro plan is $99 per server per month or $999 per server per year.
In a first-party test on 13 October 2026, CreekX 2026.10.13 measured a median delay of 0.49 seconds for WebRTC, with a worst result of 0.68 seconds. Low-latency HLS measured 1.23-1.28 seconds at the median and 1.40 seconds at worst. Standard HLS measured 3.4-3.8 seconds at the median and 4.4 seconds at worst. The test used the standard one-line installer on an Ubuntu 24.04 cloud server with 4 vCPU, 8 GB memory, a 100 GB NVMe disk and about 890 Mbit/s upload bandwidth. The source was a real 1080p, 25 fps H.264 clip at 5 Mbit/s, sent from OBS and viewed on a laptop over the local network. Each step ran for 60 seconds. These are product measurements under the stated conditions, not results from a sports customer deployment or a promise for each viewer.
CreekX has no telemetry and can run with an offline licence and offline installation package supplied through sales. Video and the installed product’s operational account data remain on the customer-controlled server during local operation. Website and sales enquiries are separate. Enabling an off-site backup, external storage, restream destination or another outbound integration creates a corresponding outbound data path. Recorded video and library files are not encrypted by CreekX on the customer’s disks; use server-level disk encryption when encryption at rest is required. Viewer-security features have been checked through CreekX automated tests, but no formal third-party security certification or assessment has been completed.
The 14-day Media Server trial is available without a credit card. It includes the Media Server feature set with trial limits of five 24/7 channels, five restream destinations per stream and 500 library videos. Installation requires an internet connection. At the end of the trial, the workspace becomes read-only and its content is retained.
Contact CreekX first if the deployment must be fully offline or air-gapped, will use several servers or more than 50 concurrent live streams, expects thousands of viewers, forms part of a tender, or needs installation, training or Enterprise support. CreekX currently operates one server per installation, so the team should check hardware, network capacity and product fit for a large audience before the trial.
CreekX delivers to browsers, phones and smart TVs using WebRTC, LL-HLS or HLS. The right delivery format depends on the acceptable delay, device mix and network conditions.
There is no single answer for every deployment. Audience capacity depends mainly on the server’s network connection, the video bitrate and the qualities being delivered. CreekX sizes large deployments with the buyer before installation.
Yes. Your system can approve each viewer before playback. CreekX also supports signed watch links, one-time tokens, IP rules and viewer connection logs.
Existing live streams and 24/7 channels continue, recordings remain playable and customer data are not deleted. Updates and email support stop. After a 30-day grace period, new channels and newly enabled features are restricted until renewal.
The standard paid licence includes the self-install kit, documentation and email assistance if installation gets stuck. Done-for-you installation and remote operator or administrator training are paid or Enterprise services.
If your team can evaluate Media Server on Ubuntu, begin with the 14-day trial. For an offline site, a large audience, a tender or a production that needs assisted setup, share what you plan to stream, the number of live sources and viewers, the acceptable delay and the server details you already know. If you are not sure about any of those details, say so and CreekX can help identify what needs to be sized.