Feeds are split across sites and applications
Bring camera feeds into one wall instead of opening a different viewer for each location or system.
Remote Site Video Monitoring
Remote site video monitoring on your own server
When engineers or operators need live views from offshore, marine, port, energy, utility, construction or industrial sites, the decision is not only how to see the feeds. It is also where video is processed, who can watch and whether the system must operate without an external cloud. CreekX Cameras runs on your server and brings supported ONVIF and RTSP feeds into a browser-based camera wall.
CreekX Cameras Illustrative camera wall with demo footage
Demo feed 01Demo
Demo feed 02Demo
Demo feed 03Demo
Demo feed 04Demo
Demo feed 05Demo
Demo feed 06Demo
Recording & playbackTimeline illustration
When a remote camera setup becomes difficult to manage
Video must remain on controlled infrastructure
Install CreekX on your own server and store recordings on your own disks rather than sending them to a CreekX-hosted service.
The site may have limited or no internet access
A fully offline package and locally verified licence file are available through an assisted deployment. Viewing from outside the site still requires a network path provided by your organisation.
Different people need different access
Use per-site permissions, protected watch links, one-time viewer tokens, IP allow-lists and viewer connection logs to control and review access.
What operators and remote teams can use
Browser-based camera wall
Use ONVIF discovery for supported cameras, add RTSP sources and arrange multiple live feeds on one screen.
Recording and review tools
Record feeds continuously and use playback, clips and snapshots from the Cameras portal. Camera-offline alerts notify the customer’s team when a feed stops.
Site and viewer controls
Limit each person to approved camera sites and provide view-only access without giving them administrative control.
Control-room displays
Show a selected feed or wall on a locked Android kiosk screen or tablet.
How video moves through the deployment
From the site
CreekX supports ONVIF and RTSP camera sources. Encrypted SRT ingest is also available for feeds sent with an AES passphrase.
On your server
The application, camera portal, access records and footage run on customer-controlled infrastructure. Server capacity is sized around the number of feeds, video quality, recording requirements, storage and network conditions.
To viewers
CreekX delivers browser viewing through WebRTC, HLS and low-latency HLS. The appropriate path depends on the required delay, device and available connection.
Evaluate CreekX with your own site details
CreekX Cameras is not included in the 14-day Media Server trial. Camera projects begin with a conversation and a pilot using the prospective customer’s camera setup.
Describe the viewing task
Share the approximate number of cameras and sites, where viewers will be, which screens they use and whether the deployment must operate offline. If you do not know the camera protocol, server specification or final architecture, say so.
Check the proposed setup
CreekX reviews known camera models, ONVIF or RTSP support, video quality, acceptable delay, recording needs, access controls and the available server and network.
Run a camera pilot
The pilot checks the proposed connection and viewing workflow with the customer’s own cameras before a wider deployment is agreed.
Install and hand over
Paid licences include an Ubuntu self-install kit, offline upgrade packages and email support. Done-for-you installation and operator training are paid or Enterprise services.
Compatibility and security boundaries to check
CreekX currently supports ONVIF and RTSP cameras. Support for cameras that only use ONVIF Media2 is being added, and physical-camera validation remains outstanding. A pilot is therefore the appropriate place to confirm a specific camera and deployment.
- There is no fixed camera count promised for one server; capacity depends on hardware, video quality, storage and network conditions.
- Recorded video and library files are stored unencrypted on the customer’s disks. Deployments requiring encryption at rest need server-level disk encryption.
- Core offline operation makes no telemetry calls. Enabling off-site backups, external storage or another outbound integration creates a separate data path.
- CreekX currently has no formal security certification, external penetration-test report or external audit.
- OpenID Connect sign-in is supported, but built-in two-factor authentication and SAML are not. Testing so far used a test identity provider.
What a CreekX Cameras subscription includes
Every Cameras plan includes the live wall, ONVIF discovery and PTZ controls, continuous recording, playback, clips, snapshots, camera-offline alerts and per-site access. Footage is stored on the customer’s disks, so CreekX does not charge for cloud storage or by viewer. If a subscription is not renewed, updates and email support stop. Existing camera recording continues and recordings remain playable; after a 30-day grace period, new cameras and features cannot be added until renewal.
Starter
Up to 16 cameras at $60 per camera per year.
Business
17-100 cameras at $40 per camera per year.
Enterprise
More than 100 cameras or a deployment using multiple servers is priced by quote.
Included support
Email support is available Sunday to Thursday, 09:00-18:00 Gulf Standard Time, with a reply within one business day.
Continue the technical evaluation
The public documentation covers installation and product operation. The benchmark page presents dated first-party Media Server tests and their conditions; those tests do not replace compatibility checks with physical cameras.
Bring your site, camera and access questions
You do not need a finished technical specification. Tell CreekX what your team needs to view, the approximate camera and site count, who needs access and whether the system must operate offline. Unknown camera models, protocols or server details can be identified during the fit review.