One live wall for every brand and location
One live wall for every brand and location is a single live view of every camera an operator is responsible for, whatever make it is and whichever site it is at, in place of a separate login for each recorder. The cameras already speak a common language: ONVIF and RTSP are on effectively every IP camera and recorder sold in the last decade. Camzify puts them on one wall grouped by site, with a no-signal state that says which site has the problem, and reaches the cameras behind a router through the Connector.
- Any ONVIF or RTSP camera or recorder
- Grouped by site, with an online count
- Local networks through the Connector
Five recorders, five logins, one operator
An operator with several sites usually has cameras bought several times, from several installers, over several years. Each site has its own recorder, its own app, its own password and its own way of showing that a camera has dropped. Checking every site means logging in and out five times, and the sites that are slowest to open are the ones checked least.
A security agency covering client sites has the same problem multiplied by clients. The control room carries a recorder login per site, and a guard who moves between sites carries them all. Nobody is watching the wall, because there is no wall; there are five windows.
The fragmentation is not in the cameras. ONVIF and the international standard built on it exist so that devices from different manufacturers work with one client. What most sites lack is the client: one place that listens to all of them.
- Warehouse — Sector 45/5 cameras online
- HQ Campus4/4 cameras online
- Retail — Downtown3/4 cameras online
- Distribution — North2/2 cameras online
- Each site runs its own sequences, schedule and guard roster on one account.
One wall, grouped by site, whatever the brand
Live streaming puts every connected camera on one grid, grouped by site, with a per-site online count in the site strip.
- A camera connects by ONVIF or RTSP directly, or through the Camzify Connector when it sits on a local network with no public route, with no port forwarding and PTZ passed through.
- A recorder that publishes its cameras as RTSP streams can be the source, so the existing recorder stays and keeps its local copy.
- The grid paginates so each stream stays legible, slideshow mode cycles the pages, and saved camera sets hold the cameras watched together with one set as the default view.
- A dropped camera shows as no signal at once, never a frozen last frame, and a site that goes offline is flagged in the site strip and with a banner across the grid.
- The grid filters by site, by AI feature or by what a given sub-user is allowed to see.
Multi-site management keeps each site its own record, so the wall does not become one undifferentiated pile of cameras.
- Each site keeps its own cameras, patrol sequences, operators and event history, and the dashboard and reporting can roll every site into one account-wide view or pull one site on its own.
- A sub-user is scoped to specific sites through a permission group, so a client or a guard sees their own cameras and nobody else's.
- Camera tampering detection raises a covered, turned or frozen camera to a person, so the wall does not depend on someone noticing a tile has changed.
- The supported cameras page lists manufacturers known to interoperate, and ONVIF and RTSP explained covers how to check a camera you already own.
Live streaming
Every camera on one grid grouped by site, paginated, with saved sets and a slideshow.
DetectionMulti-site management
A site is its own record with its own cameras, sequences and people, under one account.
DetectionCamera tampering detection
A covered, turned, defocused or frozen camera at any site, raised to a person with the frame.
DetectionPermission groups
Who sees which site. A client or a guard scoped to their own cameras on the same wall.
- Roller door closedCompliant
- Yard clear of vehiclesCompliant
- Camera view unobstructedCompliant
- Rear gate lockedNot compliant
A failed item is resolved as Fixed or Pending before the round can close.
What a round checks at a site the operator is not at
Once a camera is on the wall it is a stop like any other, whoever made it. Each site carries its own patrol sequence through its doors, its yard and its own cameras, on its own schedule, and one operator runs or reviews all of them from the same console.
A failed item captures the frame and messages the person designated for that camera at that site, and the report is filed per site, so a client with one store receives the round for that store and nothing else. The multi-site operations page covers the setup, and how to monitor live camera feeds walks through building the wall.
A check found Not Compliant captures a snapshot and messages the guard designated for that camera; on a manual round the operator chooses to send it, on an automated round it goes on its own. The item stays Pending until it is marked Fixed, which captures the after frame, and the report shows both.
Why it matters, in published figures
Figures from ONVIF, the IEC and NIST, linked to the page each comes from. None of them is a Camzify figure; we publish none.
- 35,000+
- ONVIF conformant products as the organization entered 2026, "all capable of integrating into a single management platform, regardless of vendor, using common ONVIF profiles." Its first conformant products shipped in 2009.
- Source: ONVIF, Building your security future with ONVIF conformant products (January 2026)
- 7 profiles
- Published ONVIF profiles as of 2026, from a membership of roughly 500 companies, with Profiles S and T covering video streaming, G recording and M metadata and events. ONVIF describes the aim as combining products "without vendor lock-in."
- Source: ONVIF, ISC West 2026 press release
- 2013
- The year the IEC published 62676-2-3, the international standard for IP video interoperability based on Web services, which "makes it possible to build network video systems with devices and receivers from different manufacturers using common and well defined interfaces."
- Source: IEC 62676-2-3:2013, IEC Webstore
- Proprietary formats
- NIST, at the FBI's request, on collecting video from many systems: "Current CCTV systems often output video in proprietary formats along with propriety software needed for viewing," which "adds an extra burden to the evidence collecting process."
- Source: NIST IR 8161r1, CCTV Digital Video Export Profile (2019)
What it will not do
One wall changes what the operator sees; it does not change what the cameras can do.
- It will not connect an analog camera that has no encoder or recorder putting it on the network, and it will not connect a camera that speaks a proprietary protocol and nothing else.
- It will not merge the recordings already on old recorders. That history stays on the recorder; off-site recording in Camzify starts when backup is switched on.
- It will not make a poor link good. A camera that drops shows as no signal and a site that goes offline is flagged; the fix is at the site.
- It will not run one round across every site at once. A patrol sequence belongs to a site, and each site runs its own on its own schedule.
We do not publish bandwidth per camera or a maximum wall size; the grid paginates. The trust page sets out why, and camera connectivity covers each protocol.
Industries where this applies
Frequently asked questions
Ready to patrol your site 24/7?
Book a 15-minute demo and see a live patrol run on your own cameras.