A one-time setup fee covering the Hive and its remote configuration, then a monthly subscription per site. You plug the unit in yourself — it takes about ten minutes and needs one free switch port. Adding a camera inside your stream count does not change what you pay.
Paid once, at the start. It covers the Nexovia Hive itself and the remote configuration that follows: camera discovery and credentialing, drawing your zones, setting schedules, and building the escalation chain. We do that over the tunnel once the unit is online.
Charged per site, not per camera. It covers the console and mobile app, alert delivery, the encrypted tunnel, event storage, ongoing model and firmware updates, and support. When we ship a new detection class, sites already on subscription get it without a truck roll and without a new quote.
We do not send an engineer to site. The Hive ships to you and someone on your end plugs it in — a free port on your existing switch and a power outlet. It is one cable and roughly ten minutes, and it does not need to be done by a specialist.
From the moment it comes online we take over remotely: discovery, zones, schedules, rules and escalation are all configured over the tunnel. If you would rather have someone physically do the install, your usual security installer or IT contractor can, and they bill you directly for that.
Pick the tier that covers your camera count. Every plan includes the same core detection engine — the difference is how many streams one Hive carries and how many sites you run.
Exact figures depend on your camera count, stream resolution, the detection classes you need and how many sites you run. We quote after looking at your camera list — not before.
Discovery, zones, schedules, rules and the escalation chain, all set up over the tunnel. Part of the initial fee, not a separate professional-services line.
Every dwell time, zone and confidence threshold is yours to adjust in the console. Support is on the subscription if you want a second opinion on a setting.
New and improved detection classes deploy over the tunnel to sites already running. No new hardware, no revisit, no new quote.
Every user at your site, on mobile and web. We do not charge per seat for the people who have to respond to the alerts.
| Starter | Business | Multi-Site | |
|---|---|---|---|
| Camera streams per Hive | Up to 4 | Up to 16 | 32+ |
| Sites per account | 1 | 1 | Unlimited |
| Theft & concealment | ● | ● | ● |
| Fall detection | ● | ● | ● |
| After-hours presence | ● | ● | ● |
| Loitering & zone breach | ● | ● | ● |
| Cross-camera person tracking | — | ● | ● |
| Plain-English event search | — | ● | ● |
| Pilot & roadmap classes | — | ● | ● |
| Escalation chains | Basic | Full | Full |
| Webhooks | — | ● | ● |
| API access | — | — | ● |
| Role-based access control | — | Basic | Per site |
| Custom model classes | — | On request | ● |
| Support | Standard | Priority | Named contact |
| Model & firmware updates | ● | ● | ● |
| Remote configuration | ● | ● | ● |
Because there is real hardware behind it. The Hive is a physical GPU appliance, and the configuration work that follows — discovering your cameras, drawing zones, setting schedules, building the escalation chain — is real time even though we do it remotely. We would rather charge for that once, honestly, than pretend it is free and recover it through a higher monthly rate for the next five years.
No, and that keeps the fee down. The Hive ships to you and someone on your end plugs it into a spare port on your switch and into power. That is the whole physical job — one cable, about ten minutes, no specialist needed. Once it is online we do everything else remotely over the tunnel. If you would rather not touch it at all, your usual security installer or IT contractor can do the physical side and bill you directly.
Not within your stream count. If you are on a 16-stream Hive and running 11 cameras, camera 12 costs you nothing extra per month. You only move up when you exceed the streams your Hive carries, at which point you either move to a larger Hive or add a second one.
No, and that is the whole point of the product. If your cameras produce an RTSP or ONVIF stream — effectively all IP cameras do — the Hive reads them as they are. No firmware changes, no re-cabling, no new mounts. Your existing NVR keeps recording exactly as it does today.
Detection keeps running. Inference, rule evaluation and local clip sealing all happen on the Hive, inside your building, so an outage does not blind the system. What you lose while the link is down is remote viewing and push delivery — those queue locally and sync when the connection returns.
Continuous recording stays with your NVR, on your site. The Hive holds short sealed clips tied to events on local storage. What goes to the cloud is account, site and device records plus event metadata — the things the console and app need to work. Raw video is not shipped off site in order to be analyzed.
Terms are agreed as part of the quote and depend on the tier and site count. Talk to us about what suits your situation rather than assuming the answer — we would rather structure something you are comfortable with than lock you into a shape that does not fit.
Yes — send us footage from your own cameras, ideally your worst angle, and we will run it through a Hive and show you exactly what it flags and what it misses. That is a far better test than a demo on our footage, because our footage was never going to be the problem.
Multi-Site puts every location under one account with role-based access per site, so a store manager sees their store and you see all of them. Each physical site still needs its own Hive — the compute has to be where the cameras are — but the subscription moves to a volume rate rather than a full price per location.
No. Everyone at your site who needs the app or the console gets access. Charging per seat would mean charging you to have more people able to respond to an alert, which is backwards.
Make, model and count. We will size the Hive, tell you which angles are worth having expectations about, and quote both parts properly.
