OEM & white label AI video analytics

You already sell security hardware under your own brand. You want to add AI analytics to that range — without building an engineering team, and without handing your customer list to a supplier who might sell to them directly later.

That’s the arrangement we build. You sell it under your name. We stay out of the relationship.

What you get

A stable hardware platform plus a firmware stack you can put your own name on:

• On-box processing — 2 to 128 channels depending on model, running locally with no cloud dependency.
• Standard camera ingest — ONVIF and RTSP, H.264 / H.265, so it works with the camera brands your market already buys.
• SDK and API access — REST endpoints for events, search, and device management, so analytics can be surfaced inside your own VMS or portal.
• Firmware customisation — boot screen, web interface, device model name, documentation, and packaging.

Your brand, on the box and in the interface

White label isn’t a sticker. The options cover:

• Hardware badge and housing colour
• Boot screen and device model string (how it identifies itself on the network)
• Web interface logo, colour scheme, and product name
• User manuals, quick-start guides, and packaging artwork

From your customer’s side, the product is yours. There is no reference to us anywhere they can see.

We don’t compete with you for your customers

This is the part most OEM conversations actually turn on, so we’ll state it plainly.

Our model is on-premise hardware sold outright. There is no cloud account, no subscription, and no recurring billing relationship with your end customer — which means there is also no mechanism by which we could take that customer from you. We never see their contact details unless you introduce us, and we have nothing to invoice them for.

If you have been burned by a supplier before — a software vendor who started selling direct, or an analytics company whose logo appeared on your customer’s portal — this is the structural difference, not a promise in a contract.

Certification, MOQ and lead times

Typical questions at this stage, and how we handle them:

• Certifications — CE, FCC, RoHS documentation packages available. Ask for the current certificate set and we’ll send the files, not a summary.
• MOQ — depends on whether you need custom firmware and branding, or standard units. We quote both tracks separately so you can see the cost of each.
• Lead time — quoted per order, with the constraint named up front rather than after you’ve committed to your customer.
• Spare units and RMA — advance replacement terms and warranty period stated in writing before the first order.

If a question has an answer we can’t commit to yet, we say so. Guessing a certification date is how OEM relationships end.

Firmware updates and long-term supply

Two things decide whether an OEM programme survives its second year:

• Firmware updates are free for the life of the hardware. There is no tier where your features stop updating unless you pay again.
• Hardware revisions are announced in advance. If a component change is coming, you hear about it before you’re quoting a project against the old spec.

We also publish the limits of the analytics — heavy rain, strong backlighting, very small subjects at frame edges, densely crowded scenes. You need those before you write a spec sheet, not after your customer files a complaint.

Where to go next

Start an OEM conversation

Tell us: target market, expected annual volume, whether you need firmware branding, and which certifications you need to clear. We’ll come back with an MOQ, a lead time, and the certificate set.

Device integration follows the RTSP (RFC 2326) streaming standard, with hardware interfaces built to published IEEE standards, so OEM units drop into existing deployments without proprietary gateways.