Remote bidders, sports viewers, camera operators and continuous-channel teams need different things from video. Compare the four priority CreekX use cases, see which product supports each one and decide whether to begin with the Media Server trial or an assisted conversation.
Use CreekX Media Server when remote bidders need to follow a car, livestock, art, equipment or property auction close to real time. Send video from a browser, encoder or supported stream source, deliver it over WebRTC and protect viewing with controlled watch links.
Stream matches from one or several video sources to viewers on browsers and phones. Media Server supports WebRTC for viewing close to real time, plus HLS and low-latency HLS when wider device support matters. Viewer controls can restrict access to approved audiences.
Use CreekX Cameras for industrial sites, offshore and marine operations, ports, utilities, construction sites or campuses. Connect ONVIF or RTSP camera feeds, bring them into one browser-based wall and provide controlled remote viewing. CreekX checks camera models and deployment requirements before arranging a pilot with your cameras.
Build a continuous channel from your own video library without keeping an operator at the controls. Upload videos, create a schedule and let the channel refill its schedule so it can continue through nights and weekends. The channel capability is included within CreekX Media Server.
The per-server subscription covers live streaming and 24/7 channels, with browser, encoder and stream-source ingest; WebRTC, HLS and low-latency HLS delivery; recording; viewer controls; an API; and supporting media tools. It is the starting point for auctions, sports and continuous channels.
The separate per-camera subscription is for managed IP camera operations. It includes ONVIF discovery, the live camera wall, recording, playback, clips, snapshots, offline alerts and access by site. Camera capacity is sized for the customer's hardware and video requirements.
Both products run on customer-controlled servers rather than hosting video on CreekX infrastructure. The standard Media Server trial needs internet access during installation. Fully offline or air-gapped deployments use an offline installation package and licence file supplied directly by CreekX. Optional outbound integrations create their own external data paths, so those connections should be reviewed as part of deployment planning.
Developers, IT teams and technical buyers can evaluate live streaming or 24/7 channels without a call. The trial lasts 14 days, requires no credit card and includes Media Server Pro features with trial limits of five channels on air, five restream destinations per stream and 500 library videos. It runs on Ubuntu or a laptop using WSL 2, Multipass or Ubuntu.
Begin with a conversation for CreekX Cameras, a fully offline site, several servers, more than 50 live streams, thousands of viewers, a tender or an Enterprise deployment. CreekX can review the intended use, sources, audience, delay requirements and available hardware before recommending the next step.
The public evaluation material includes a working 14-day Media Server trial, 24 documentation guides and a REST API reference. First-party benchmark results are published separately with their test dates, hardware, video settings, network conditions and measurement boundaries so technical teams can assess what was measured without treating it as a promise for every deployment.
Describe what you need to keep live, who needs to watch and whether the system must work offline. It is fine if you do not yet know the product, protocol, server specification, viewer count or camera details. CreekX can use an initial conversation to identify the information needed for a trial, pilot or quotation.