Public Safety

Live video for public safety teams, on servers you hold

Public safety teams often cannot send video through a commercial cloud. CreekX runs on servers you control, receives camera and field feeds over encrypted connections, and records who watched what.

01triggers

When video must stay under your control

A control room needs video from fixed cameras, vehicles and temporary incident sites on one screen, and a rule often says that video may not pass through a commercial cloud. That leaves two questions for the technical lead: how each feed gets in over the network it actually has, and how to show afterwards who watched it.

Policy rules out a public cloud

Install creekX on your own Ubuntu servers, including a network with no internet connection. The licence is verified locally from a signed file, the product sends no telemetry, and upgrades arrive as offline packages.

Field feeds arrive over weak links

Send with SRT, which re-sends lost packets inside a delay you choose, with AES encryption and a separate passphrase for each stream. A vehicle on mobile data keeps a usable picture where RTMP would break up.

You need a record of who watched

Viewer connection logs show who watched, from which address and device, and when. Admin actions go to a separate audit log whose entries are chained by hash, so a changed entry can be detected. Both stay on your server.

A fire engine with blue lights on a dark street at night, seen from above
An incident scene is temporary and its network is whatever the vehicle carries. That is the feed a control room most needs and the hardest one to deliver.
02process

How teams use it

Fixed and field video take different routes in and meet on the same server. The longer walk-through is in the public safety video streaming guide.

Bring in fixed cameras

Use CreekX Cameras for ONVIF and RTSP cameras grouped by site, recorded continuously and shown on walls of up to 4x4 tiles. Cameras is licensed per camera and starts with an assisted pilot.

Bring in field video

Receive SRT, RTMPS or RTSPS from encoders and vehicles. Each stream has its own key, and a guest key that expires can be given to a unit from another agency for one incident. Steps: go live from an encoder.

Share with the right people

Give time-limited watch links, limit watching to known network addresses, or have your own system approve each viewer before playback. If that system does not answer, creekX refuses the viewer.

Diagram: fixed cameras over RTSP and field encoders over encrypted SRT feed a creekX server inside the agency network, which serves a command room wall, officers and partner agencies
The public safety path with the server inside the agency network. Delay figures: creekX 2026.10.13, 1080p source, measured on a local network. Viewer figures: one 4 vCPU, 8 GB cloud server with about 890 Mbit/s of upload. Conditions are on the benchmarks page.
03deliverables

What you get

  • Encrypted contribution: SRT with a per-stream AES passphrase, RTMPS and RTSPS
  • Camera walls grouped by site, with continuous recording on your own disks
  • WebRTC delivery for a wall that follows events in under a second in our tests
  • Viewer connection logs and a hash-chained admin audit log, kept on your server
  • Time-limited links, one-time viewer tokens and address allow-lists
  • Offline installation, licence and upgrades on request
04protocol fit

Which protocol for which feed

Choose the way in by the network the source has, and the way out by how quickly the viewer must react.

creekX carries standard audio and video. It has not been tested with drone telemetry or other metadata embedded in the stream; do not plan on metadata pass-through without testing it with CreekX. Background on the protocol: SRT over bad networks.

Protocol choices for public safety video. Delay figures are creekX’s own measurements on a local network.
FeedProtocolFigureWhy
Fixed camera on your networkRTSP, with ONVIF control3 Mbit/s per 1080p camera in our testStays inside your network and records without conversion.
Vehicle or drone ground station on mobile dataSRT with AESDelay is the SRT latency you setRe-sends lost packets; encrypted with a passphrase per stream.
Encoder on a private circuitRTMPS or RTSPSNot measured separatelyTLS on a link that does not lose packets.
Command room wallWebRTC0.49 s median, 0.68 s worstOperators and the radio channel stay in step.
Officer or partner on a laptopLow-latency HLS1.23-1.28 s medianPlain HTTPS through restrictive firewalls.
05sizing and cost

A sizing example: 20 field feeds and a control room

From our Media Server test on a 4 vCPU, 8 GB server: 49 incoming 1080p streams at 5 Mbit/s, each recorded, used 13% of the processor and 1.5 GB of memory.

  • Feeds: 20 at 1080p and 5 Mbit/s is 100 Mbit/s into the server.
  • Recording: 20 x 2.3 GB is about 46 GB an hour, about 1.1 TB for a full day of all 20.
  • Viewers: a control room of 30 screens at 5 Mbit/s is 150 Mbit/s on the local network. Receiving and passing streams through needs little processor.
  • Fixed cameras: sized separately, by disk. One camera at 3 Mbit/s writes about 32 GB a day.
  • Licence: Media Server Pro is USD 99 per server each month, or USD 999 a year, for up to 50 live streams. Cameras are USD 40 to 60 per camera per year. Offline packages, installation and training are arranged through sales.

