If your video must remain on infrastructure you control, the first decision is whether you need a connected on-premise installation or a package for a fully offline or air-gapped site. CreekX supports both routes on your own Ubuntu server. The standard trial downloads CreekX from the internet during installation; the fully offline package and locally verified licence file are supplied directly by CreekX.
Install CreekX on an Ubuntu server within your environment. The self-installer downloads the software during setup, making this route suitable for the Media Server trial and sites that permit controlled internet access.
For restricted or air-gapped networks, CreekX supplies an offline installation package and an offline licence file through the assisted sales route. Licence verification happens locally using a digital signature, and releases issued during the paid subscription can be provided as offline upgrade packages.
CreekX does not send telemetry. Outbound connections are limited to documented features that your team chooses to enable. Off-site backups, external restreaming and other outbound integrations create their own data paths and should be assessed as part of your network design.
CreekX Media Server and CreekX Cameras are separately licensed products deployed on customer-controlled servers.
Media Server accepts SRT, RTSP, RTMP and browser or encoder inputs. Viewers can receive video through WebRTC, HLS or low-latency HLS. It also supports live streams, scheduled 24/7 channels, recordings and a self-hosted video library.
CreekX Cameras discovers supported ONVIF cameras and connects to ONVIF or RTSP sources. Teams can bring multiple feeds into a browser-based camera wall, record footage on their own storage and control access by camera site.
Available controls include signed watch links, one-time viewer tokens, IP allow-lists, role-based access, viewer connection logs and administrative audit logs. These records remain on the customer’s server.
Use the offline package where production servers cannot reach the public internet, including government, defence, industrial, offshore and other controlled environments.
Keep live feeds, recordings, viewer details and operational logs on infrastructure managed by your organisation instead of sending them to a hosted streaming platform.
Run local channels, camera viewing and recording without making core operation depend on a continuous internet connection.
CreekX was built for requirements common in government and critical-infrastructure tenders: fully offline installation, encrypted SRT, view-only field access and viewer audit logs.
Start with the job: live streaming, 24/7 channels, IP cameras or a mixture. Share approximate source and viewer numbers, required video quality, acceptable delay, locations and whether the network is fully offline. If you do not know the technical details yet, say so.
Capacity depends on server hardware, video quality, recording, transcoding, incoming bandwidth, storage and viewer traffic. CreekX uses those details to assess the proposed server rather than promising one fixed capacity for every installation.
Paid licences include the Ubuntu self-install kit, documentation, release updates and email support. Fully offline packages are supplied directly. Done-for-you installation and operator training are paid or Enterprise services.
Before rollout, verify the actual camera or stream inputs, target screens, access rules and permitted network connections. CreekX Cameras prospects can arrange an assisted pilot using their own cameras.
The 14-day Media Server trial requires no credit card and includes the Pro feature set with trial limits of up to five 24/7 channels, five restream destinations per stream and 500 library videos. Its installer requires internet access, so it does not test the fully offline installation route. The CreekX Cameras portal is also excluded, although an RTSP or SRT camera feed can be added as a stream. At the end of the trial, the workspace becomes read-only; existing content is retained.
Tell CreekX what you need to stream, whether the site can reach the internet, and the approximate number of channels, cameras and simultaneous viewers if known. You do not need to choose the architecture or server specification before getting in touch.