Alarms and guarding have become commodities — the customer compares prices and switches vendor. A video surveillance platform for security companies changes that conversation: intelligent monitoring under your brand, billed per camera as a monthly fee, with fewer false alarms and without switching off the system you already run.
A private security company adopts an intelligent video surveillance platform for four reasons: to hold on to customers with a service an alarm alone cannot deliver (AI, plate reading, facial recognition); to cut costs by filtering false alarms before they turn into a patrol dispatch; to build recurring revenue, billing a monthly fee per camera and module; and to scale the portfolio without buying a server for every new contract. Xeqmate delivers that in a SaaS model, with complete white-label.
A traditional guarding contract defends itself poorly against price competition. An intelligent monitoring service — sold under your brand, on the cameras the customer already owns — creates a bond that is harder to break: the customer comes to depend on your portal, your alerts and your response history.
The video analytics are tuned per camera: detection zones drawn on the image, a trigger condition, sensitivity, and hours by day of the week — person detection only outside business hours, for example. The operator sees the event image before deciding, and only dispatches a patrol when the incident is real.
The platform commercial model is a monthly subscription per camera and module. You pass it on as a monitoring fee, and the integrator billing area tracks cycle usage per account, invoices, the forecast, the contractual minimum and an Excel export.
With complete white-label, the platform runs under your name, your own domain, logos, colours, support contacts, app store links and legal terms. The end customer sees your company — not ours.
In the cloud model there is no server to install per customer: a new contract is a new record, and the cameras come in over RTSP, RTMP or P2P, any brand. When a contract requires local video, on-premise servers live alongside the cloud on the same platform.
Each module is enabled per account — you build the package to match the contract.
Plate and vehicle-attribute alerts, read search, co-occurrence and convoy reports — for residential sites, yards and perimeters.
Explore LPRReal-time face monitoring, face alerts and searchable reads — a clear differentiator in the commercial proposal.
Explore facialPerson, vehicle, object, fire and PPE detection on any camera with an RTSP/RTMP stream — the AI runs on the server, with no special hardware.
Explore the AIFor the shift itself — video walls with cycling, an event center with auditable handling, alerts over push, Telegram and webhook — see the VMS for central stations page. And if your company also installs and resells to others, the full business model is on VMS for integrators.
The most common objection from anyone already running a control room is the risk of the switch. There is no abrupt switch here: Xeqmate runs in parallel with the system you already use, sending events to your current software over webhook — an HTTP POST with a fixed JSON shape, a Bearer token and an HMAC signature. Migration happens at your pace, camera by camera, and customer cameras do not have to be replaced: any brand comes in over RTSP, RTMP or P2P.
Throughout the process, per-user permissions and an audit trail keep control: each operator sees only the accounts and cameras released to them, and every action is logged — one more argument in contracts that demand privacy compliance.
Yes. Xeqmate can run in parallel with what you already have and send events to your current system over webhook. Migration happens at your pace, camera by camera — and the demo already connects one of your cameras live.
Not if you use white-label: the platform name, your own domain, logos, colours, support contacts, app store links, watermark and legal terms are all customised with your brand. Details on white-label VMS.
The platform is a monthly subscription per camera and module, and you set your own price at the end. The integrator billing area shows cycle usage per account, invoices, the forecast and the contractual minimum, with an Excel export — the basis for billing monitoring as a monthly fee.
No. IP cameras, DVRs and NVRs of any brand connect over RTSP, RTMP or P2P, and the AI runs on the platform server — any camera with an RTSP/RTMP stream gets analytics.
The analytics are tuned per camera (detection zones, trigger condition, sensitivity and hours), and the operator sees the event image in the event center before deciding what to do — recording the handling with a status and a comment. A patrol only rolls when the incident is real.
No. In the cloud model, a new customer is just a new record in the platform. When a contract requires local recording, on-premise servers live alongside the cloud in the same operation, billed separately by type.
30 minutes with our team: we connect one of your cameras live, you watch the AI and the alerts work, and you leave with the cost for your own scenario — without switching anything off.
We reply within one business day · no credit card, no install, no commitment