Not measured: feeds arriving over real mobile networks, and more than 50 streams on one installation. Larger deployments should be sized with CreekX.

06First-party evidence

A recorded-stream benchmark, with its limits

On 13 October 2026, CreekX 2026.10.13 was installed using the standard one-line installer on Ubuntu 24.04. The test server had 4 vCPU, 8 GB memory, a 100 GB NVMe disk and about 890 Mbit/s upload bandwidth. It received a real 1080p, 25 fps H.264 test clip at 5 Mbit/s, and each test step ran for 60 seconds.

49 recorded input streams

All 49 streams remained live. CreekX reported 13% CPU across the four cores, 1.5 GB memory use and 30.6 MB/s of disk writes. The CPU figures exclude the test tools.

What this result does not establish

The inputs were not validated physical cameras. The test therefore measures concurrent recorded streams under the stated conditions, not broad camera compatibility or a fixed number of cameras for another server.

Storage matters

At the tested 5 Mbit/s rate, one 1080p stream produces about 2.3 GB per hour, or about 55 GB per day. Retention requirements and disk performance should be included when sizing a deployment.

07honest limits

What creekX does not do for public safety

  • No security certification, independent penetration test or external audit has been completed.
  • No direct integration with body-worn cameras, dispatch or records systems. It receives standard streams and offers an API.
  • No video analytics: no face, person or number-plate recognition.
  • No built-in evidence management. Recordings are files on your disks; chain of custody is your procedure.
  • Recordings are not encrypted by creekX on disk.
  • One server per installation, and no round-the-clock phone support unless agreed in an Enterprise contract.
08Scope & limitations

Security and data boundaries

CreekX reports HTTPS for the application and video, encrypted WebRTC media, encrypted SRT ingest and AES-256-GCM protection for stored credentials. Recorded video is not encrypted by CreekX on the customer’s disks; deployments requiring encryption at rest need server-level disk encryption. Optional off-site backups, storage services or other outbound integrations create data paths outside the server when the customer enables them. CreekX currently has no formal security certification, independent penetration test or external audit.

09buyer fit

Who CreekX Cameras is suited to

CreekX Cameras is intended for mid-sized and large organisations with a technical owner and a need to view or record camera feeds on customer-controlled infrastructure.

  • Industrial, offshore, marine, port, energy, utility, construction and campus teams that need remote browser viewing.
  • Government and critical-infrastructure teams evaluating an offline or air-gapped deployment.
  • Organisations that need camera access separated by site.
  • Teams prepared to confirm their camera models through an assisted pilot.
10faq

Questions from public safety teams

Does CreekX connect to body-worn cameras or dispatch systems?

Not directly. It receives standard streams such as RTSP, SRT and RTMP, and has a REST API and webhooks for your own integration. A body-worn camera that can only upload to its vendor’s cloud will not work. Ask CreekX about a specific device before buying.

Is it certified for law enforcement use?

No. No formal third-party security certification, penetration test or audit has been completed, and CreekX makes no compliance claim for any policing standard. The security page lists what the product does and how it has been tested.

Can it run in a closed network?

Yes. An offline licence and installation package is available through sales, and core operation makes no outbound connection. Viewing from outside the closed network needs a path your own team provides.

How much delay does a command room see?

Over WebRTC we measured 0.49 seconds median and 0.68 seconds at worst on a local network. A field feed adds the SRT delay you set for the link, commonly a fraction of a second to a few seconds on mobile data, and we have not measured that end to end over a mobile network.

Is the video encrypted?

In transit: SRT uses AES with a passphrase per stream, RTMPS and RTSPS use TLS, the app uses HTTPS, and WebRTC media uses DTLS-SRTP. On disk: creekX does not encrypt recordings; use disk encryption on the server when you need encryption at rest.

How long can recordings be kept?

As long as your disks allow. A 1080p feed at 5 Mbit/s writes about 2.3 GB an hour, about 55 GB a day. Removed videos are kept for 30 days before deletion. Retention policy and evidence handling remain your own procedures.

Can a partner agency watch one feed for one incident?

Yes. Send a private watch link that expires, or a one-time token, for that stream only. Revoke all private links at once when the incident closes. The connection log shows whether the link was used and from where.

11Your next step

Check it against your own policy

Share your network rules, the sources you need to bring in and who must watch, and CreekX will tell you plainly what fits and what does not.

Follow the build