News and Media Streaming

Live coverage on your own site, and everywhere else at once

Publishers want their live coverage on their own pages, where the audience and the ads are theirs. CreekX plays it on your site, sends it to social platforms at the same time and keeps a 24/7 channel running between events.

01triggers

When platforms own your audience

A publisher’s best live moments are a verdict, a result, a storm. When the live sits only on a social platform, the readers, the comments, the replay and the advertising around it sit there too, and the article page carries an embed that sends people away.

Viewers watch on someone else’s site

Embed the live player on your own pages. The player and the video come from your server, so the reader stays on the article, beside your own advertising and subscription prompts.

You still need social reach

Restream to several platforms at once. creekX copies the same live to YouTube, Facebook or any RTMP or SRT destination without re-encoding, up to 10 per stream on the Pro plan.

Airtime between events

Run a 24/7 channel from your video library, so a “watch live” page is never empty. A live can take the channel over when news breaks. Each channel used 4 to 6% of a core in our tests.

A television outside broadcast truck parked at an event with its side panels open
A truck like this once was the only way to go live from the field. A phone and an SRT app now do the contribution; the question left is where the audience watches.
02process

How it works

Bring in feeds

From reporters’ encoders over SRT, or from the studio. SRT re-sends lost packets, which is what a crowded mobile network outside a courthouse needs. Give a freelancer a guest key that expires instead of your own stream key.

Publish everywhere

Your site plus platforms at once. Tick the platforms on the stream before going live; each shows whether it is receiving. Steps: YouTube, Facebook and more at once.

Keep it running

Recordings go to the library and into 24/7 channels. The replay is ready when the live ends, on your own disks, with captions made on your server.

Diagram: a reporter’s phone sends SRT and a studio sends RTMP to a publisher’s creekX server, which plays the live on the article page, restreams to platforms and runs a 24/7 channel
The publisher’s path. Delay figures: creekX 2026.10.13, 1080p source, measured on a local network. Conditions are on the benchmarks page.
03deliverables

What you get

  • A live player on your own pages
  • Restreaming to up to 10 platforms per stream
  • 24/7 channels from your library, up to 10 on Pro
  • Recordings and video on demand on your own disks
  • Captions and search made on your server (accuracy not yet measured)
  • A REST API and webhooks to start, stop and list lives from your CMS
04protocol fit

Which protocol from the field to the reader

Protocol choices for a publisher. Delay figures are creekX’s own measurements on a local network.
LegProtocolMeasured delayWhy
Reporter to server on mobile dataSRT with AESThe SRT latency you setRe-sends lost packets; encrypted in transit.
Studio gallery to serverRTMP or SRTNot measured separatelyA steady wired line.
Server to readers on the articleLow-latency HLS1.23-1.28 s median, 1.40 s worstHTTPS in every browser, and cacheable by a CDN.
Server to a live blog or results deskWebRTC0.49 s median, 0.68 s worstWhen the video must match live text or data.
Server to social platformsRTMP restreamThe platform’s own delayReach, without a second encoder.
05sizing and cost

A sizing example: one live desk and a rolling channel

From our tests on a 4 vCPU, 8 GB server: 400 low-latency HLS viewers of a 1080p stream used 0.80 of a core; a 24/7 channel used 4 to 6% of a core in development.

  • Lives: three at once (studio and two reporters) at 1080p and 5 Mbit/s is 15 Mbit/s in.
  • Channel: one rolling channel, 4 to 6% of a core. Channel capacity per server has not been load-tested.
  • Readers: direct from the server, about 350 at 2.5 Mbit/s on 890 Mbit/s of upload. Beyond that the CDN carries HLS and the server feeds the CDN.
  • Restreams: each destination is one more outgoing copy of the feed, 5 Mbit/s each.
  • Recording: 2.3 GB an hour per live at 5 Mbit/s. Four hours of lives a day is about 9 GB a day, about 3.4 TB a year.
  • Licence: Media Server Pro is USD 99 per server each month or USD 999 a year. No charge per viewer or per hour, which is the difference from hosted video priced by minutes watched.

A cost comparison is worked through in self-hosted and cloud streaming cost.

06First-party evidence

Measured delivery delay, with the test conditions

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 customer deployment or a promise for each viewer.

07honest limits

What creekX does not do for publishers

  • No DRM, paywall or ad insertion.
  • No newsroom, graphics, switching or editing tools.
  • No measured large-audience result; a CDN is required beyond one port and must be rehearsed.
  • No MPEG-DASH output; delivery is WebRTC, low-latency HLS and HLS.
  • Caption accuracy is unmeasured, so read captions before publishing.
08Scope & limitations

Know where the security and data boundary sits

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.

09buyer fit

Start with a trial or speak to CreekX first

Start the trial yourself

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. Your content is kept when the trial ends. Add a paid licence to continue using licensed features and creating channels after the trial and any applicable licence grace period.

Speak to CreekX before installing

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.

10faq

Questions from publishers

Does CreekX include a newsroom or graphics system?

No. Produce the show in your own tools, then send it to CreekX. Lower thirds, tickers and switching belong in the gallery or in OBS.

Is there DRM?

No. Protect access with private links, tokens and your own approval check, which lets your subscriber system decide who plays a stream. There is no built-in paywall and no ad insertion; advertising on your page and in your own player is yours to run.

Can reporters send from the field?

Yes, with SRT from an encoder or phone app, or RTMP where SRT is not available. Plan for upload of about twice the stream’s bitrate. Background: SRT, RTMP and WHIP compared.

Can one server handle a breaking-news spike?

Up to its network port. A 4 vCPU server delivered a 1080p live to 400 low-latency HLS viewers at 0.80 of a core, so the processor has room, but 890 Mbit/s of upload is about 350 viewers at 2.5 Mbit/s. A news site should plan on HLS behind a CDN from the start: HLS through a CDN. We have not published a measured CDN result.

Can the CMS start and embed a live automatically?

Yes. The REST API creates streams and returns their watch details, and signed webhooks tell your systems when a stream goes live or ends and when a recording is ready. Start with the API quick start.

How quickly is the replay available?

The recording is prepared when the live ends and appears in the video library; long lives may be split into parts. Check it plays before linking it from the article.

Can a rolling channel carry our packages all day?

Yes. Build a 24/7 channel from library videos; the schedule refills itself so it does not run dry. How it works: 24/7 playout from a library.

11Your next step

Start with one show

Run one programme through the trial, then plan the rest with CreekX.

Follow the build