The open-source NVR alternative.
Evaluating OpenNVR against Frigate, ZoneMinder, Verkada, Shinobi, or Viseron? We try to be honest about what each one does well — bashing competitors makes for poor positioning and worse engineering. OpenNVR solves a specific problem: auditable, offline-first AI surveillance with operator-controlled models. Here's where it fits and where it doesn't.
OpenNVR vs Frigate
Choose Frigate if
Home Assistant is your control plane, the shipped capability set (detection, face, LPR, CLIP search) covers your needs, and your security posture is “TLS optional, behind my home firewall.” Frigate’s HA integration and Coral / TensorRT polish are years ahead today.
Choose OpenNVR if
You need a published adapter contract so AI can ship outside the main repo under any licence (including proprietary or classified), an end-to-end audit chain for compliance, or a threat model where the vendor’s cloud is part of the attack surface. New AI capabilities land as standalone containers, not in-tree merges.
OpenNVR vs ZoneMinder
Choose ZoneMinder if
You have a working ZoneMinder deployment and no AI, audit, or sovereignty pressure that justifies migrating. Twenty years of operational maturity and the broadest camera compatibility anywhere.
Choose OpenNVR if
You’re starting fresh, the existing posture won’t survive your next compliance audit, or you need AI that ZoneMinder’s plugin model doesn’t reach. OpenNVR is built around the security-by-default thinking that emerged after Mirai and Verkada.
Open-source Verkada alternative
Choose Verkada if
Your buyer wants a SaaS commercial relationship and your threat model genuinely doesn’t include vendor-side compromise.
Choose OpenNVR if
Your threat model includes vendor-side compromise — the 2021 Verkada breach exposed ~150,000 cameras through one credential compromise — or your compliance environment requires customer-managed keys, or you’re replacing FCC Covered List equipment and don’t want to swap one centralised cloud vendor for another. With OpenNVR nothing leaves your hardware by default.
OpenNVR vs Shinobi
Choose Shinobi if
You want a polished commercial-support relationship with a smaller vendor and your AI needs fit Shinobi’s existing integrations.
Choose OpenNVR if
Your AI needs are non-standard, your compliance auditor wants an architectural paper trail, or you want a fully open Apache-2.0 SDK so you can ship adapters under any licence.
OpenNVR vs Viseron
Choose Viseron if
You want a small, readable, Python-native NVR with a clean detector abstraction and Home Assistant alignment. Viseron deserves more attention than it gets.
Choose OpenNVR if
You need the security, audit, or sovereignty controls that aren’t Viseron’s design centre — the correlation-ID audit chain, model-fingerprint drift detection, the default-deny sovereignty gates — or the broader contract-driven AI scope.
What's different about OpenNVR
Five things set OpenNVR apart from every NVR above, open-source or commercial: a published Open Adapter Contract so any model behind an endpoint becomes a first-class detector under any licence; an end-to-end audit chain with sha256 model-fingerprint drift detection; two independent default-deny sovereignty gates (`DEPLOYMENT_MODE=offline`, `AI_SOVEREIGNTY=local_only`); a peer-reviewed architecture paper (DOI 10.5281/zenodo.17261761); and a voice agent — you can literally ask your cameras what they see.
OpenNVR is v0.1 and honest about its gaps: the web UI, hardware-accelerated detection coverage, and Home Assistant depth all trail the mature projects. The bet is that the audience for whom the audit chain and sovereignty matter is large and underserved.