Campus Security Cameras

Campus and office cameras, one wall per building

Universities, schools and companies run cameras across many buildings. CreekX Cameras groups them by building, records them and lets each guard or manager see only their own.

01triggers

When buildings are watched separately

A campus grows a building at a time, and each building arrives with the camera system its contractor preferred. The security office ends up with a different viewer for the library, the residences and the car parks, and reviewing one incident that crossed three buildings takes an afternoon.

Each building has its own system

Bring ONVIF and RTSP cameras into one place, whatever brand each building has. The cameras stay where they are; creekX connects to them over the campus network.

Guards cover different buildings

Limit each person to their buildings. A residence warden sees the residences, the security office sees everything, and the server enforces the difference.

Incidents need reviewing

Play back by time and save clips. Move through a camera’s timeline to the minute, then save a clip or a snapshot to hand over, instead of exporting hours of footage.

Aerial view of a university campus with stone buildings, lawns and a lake among wooded hills
A campus is many buildings on one network. That is what lets a single server on that network record all of them.
02process

How it works

Group cameras by building

Give each camera a site name; they appear together. Find cameras with ONVIF discovery from the server, or add an RTSP address by hand for a camera that does not answer.

Watch on any screen

Walls of up to 4x4 tiles, on a TV or a laptop. A lodge or reception screen can run the locked Android kiosk player, which shows one view and gives no controls.

Review and share clips

Save clips and snapshots for an incident. Recording is continuous to your own disks, and the viewer log records who looked at which camera and when.

Diagram: cameras in campus buildings connect by ONVIF and RTSP to one creekX Cameras server, which serves the security office wall, building guards and a locked lodge screen
The campus camera path. Figures come from tests with simulated ONVIF cameras in October 2026; physical cameras have not been validated.
03deliverables

What you get

  • Walls grouped by building, in 2x2, 3x3 or 4x4 tiles
  • Continuous recording to your own disks, with playback by time
  • Clips and snapshots
  • Per-person building access, with viewer and admin logs
  • Camera-offline alerts and pan, tilt and zoom where the camera supports it
  • Your own server, on the campus network
04protocol fit

Which protocol carries which leg

Protocol choices for campus cameras. Delay figures are from creekX Media Server tests on a local network.
LegProtocolFigureNotes
Camera to server on the campus networkRTSP video, ONVIF control3 Mbit/s per 1080p camera in our testStays on your network. Nothing goes to a camera cloud.
A satellite campus to the serverSRT with an AES passphraseNot measured separatelyEncrypted across the internet; re-sends lost packets.
Server to the security office wallWebRTC0.49 s median, 0.68 s worstGuards see events as they happen.
Server to a manager’s laptop off campusLow-latency HLS over HTTPS1.23-1.28 s medianThrough a VPN or other path you provide.
05sizing and cost

A sizing example: 80 cameras in eight buildings

In our test on 15 October 2026 an 8 vCPU, 16 GB server recorded 100 simulated ONVIF cameras at 1080p and 3 Mbit/s at 21.8% CPU and about 1.1 GB of memory. The same class of server covers this example with room to spare.

  • Network in: 80 x 3 Mbit/s is 240 Mbit/s.
  • Disk: about 2.6 TB a day; 36 TB for 14 days, 77 TB for 30 days.
  • Processor: about 0.2% of the server per recording camera, so roughly 17%.
  • Licence: 80 cameras at USD 40 per camera per year is USD 3,200 a year, with no charge per viewer or per gigabyte.

The disks cost more than the licence. Decide the retention period first, because it sets the storage bill. Not measured: physical cameras, H.265, and walls and recording under load together.

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 Cameras does not do for a campus

  • No analytics: no motion, person, vehicle or number-plate detection.
  • No door access, alarm or intercom integration.
  • No support yet for ONVIF Media2-only cameras, and no validation on physical cameras yet.
  • No SAML and no security certification.
  • Not part of the free trial: Cameras starts with an assisted pilot on your own cameras.
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 campus teams

Can a guard see only their building?

Yes. Limit each person to named sites. The limit covers live video, recordings and clips, and it is enforced by the server, so a shared link does not get round it.

Does it alert on motion or people?

No analytics are included in the current release: no motion, person or vehicle alerts. creekX alerts when a camera goes offline. If your policy depends on analytics, say so before the pilot.

Is it the same product as Media Server?

No. CreekX Cameras is licensed separately, per camera: USD 60 per camera per year up to 16 cameras and USD 40 from 17 to 100. Media Server is USD 99 per server each month and is the product for lectures and events, described under live classes.

How much disk does a campus need?

Cameras times bitrate times days. One 1080p camera at 3 Mbit/s writes about 32 GB a day. 80 cameras write about 2.6 TB a day, so 14 days needs about 36 TB and 30 days about 77 TB. Lowering a camera’s bitrate lowers this in proportion.

Will it load the campus network?

Each camera sends its stream to the server all day: 80 cameras at 3 Mbit/s is 240 Mbit/s arriving at the server’s port. Put the server where the building links meet, and keep cameras on their own network segment.

Can staff sign in with their university account?

Yes, through any OpenID Connect provider. SAML is not supported. Steps: single sign-on.

Which cameras work?

Cameras with ONVIF or an RTSP address. Cameras that rely only on ONVIF Media2 are not supported yet, and our tests used simulated cameras, so check your models in the pilot.

11Your next step

Count your cameras and buildings

Share the number of cameras, buildings and people who need access, and CreekX will size it.

Follow the build