A VMS for central stations has to bring every customer camera into one place, filter out what does not matter and put the right alert in front of the right operator — with everything logged. Xeqmate is a video surveillance platform for control rooms that does this in a single subscription, in the cloud or on-premise.
Central station software needs four things: it has to gather cameras from many customers and many brands into one dashboard, with each operator seeing only what they are allowed to; it needs tools for continuous operation, such as video walls, automatic cycling and PTZ; it needs AI-filtered alerts to cut false triggers; and it needs an auditable record of every event handled. Xeqmate delivers all four on the same platform, and also pushes alerts into the software the control room already uses, over webhook.
Xeqmate is a multi-tenant VMS SaaS: the control room subscribes per camera and per module, with no perpetual license, and can run under its own brand using white-label. The sections below show how each need is met in practice.
A control room serves dozens of contracts, each with different equipment. The VMS has to absorb all of it with no hardware swap.
IP cameras, DVRs and NVRs from any manufacturer join the platform over RTSP, RTMP or P2P. The cameras your customers already own keep working.
Each control-room customer is registered separately, with modules enabled one by one — LPR for one, facial and analytics for another. Camera groups organise who sees what.
Cycle usage, invoices, forecast, contractual minimum and Excel export — the foundation for the control room to bill a monthly monitoring fee per camera and module.
The video wall screen was designed for people who spend a whole shift in front of the video.
The operator builds the grid by dragging cameras, picks the layout (automatic or fixed, from 1 up to 6×6), highlights the important tiles and saves the wall under a name — up to 36 cameras per wall, reopened in one click at the start of each shift.
Each tab at the bottom is a complete wall; only the active tab plays video, so opening several does not load the connection. The "New Window" button opens a wall in another browser window — handy for spreading sectors across several monitors.
With two or more walls open in tabs, cycling switches between them on its own, at intervals from 3 to 600 seconds — one wall per sector, and the screen rotates without the operator clicking anything.
Cameras with PTZ enabled get a control panel right in the wall. The camera map shows the geographic spread and the status of every device — with a filter for offline or faulty cameras to run at the start of a shift.
A false alarm costs operator attention and credibility with the customer. At Xeqmate the video analytics run on the server — any camera with an RTSP/RTMP stream will do — and each one is tuned to fire only when it matters.
The available analytics are motion, person, vehicle, object, fire and PPE detection, with up to 2 algorithms per camera. Together with LPR and facial recognition, they feed the event center with already-filtered incidents.
Alert and analytics triggers land in the Event Center with an image, the source camera, a description and a status. The operator follows the rule look → decide → record: open the event, assess the image, decide what to do and change the status with a comment ("patrol dispatched", "false positive", "escalated to supervisor"). Every change goes into the event history with timestamp, status, user and comment — the record that supports the audit of the response and the accounting to the customer.
Search filters by customer, cameras, period, event type and status, and even by specific plates. There is also smart search across AI events to locate incidents inside the recordings. The details are on the event center page.
No control room wants to be held hostage by one more screen. Xeqmate alerts go out through several channels at once.
A push notification in the mobile app and a popup in the platform itself, with alert preferences set in each operator profile.
Alerts in the operator Telegram or in groups. Alert groups define who gets notified per customer — platform users, a Telegram group and up to 5 third-party email addresses per group.
Plate, vehicle-attribute and face alerts are sent as an HTTP POST with a fixed JSON shape to your system URL, with a Bearer token, an HMAC signature, camera and event-type selection, and an external code per camera. See the integrations page.
In the cloud model there is no server to install per customer: a new contract is a new record, and the cameras go live over RTSP, RTMP or P2P. Billing follows usage — a monthly subscription per camera (resolution × retention days) and per module, with a monthly minimum. For operations that require video inside their own infrastructure, on-premise recording servers live alongside the cloud on the same platform.
This is the model security companies use to turn monitoring into recurring revenue — with the whole platform running under the control-room brand, thanks to white-label.
Yes. Xeqmate sends plate, vehicle-attribute and face alerts over webhook: an HTTP POST with a fixed JSON shape to your system URL, with a Bearer token, an HMAC signature, camera and event-type selection, and an external code per camera/event.
No. IP cameras, DVRs and NVRs of any brand connect over RTSP, RTMP or P2P. The AI runs on the platform server, so any camera with an RTSP/RTMP stream gets analytics, with no special hardware.
Each analytic is tuned per camera: up to 4 detection zones drawn over the image, a trigger condition (minimum count, consecutive detections, time window), sensitivity in three levels, and operating hours per day of the week — person detection active only outside business hours, for example.
Only if the administrator allows it. Each user reaches only the sites, cameras and modules permitted, and the audit trail records queries, alerts and actions — the control room knows who saw what, and when.
No. In the cloud model, a new customer is a new record, with no extra infrastructure. When the contract requires local recording, on-premise servers live alongside the cloud on the same platform.
Yes, white-label is complete: your own domain, logos, colours, support contacts, app store links, watermark and custom legal terms. Details on the white-label VMS page.
The operator opens one wall per sector, each in a tab, sets the interval (3 to 600 seconds) and starts cycling: the screen switches between tabs automatically. Only the active tab plays video, so the connection is not overloaded.
30 minutes with our team: we connect one of your cameras live, you watch the alerts land, and you leave with the cost for your own scenario.
We reply within one business day · no credit card, no install, no commitment