Government · defence · critical infrastructure · regulated

For sites that cannot hand their cameras to a vendor.

OpenNVR sits between your cameras and everything downstream: it records, streams and runs AI on your hardware, air-gapped if you need, refuses cloud routes by default, and proves all of it with evidence an auditor can check. Compliant cameras you already own keep working; covered-list cameras get a path out.

The problem

Covered-list vendors

Cameras from vendors restricted under the Secure Networks Act and NDAA §889 for government, public-safety and critical-infrastructure use.

Unmaintained firmware

Devices that stopped receiving updates years ago, with high-severity CVEs still open on production networks.

Vendor-cloud-bound

Feeds, recordings and analytics routed through a vendor's cloud — the architecture behind the 2021 Verkada breach that exposed about 150,000 cameras in one credential compromise.

OpenNVR works with any ONVIF or RTSP camera, re-streams over TLS through a gateway you control, and keeps recording, playback and AI on your hardware, so a camera's flaws stop at the camera.

Covered-list cameras are the exception. NDAA §889 is about the manufacturer, so no isolation makes a covered camera compliant; it has to be replaced. OpenNVR is the recorder you replace first: it finds the covered cameras in your inventory, keeps them isolated on a network with no route out while they remain, and records the compliant cameras that replace them, on your schedule and your budget.

Do you know what is on your camera network?

Most organisations cannot answer that with evidence: restricted hardware sold under other names, firmware years out of date, cameras reachable from the internet. OpenNVR Scout is a read-only scan that identifies every camera, checks each one, and gives the estate one posture grade.

What you can prove, not just claim

An evidence pack, on demand

One read-only command asks your deployment the questions an auditor asks and writes the answers into a zip: posture, the camera security check, recording coverage against retention, every AI model's fingerprint and declared network reach, every app's signer and reach, firewall rules and the audit log. Each check is marked PASS, ATTENTION or UNKNOWN, mapped to your framework, and hashed so the pack is tamper-evident.

An audit chain from alert to model

Every alert carries a correlation ID through the middleware to the model that ran, its weights' SHA-256, the operator who provisioned the camera and the transport policy in force.

§889 in the inventory

The built-in security check flags covered-list cameras. OpenNVR Scout is the formal assessment: OEM-rebrand resolution, CVE cross-reference and a signed report.

A camera network that stays dark

Two network cards: cameras on a network with no gateway and no route out, people and updates on the other. The management side can be sealed or online; either way the cameras never touch the internet.

Not just offline

USB sticks, maintenance laptops, insiders, tampered models and unsigned updates all reach isolated systems. Roles and MFA, the audit log, model fingerprints, signed app images and confined apps answer each.

A published architecture

The design is a peer-citable paper synthesising 34 sources — CISA advisories, NVD CVEs, the Verkada breach, Mirai — and every section maps to code.

Maps onto the frameworks compliance officers ask about:

  • CISA Secure by Design
  • NIST CSF 2.0
  • NIST AI RMF 1.0
  • ISO/IEC 27001:2022
  • SOC 2
  • IEC 62443
  • ETSI EN 303 645
  • HIPAA
  • EU GDPR
  • India DPDP Act 2023

The control-by-control mapping is in COMPLIANCE.md; the paper is DOI 10.5281/zenodo.22804254.

Your AI, your doctrine, your hardware

What you watch for, how you weigh it and what triggers escalation is operationally sensitive. It should not live in a vendor's cloud or on a vendor's roadmap. Every analytic in OpenNVR is a container behind one open contract, running on your hardware: a perimeter classifier trained on your terrain, a tamper detector trained on your substation cabinets, a restricted-area rule your safety committee wrote.

The SDK is Apache-2.0, so your models and apps can ship under any licence your programme requires, including proprietary or classified. Under the default local_only policy, any model that declares network access is refused registration outright.

What an engagement includes

Deployment on the reference appliance

We size the site, specify or validate the hardware, install on your network and hand over with the hardening checklist complete and the first evidence pack all-pass. Air-gapped installs are the normal case: images arrive on media.

Compliance evidence, reviewed

The evidence pack annotated against your control framework, with the control mapping, audit-log queries and runbooks an auditor asks for, on your audit cycle.

§889 attestation

For procurement that must show no covered-vendor equipment: a Scout assessment and a signed report.

Support with response times

Named severities, defined response and resolution windows, a private disclosure path and an upgrade cadence agreed with your change board.

Custom AI that stays yours

Adapters for models you cannot share, built under NDA and delivered as containers you own; fine-tuning on footage that never leaves the site; apps for your workflow, open or private.

Architecture review and training

A named reviewer signs off the integration with your network, identity and SIEM; a half-day operator track and a two-day developer track.

What it never includes: a private fork, a feature only paying customers get, or a cloud service holding your video. Every capability lands in the open-source main branch.

How it is priced

Per site, per year, sized by appliance tier and support level. Custom AI and Scout assessments are scoped work.

The software itself is free to self-host under the AGPL. Send the site's shape — cameras, retention, AI, network — and the framework you report under; a scoping call follows, including "you do not need us" when a community deployment will do.

What it doesn't do

  • It does not replace your cameras. It isolates them behind middleware you control; device firmware CVEs remain the vendor's to patch.
  • It does not provide hardware tamper detection. Locked racks, port security and tamper alarms are operator controls.
  • It does not stop an insider with physical access to the camera network; isolation reduces that surface, it does not remove it.
  • It does not defend against hardware implants in the cameras themselves, a residual risk the paper names.

Start with your site's shape

Procurement, licensing and SLA-backed support go to contact@opennvr.org. Security questionnaires, MSAs and vendor onboarding go through the same address. Technical questions are welcome in GitHub Discussions.