A VMS built for security integrators turns every camera project into recurring revenue: you connect the customer cameras to the platform, deliver monitoring as a monthly service, and manage everything — accounts, modules, users and billing — from a single dashboard, under your own brand.
Integrators adopt a VMS SaaS to stop selling installation alone and start selling a service: instead of delivering the project and ending the relationship, the integrator connects the customer cameras to a subscription platform and bills monthly for monitoring — with no server to buy, install and maintain at every customer. The platform handles recording, AI and updates; the integrator handles the customer.
Xeqmate was designed for that model: a multi-tenant VMS SaaS where the integrator administers their own operation — registering accounts, switching modules on to match each contract, controlling who sees what, and tracking usage and invoices in the billing area. And with white-label, all of it happens under the integrator brand.
The integrator commercial cycle at Xeqmate, end to end.
This reseller model is not a marketing promise — it is platform structure. The integrator billing dashboard shows, in real time, current-cycle usage item by item (camera, module, service), grouped by account, with a closing forecast, the contractual minimum and an invoice history. Every item is pro-rated by the days it was active in the cycle: switch a module on mid-month and you pay only for the days of use. With those numbers per account, the integrator sets their own pricing and margin on the service they resell.
In the cloud model there is no server to buy, install or maintain at each customer — cloud recording is sized per camera (resolution × retention days). For customers who require local video, the same platform runs on-premise servers.
IP cameras, DVRs and NVRs of any brand come in over RTSP, RTMP or P2P, with no hardware swap — the first cameras are connected live during the demo itself.
LPR for the residential community, facial for the plant, front desk for the apartment block: the integrator switches modules on and off per account, and billing follows — pro-rated by the days each module was active.
Platform name, your own domain, logos, colours, contacts, watermark and legal terms in your identity. The end customer sees your brand — details on white-label VMS.
The Administration menu concentrates the multi-tenant operation: accounts, cameras, users, auditing and billing.
A complete record for each account (details, address, time zone, language) with the list of modules enabled. The screen shows devices online and offline and the storage consumed per account; disabling an account preserves its cameras and users.
Each camera belongs to an account; camera groups define which cameras each user sees, and cameras flagged as shareable can be released to other accounts.
Invitation links per camera group let users sign themselves up; the integrator checks the details and approves each pre-registration before it becomes a real login.
Roles define what each user can view or edit per feature; camera groups define which cameras they see. Two-factor authentication (2FA), account expiry and session termination complete the control.
Queries, alerts, administrative actions and API calls are all logged — the integrator can prove who saw what and when, a frequent requirement in contracts and under privacy law.
Cycle usage filtered by account, category and type (cloud or on-premise), a detailed statement per account, and an Excel export of the estimate to reconcile with your own invoicing.
Migrating a customer portfolio to a new VMS is a project, not a click — and the integrator does not do it alone. The Xeqmate team works alongside yours on the camera rollout, and the first demo already connects a real camera from your operation: you see the platform running on your own footage before deciding.
For operations monitoring many customers from one control room, see also VMS for central stations. And if your team builds its own systems, the documented external API and the webhooks wire the platform into your software.
No. In the cloud model, the customer cameras send video straight to the platform over RTSP, RTMP or P2P — no local server. For customers who require recording inside their own infrastructure, the same platform runs on-premise servers, and both types live in the same dashboard.
A monthly subscription calculated on usage: cameras (by resolution × retention plan), modules and active services, pro-rated by days of use in the cycle, with a contractual minimum. The invoice is always the greater of the minimum and the measured usage, and the billing dashboard shows it all in real time, per account.
Pricing to the end customer is yours. The platform gives you the detailed cost per account — cycle usage, an itemised statement and an Excel export — and on top of that cost the integrator sets whatever monthly fee and margin they want.
Yes, fully: platform name, your own domain with DNS instructions, logos, menu colours, support and sales contacts, app store links, watermark and your own legal terms. Details on the white-label VMS page.
In three layers: modules enabled per account (what the account contracts), camera groups (which cameras each user sees) and permission roles (what each user can view or edit in each feature). All of it written to the activity audit trail.
No. IP cameras, DVRs and NVRs of any brand connect over RTSP, RTMP or P2P. The AI analytics, LPR and facial recognition run on the platform server, so the existing base gains intelligence with no special hardware.
Yes. Modules are enabled individually per account, and billing follows: ticking or unticking a module moves the invoice pro-rata by the days it was active. Every account pays for what it uses.
30 minutes with our team: we connect one of your cameras live, show account management and integrator billing, and you leave with the cost for your own scenario.
We reply within one business day · no credit card, no install, no commitment