Skip to content
Camzify
Managed service providers

Camzify for managed service providers

An MSP already carries the operational relationship, the network and often the site access, which is most of what a video surveillance rollout needs. Camzify adds a security service line on top of that footprint with no hardware to procure: one account you hold, a scoped login per customer, license quota you allocate and reclaim, and a report per patrol round to show each of them.

Book a demo How sub-users and quotas work
  • One account, a login per customer
  • Quota allocated and reclaimed by you
  • Alerts and reports per client
Account structure

Built for the party that is not the site owner

Most video software assumes the operator and the owner are the same company. Camzify assumes they may not be. You hold the account; every customer is a sub-user scoped to its own sites and cameras, carrying a permission group that decides which pages it can open and what it can change. A customer never sees another customer.

Quota flows the same way. Sites, cameras, AI feature instances and backup storage are handed to each customer out of what you hold, and a customer that reaches its allocation requests more rather than taking it. The plan page breaks storage out as provisioned, used, assigned to child accounts and remaining.

The service

What you run for each customer

Live wall across customers

Every customer's cameras on one screen, grouped by site with a per-site online count. Filter to one customer or one AI feature.

Recording and retention

Per camera, continuous or scheduled, kept by days or a storage cap. A copy in the cloud survives whatever happens to the customer's recorder.

Alerts routed per client

Channels per alert category and severity per camera per feature, so the critical events reach you and the routine ones reach the customer.

Rounds with a report each

Scheduled patrol rounds on each customer's cameras, the guard messaged on a failed check, and a compliance report per round to hand over.

Operations

Onboarding, change and offboarding

  • Onboard a customer by creating the sub-user, allocating quota and adding their sites. Cameras on their LAN connect through the Connector with no change to their firewall.
  • Change what a customer can do by moving them to a different permission group. The change takes effect immediately, with nothing to propagate.
  • Offboard by suspending the sub-user. Login stops, the data stays, and reinstating restores exactly what was there. Every step is in the audit trail.

What we will not tell you

That there is a published partner margin, a white-label option or an SLA figure. Pricing is quote-based and partner terms are agreed in conversation. The console carries the Camzify name. We also do not publish uptime, response-time or event figures, because we cannot substantiate them for your customers; the trust page sets out that policy. If your work is installing cameras rather than operating them, see security integrators; if you run monitoring for security agencies, see monitoring companies.

FAQ

Frequently asked questions

Each customer is a sub-user scoped to its own sites and cameras. A customer logging in sees only what is theirs: their live wall, their alerts, their patrol reports. Your operators, on the parent account, see every customer. Sub-users can create their own sub-users, so a customer with several departments can delegate further without involving you.

From what you hold. Sites, cameras, AI feature instances and backup storage are allocated to each sub-user out of your own quota, and a customer that reaches its allocation sees it as at capacity and can request more. You approve the request, or not. Storage is broken out as provisioned, used, assigned to child accounts and remaining, so what you have given away is never blended into one number.

Yes. A sub-user can be suspended, which blocks login and leaves the sites, cameras, recordings and reports in place. Reinstating them restores access to exactly what was there. Deleting is a separate, deliberate action.

Whoever you configure. Notification channels are set per alert category, and severity can be set per camera for each AI feature, so a critical event at one customer can reach your desk while routine events go to the customer's own contact. Patrol failures message the guard designated for that camera.

With the Camzify Connector, a small application on a Windows, macOS or Linux machine inside the customer's network. It relays local RTSP cameras to Camzify with no port forwarding, which matters when you do not control the customer's firewall. Cameras reachable from the internet connect directly, and encoders push RTMP.

A report per patrol round with every checklist result, the snapshot it was judged against, before-and-after frames for anything fixed, timestamps and a compliance percentage. Every action on the account is also written to an audit trail. The customer can read their own reports through their login, or you can send them.

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.