Skip to content
Camzify
Partner Program

Remote guarding software for security agencies

A guarding company can only sell as many hours as it can staff. Virtual patrolling is coverage that is not capped by headcount: scheduled rounds across every client site, through the hours nobody wants to work, with a report per client at the end of each one. Sold alongside guards, not instead of them.

The constraint every agency runs into

Night coverage is the hardest to staff and the least profitable to sell. A client with four sites wants all four checked overnight; the honest answer is usually a patrol car doing a circuit, or one site covered properly and three not at all.

Meanwhile the client keeps asking for something the industry has never been good at giving them: proof. Not that a guard was on site, but that the specific things they care about were actually checked, on the nights they were supposed to be.

Virtual patrolling answers both with the same product. Rounds run on the cameras a client already owns, on a schedule, across every site at once — and each round files a compliance report with the snapshot behind every check.

What it changes commercially

Coverage you cannot staff

Rounds every two hours across a portfolio of sites, overnight, at a cost that does not scale with headcount. The line item did not exist before because nobody could deliver it.

Evidence the client can hold

Each round produces a report naming every camera, every check, the result and the frame it was judged against, for the client, their insurer, or a dispute.

Guards dispatched to verified events

A failed check or a flagged risk notifies the guard responsible for that camera. Guard hours become response hours, which is the part a client will not cut.

One account, every client separated

Each client gets a login scoped to their own sites, with license quota allocated from yours and requests for more coming back to you to approve.

How a multi-client account is structured

The account model was built for exactly this shape: an organization holding license capacity and handing portions of it to others, who may in turn do the same.

  1. 1

    Sites are the unit

    Every camera belongs to a site, and access, reporting and alert filtering are all organized around it. One client, one or more sites.

  2. 2

    Each client gets a scoped account

    A sub-user reaches only the sites assigned to them. They see their own cameras, patrol reports and alerts, and nothing belonging to anyone else.

  3. 3

    A permission group decides what they can do

    Page-level access combined with create, read, update and delete rights per resource. A client who should look but not change gets exactly that.

  4. 4

    You allocate license quota

    AI feature instances, patrolling instances and backup storage are granted from your own unused allocation — never more than you hold.

  5. 5

    Requests come back to you

    When a client reaches a limit they submit a quota request rather than hitting a dead end. You approve it if you have capacity, or decline it.

Detail on both halves: user management and permission groups, or the walkthrough at managing sub-users and quotas.

Where your agency sits

Agencies come at this from different directions, and the argument changes slightly depending on which one you are.

Manned guarding

You sell guard hours and want to sell coverage on top of them, particularly overnight and across sites you cannot reach.

Remote guarding

You already sell monitoring as a service and want scheduled verification with an audit trail, not just event-driven alerts.

Monitoring center, CMS or ARC

You are staffed and watching, and the constraint is operator load and noise rather than coverage.

If you sell mobile patrols today, the mobile patrols comparison sets the two side by side, and the selling guide covers the client conversation. If you run a staffed monitoring operation, or a monitoring company runs it for you and notifies your guards, the monitoring companies page covers that angle, including who holds the account in that arrangement. If you resell rather than operate, see becoming a reseller; if you install and maintain camera systems, see security integrators.

What we will not tell you

That this replaces your guards. It does not, and an agency is the last audience that should be sold that story. Someone still has to attend, and no software decides what to do about a broken window at 2am. What changes is that the routine round — the part that is expensive to staff, easy to skip and impossible to prove — stops depending on somebody being awake, and your people are sent to the things that need people.

Everything on this page describes what the platform does today. Our position on claims we cannot substantiate is on the trust page, and it applies to partner conversations as much as to marketing.

FAQ

Frequently asked questions

No, and an agency should be skeptical of anyone claiming it will. What it changes is what a guard is dispatched to. A scheduled round covers the sites and hours you cannot staff, verifies specific conditions at each camera, and escalates to a guard when something needs a person. The guard hours you sell become response hours rather than walking hours, which is the part a client is least willing to cut, because it is the part that actually deals with the problem.

Sites are the unit everything is organized around. Each client can be given a sub-user account scoped to their own sites and cameras and nothing else, with a permission group deciding which pages they can open and what they can change. You allocate AI feature instances, patrolling instances and backup storage to each from your own license, and when a client reaches a limit their request comes to you to approve or decline rather than being granted automatically.

Yes. A sub-user reaches only the sites assigned to them, so a client logging in sees their own cameras, their own patrol reports and their own alerts. Reports carry the site and camera names, the checklist results, the snapshots each result was judged against, and the compliance percentage for the round.

Scheduled rounds across every client site at whatever frequency is agreed, every two hours through the night is common, with a compliance report filed after each one. Staffing that as physical patrols across a portfolio of sites is usually impossible at any price a client will pay. The rounds happen whether or not anyone is on shift, and the report is what the client is really buying: evidence the site was checked.

Yes, and the argument is slightly different there. A CMS or ARC is already staffed and already watching; the problem is operator load and the ratio of real events to noise. Scheduled rounds handle the routine verification that would otherwise occupy an operator, and detections arrive with the snapshot and the surrounding video attached so an operator can judge quickly. See our monitoring centers page for that side of it.

A guard tour system proves a guard reached a checkpoint, an NFC tag or a QR code was scanned. It says nothing about what was there. A virtual round checks a defined condition at each camera and stores the frame it was judged against, so the record shows the gate was actually closed rather than that somebody stood next to it. For an agency defending a claim, that difference is the whole point.

Ready to patrol your site 24/7?

Book a 15-minute demo and see a live patrol run on your own cameras.

Book a DemoCalculate Your Savings

This site is being updated

We are rebuilding pages as you read this, so an image, a link or a section may look unfinished for a while. The product itself is unaffected. If something important is broken, tell us at the contact page and we will fix it.