Insights

Technical insights for your streaming-server decision

Start with six articles on the decisions that shape a streaming setup: WebRTC servers, WHIP and WHEP, SRT vs RTMP vs WHIP, IP camera streaming, live streaming media servers and server sizing. Each one explains the subject first and says where CreekX does and does not fit.

01service links

Match the subject to what you need to do

Deliver live video with less delay

CreekX Media Server accepts video from browsers, encoders and cameras through RTMP, SRT, RTSP or WebRTC inputs. Viewers can watch through WebRTC, low-latency HLS or standard HLS.

View IP cameras in one place

CreekX Cameras is the separately licensed option for discovering ONVIF cameras, connecting ONVIF or RTSP feeds and displaying multiple feeds in a browser-based camera wall.

Run a channel around the clock

CreekX 24/7 Channels is a Media Server capability for arranging uploaded videos into a TV-style schedule that continues when nobody is streaming live.

Keep the deployment on your infrastructure

CreekX runs on customer-controlled servers. Fully offline and air-gapped installations use an offline package and licence file supplied through the assisted sales route.

02document list

Six articles to start with

WebRTC servers

What a WebRTC server does, when real-time delivery is worth its cost and what to check before choosing one.

WHIP and WHEP

How publishing and playback work over HTTP signaling, and what a custom player still has to handle.

SRT vs RTMP vs WHIP

Which way to send video into your server, by network, encoder and required delay.

IP camera streaming

How to get RTSP camera feeds into a browser while keeping camera credentials on the server.

Live streaming media servers

The difference between a streaming server, a media server and a CDN, and which job each one does.

Streaming server sizing

How to estimate cores, memory, disk and bandwidth for your workload, and how to test the estimate.

Go deeper into the stream.

Browse all articles

Practical articles on streaming protocols, camera feeds, server sizing and implementation — with code examples and diagrams.

03technical brief

Choose the right level of technical detail

Documentation

Use the more than 40 public guides for installation, live inputs, 24/7 channels, recordings, captions, sharing, viewer security, single sign-on, backups, licensing and troubleshooting.

API reference

Use the REST API reference, documented in OpenAPI 3.1, when evaluating integration with your own applications and workflows.

Benchmarks

Review CreekX first-party measurements together with the stated product version, server specification, video settings, network conditions and test method.

Security and privacy

Review the current encryption, access-control, logging, storage and identity boundaries. CreekX does not currently have a formal security certification, independent penetration test or external audit.

04buyer fit

Choose your next evaluation step

Test Media Server yourself

The 14-day Media Server trial requires no credit card and includes the Pro features, with trial limits of five 24/7 channels, five restream destinations per stream and 500 library videos. Installation requires internet access, and the CreekX Cameras portal is not included.

Speak to CreekX before testing

Start with a conversation if you need CreekX Cameras, a fully offline or air-gapped installation, several servers, more than 50 live streams, thousands of viewers, tender support or Enterprise services.

Not sure about the technical details?

Describe what the video needs to do and where it must run. You do not need to know the final server, protocol, camera count, viewer count or architecture before getting in touch.

Follow the build