AI video analytics for the integrator who owns the customer relationship

You specified the cameras. You pulled the cable. You configured the NVR. You’re the one who answers the phone at 11pm.

Then an analytics vendor bills your customer every month, directly, forever — and slowly, your customer starts calling them instead of you.

We don’t do that. There is no subscription, because there is nothing to subscribe to. The processing happens in a box you installed, on your customer’s own network. If something goes wrong, they call you.

There is no subscription, because there is nothing to subscribe to

Most AI analytics products are cloud services. That architecture has a built-in consequence: the vendor keeps billing your customer every month, and the vendor’s name stays in front of your customer every month.

Our model is different. You sell a box. It processes video on-premise, inside your customer’s network. There is no recurring fee, no cloud account, no vendor relationship that sits between you and the person who hired you.

What that means for your business:

• You keep the recurring maintenance contract, not us.
• Your customer’s data never leaves their building — which is also why this closes deals where cloud analytics gets rejected outright by IT or compliance.
• There is no monthly line item for your customer to renegotiate with someone else next year.

One box, every channel — not six apps

The most common complaint we hear from integrators isn’t about accuracy. It’s about fragmentation: one app for people counting, another for LPR, a third for intrusion, each with its own login, its own licence, its own update cycle.

“I don’t want somebody that sells a product that I have to have launched six applications for in order to just lock my building.”
— an integrator, quoted in SDM Magazine

One box runs the analytics across every channel you connect. One interface, one search timeline, one export path. Your customer learns one system, and you support one system.

Standard packages are fixed at 2, 4, or 6 channels; custom builds scale to 128 — see custom solutions for how those are scoped and quoted. Cameras connect over ONVIF or RTSP, so the cameras you installed two years ago stay exactly where they are.

Your brand on the box, your name on the invoice

If you want to sell analytics under your own name, you can.

White-label options cover the hardware badge, the boot screen, the web interface, and the documentation. Your customer sees your brand, and your company stays the one they call.

This matters more than it sounds. When the analytics carry someone else’s logo, every support call is a reminder that your customer bought from two vendors. When they carry yours, the whole system is yours — including the renewal conversation.

OEM and ODM enquiries — custom firmware, SDK and API access, MOQ, and certification packages — are handled on a separate track. Send the requirement through the contact form and we’ll route it to the OEM team.

When something breaks at 11pm

We know what actually decides whether you’ll specify a product a second time. It isn’t the spec sheet. It’s what happens when a customer site goes down and you need an answer.

• Technical documentation, integration guides, and compatibility lists are public — no gate, no form.
• Direct technical support for integrators, including pre-sales design questions.
• Firmware updates are free for the life of the hardware. There is no “upgrade to keep your features” tier.

We also publish what our analytics are bad at — heavy rain, strong backlighting, very small subjects at frame edges, densely crowded scenes. You should know the limits before you promise a customer something, not after.

Where to go next

Tell us the scenario you’re quoting

Send us the site details — camera count, camera brands, what your customer actually needs to detect. We’ll come back with a channel recommendation, a compatibility check, and integrator pricing.

Integrators get standard-conformant interfaces rather than a private API: IEEE standards for networked device interfaces and RTSP (RFC 2326) for stream transport.