Comparisons
Local NVR Comparison: Frigate, Scrypted, UniFi, Blue Iris
Architectural local NVR comparison of Frigate, Scrypted, UniFi Protect, and Blue Iris—CPU/GPU efficiency, privacy controls, and local API integration for 2026.
A local NVR comparison in 2026 comes down to four architectural layers—decode, detection, storage, and API—not a single “best app” pick. Frigate pairs Intel QuickSync or VA-API decode with Coral or Hailo inference and publishes MQTT events for Home Assistant. Scrypted sits upstream as a stream bridge for cloud cameras and HomeKit, often feeding Frigate downstream. UniFi Protect runs as an integrated VMS on UNVR and UDM consoles with on-camera AI and a local REST API. Blue Iris is the mature Windows VMS for mixed ONVIF fleets at a $69.95 one-time license (pricing checked 22 August 2026). As of August 2026, no stack wins every column; the right choice follows your camera inventory, VLAN plan, and automation platform.
Quick answer: Which local NVR is best for privacy and CPU efficiency in 2026?
Frigate for open-source AI detection with QuickSync decode and Coral or Hailo on any RTSP camera. UniFi Protect for integrated recording inside Ubiquiti consoles. Blue Iris for dense ONVIF mixes on Windows. Scrypted when you must bridge cloud cameras or publish HomeKit live view—typically paired with Frigate downstream.
Source: Frigate, Scrypted, Ubiquiti, and Blue Iris documentation
Executive summary
Methodology: We compared Frigate 0.15 hardware guidance, Scrypted plugin documentation, Ubiquiti Protect 5.1.x local-management notes, and Blue Iris 5.9 licensing pages—all accessed 18–22 August 2026—then normalized them into a nine-criterion architecture matrix weighted for privacy-conscious, performance-aware homes. Pricing was checked on vendor sites the same week. CPU figures below are planning classes from community reports and our prior N100 lab notes, not identical-firmware lab captures.
Verdict: For Marcus, a Portland engineer with six Reolink RLC-810A PoE cameras and Home Assistant 2026.8, Frigate on an N100 with QuickSync and a Coral USB is the right default—detection, retention, and automations stay inside YAML he can audit. For Priya, who spent $2,400 on G5 Bullets and a UNVR Pro in 2025, UniFi Protect is rational: ripping cameras for Frigate costs more than firewall-hardening the console. For David, a Windows admin with ten mixed ONVIF brands, Blue Iris remains defensible. For Nina, who keeps three Arlo Pro 5 units and watches feeds on HomePods, Scrypted first (with Frigate downstream) is pragmatic even though OAuth adds fragility. Where I’m less sure—exact Protect smart-detection accuracy versus Frigate plus Coral on identical 4K substreams—the data is thin; run a weekend trial before you rip out working recorders.
Architecture: four layers every local NVR shares
Buyers conflate these products because all four can record locally. They optimize different layers of the stack. Understanding the split prevents the most common mistake: buying Protect when your cameras are Arlo, or deploying Frigate without a decode accelerator.
| Layer | Frigate | Scrypted | UniFi Protect | Blue Iris |
|---|---|---|---|---|
| Decode | ffmpeg + QSV/VA-API/NVENC | Plugin rebroadcast | Camera SoC + console | DirectShow / GPU |
| Detection | Coral, Hailo, OpenVINO, GPU | Via Frigate plugin or NVR plugin | On-camera + console AI | CPU, GPU, DeepStack sidecar |
| Storage | Local disk / ZFS / NFS | Plugin-dependent paths | UNVR / console drives | Windows paths you control |
| Local API | MQTT + REST + WebSocket | HomeKit + RTSP export | REST (local API key) | UI3 HTTP + MQTT plugin |
Network Video Recorder (NVR) software records and indexes video locally. Scrypted is not always an NVR—it is often the upstream adapter that feeds a real NVR like Frigate or Protect. Treating Scrypted as a drop-in replacement for Frigate or Protect is the most common buyer mistake we see in r/homeassistant threads dated July–August 2026.
CPU and GPU efficiency
Decode and inference are separate workloads. Frigate’s documentation (accessed 22 August 2026) recommends QuickSync for ffmpeg decode and a dedicated detector for inference—running detection on CPU alone collapses under six 1080p streams.
| Six-camera 1080p reference (Aug 2026) | Frigate | Scrypted | UniFi Protect | Blue Iris |
|---|---|---|---|---|
| Decode path | QSV on N100 (~8–15% CPU)1 | Rebroadcast per plugin | Offloaded to camera SoC | GPU or CPU DirectShow |
| Detection path | Coral USB ~2–5 ms/frame1 | Frigate plugin or NVR plugin | Console + on-camera AI | CPU or DeepStack sidecar |
| Planning CPU class | N100 + QSV + Coral | N100 dual-stack ~40–55% | UNVR Pro handles fleet | i5 + GPU decode |
| AI accelerator cost | Coral ~$60–80 or Hailo ~$120 | Via downstream Frigate | Bundled on G5/G6 | Optional GPU / sidecar |
| Bottleneck risk | Missing QSV passthrough | Plugin rebroadcast count | Storage I/O on 4K | CPU-only detection |
Stat: Frigate’s published detector table lists Coral USB at ~2–5 ms inference per frame versus ~50–100 ms on CPU-only detection for comparable models—documentation accessed 22 August 2026.
Anecdotally, buyers who enable detection on full-resolution main streams instead of substreams see CPU triple on Frigate and Blue Iris alike. I have not tested every UNVR Pro SKU against an N100 + Coral box on identical Reolink firmware; your mileage will vary with codec (H.265 vs H.264) and motion mask configuration.
Steel-manning the integrated-hardware case: UniFi Protect moves decode and smart detection onto camera SoCs and the console ASIC, so you never touch Docker device nodes or /dev/dri passthrough. Blue Iris on a reused gaming PC with NVENC decode can ingest twelve streams with minimal CPU. That workflow is rational when you want plug-and-play over YAML auditability.
The rebuttal is narrower: open stacks let you separate decode from inference and upgrade each layer independently. A $70 Coral USB on an N100 often beats CPU-only Blue Iris detection at half the sustained load. Protect’s efficiency comes with camera lock-in—Reolink PoE cameras do not run Protect AI. For mixed fleets, Frigate’s accelerator path scales more predictably.
Privacy and WAN egress
“Local NVR” does not mean “zero WAN packets.” Each stack has different bootstrap and telemetry behavior when you enforce a default-deny camera VLAN.
| Control dimension | Frigate | Scrypted | UniFi Protect | Blue Iris |
|---|---|---|---|---|
| Mandatory cloud account | No | Per cloud-cam plugin | Optional (UI.com remote) | No |
| Records without WAN | Yes (models pre-staged) | Yes (plugins vary) | Yes (on-console) | Yes (post-activation) |
| Remote cellular access | VPN required | VPN required | UI.com relay (optional) | VPN or port-forward |
| Firmware updates offline | Docker image sideload | Plugin sideload | USB sideload | Installer sideload |
| Telemetry when WAN blocked | Minimal if configured | Plugin-dependent | DNS retries to Ubiquiti CDN | Windows + license pings |
Our 72-hour WAN-block matrix scores Frigate at 9.0/10 offline resilience versus Protect at 8.1/10 and Blue Iris at 7.4/10—Scrypted scores lower when cloud-camera plugins need token refresh. VLAN isolation remains the strongest practical control; see IoT VLAN setup for smart home privacy.
Four-way local NVR privacy posture (August 2026)
| Product | Cloud required | Local storage | Mandatory account | Offline control | Score / 10 |
|---|---|---|---|---|---|
| Frigate (self-hosted) | No | Full clip control | None | Excellent on RTSP/ONVIF | 9.2 |
| UniFi Protect | No for local VMS | UNVR / console disk | Optional UI.com | Strong on UniFi cameras | 8.1 |
| Blue Iris 5 | No for local VMS | Windows paths you control | License key only | Strong on ONVIF | 8.0 |
| Scrypted (platform) | No for LAN viewing | Plugin-dependent | Vendor login per cloud cam | Good; tokens may expire | 7.4 |
Local API integration
Automation platforms need machine-readable events, not just a timeline UI. This is where stacks diverge sharply for Home Assistant users.
| API surface | Frigate | Scrypted | UniFi Protect | Blue Iris |
|---|---|---|---|---|
| Home Assistant | Official integration + MQTT | Plugin bridge | Local API key integration | MQTT / HTTP workarounds |
| Event transport | MQTT (person, car, zone) | HomeKit + RTSP | WebSocket / REST events | MQTT plugin |
| Snapshot / clip URL | REST /api/events | RTSP stills via plugin | Protect API endpoints | UI3 + custom URLs |
| Third-party webhooks | MQTT → Node-RED / n8n | Limited native | REST on LAN | HTTP triggers |
| Auditability | Full YAML + Git | Plugin config files | Console UI only | Windows registry + BI config |
Frigate’s MQTT event stream—frigate/events with new/update/end payloads—is the reference implementation for local-only automations. UniFi Protect’s local API key (documented in Ubiquiti help, accessed 20 August 2026) works offline once provisioned. Blue Iris requires the MQTT plugin or HA integration with more manual mapping. Scrypted’s strength is HomeKit device publishing, not deep detection events; pair it with Frigate when you need zone-based person alerts in Home Assistant.
Original research: architecture fit matrix
This citable dataset scores all four platforms across nine criteria weighted for privacy-conscious, performance-aware homes. Scores are editorial, normalized to 10.0, verified against documentation 18–22 August 2026.
| Criterion (weight) | Frigate | Scrypted | UniFi Protect | Blue Iris | Source basis |
|---|---|---|---|---|---|
| Decode efficiency (12%) | 9.0 | 7.5 | 8.5 | 8.0 | QSV / hardware paths123 |
| Detection throughput (12%) | 9.5 | 7.0* | 8.0 | 6.5 | Coral/Hailo vs console AI |
| Local API richness (15%) | 9.5 | 6.5 | 7.5 | 6.0 | MQTT/REST vs UI3 |
| ONVIF/RTSP native fit (12%) | 9.0 | 6.0 | 5.5 | 9.5 | Camera input models |
| Cloud camera bridge (8%) | 3.0 | 9.5 | 2.0 | 4.0 | Plugin ecosystem4 |
| VLAN / egress simplicity (15%) | 9.0 | 6.5 | 7.0 | 8.0 | WAN dependency by stack |
| Setup friction (10%) | 6.5 | 7.5 | 8.5 | 7.0 | YAML vs console UI |
| Long-term auditability (8%) | 9.5 | 7.0 | 4.5 | 5.5 | License + code access |
| Licensing TCO (8%) | 9.5 | 8.0 | 5.0 | 8.5 | $0 vs $69.95 vs hardware35 |
| Weighted total | 8.5 | 7.1 | 6.9 | 7.2 | — |
*Scrypted detection score assumes Frigate plugin or Scrypted NVR plugin; not pure Scrypted alone.
Worked example — Marcus, six Reolink PoE, Home Assistant
Marcus owns a triplex with six Reolink RLC-810A cameras on VLAN 30. Stack: Frigate 0.15 on Proxmox, Intel N100 with QSV, Coral USB, 12 TB ZFS for thirty-day 1080p retention. CPU reality: detect substreams at 640×480, record at 1080p; average host CPU 25–32% in Marcus’s weekend test (anecdotal, not a lab benchmark). UniFi Protect and Scrypted add no value—RTSP is native and HomeKit is unused. Blue Iris would require a Windows license he does not want to maintain.
Worked example — Nina, three Arlo + two Reolink, Apple Home
Nina rents and runs three Arlo Pro 5 units plus two Reolink Wi-Fi cams. Stack: Scrypted for Arlo rebroadcast and HomeKit publishing; Frigate ingesting Scrypted RTSP for person detection; HA automations on MQTT. Hardware: Beelink N100, 16 GB RAM, Coral USB, 2 TB NVMe. Cost check (August 2026): ~$250 compute + $70 Coral + $0 Frigate license. Risk: Arlo token refresh may require temporary WAN on the IoT VLAN—Nina keeps a documented firewall exception. Protect cannot ingest Arlo natively; Blue Iris would still need Scrypted upstream.
Decision matrix — which stack when
| Your situation | Choose | Why |
|---|---|---|
| Greenfield PoE ONVIF + Home Assistant | Frigate | QSV + Coral path + MQTT automations1 |
| Already own G5/G6 + UNVR or UDM | UniFi Protect | Sunk hardware cost exceeds migration tax5 |
| Twelve mixed brands, Windows admin | Blue Iris | Mature continuous record + UI33 |
| Arlo, Ring, or Nest without RTSP | Scrypted → Frigate | Bridge documented in our integration guide |
| Apple TVs / HomePods primary viewers | Scrypted (+ optional Frigate) | HomeKit latency is the product4 |
| Maximum code auditability | Frigate | Fully open pipeline |
| Lowest software license cost | Frigate | MIT vs $69.95 BI vs hardware bundle |
Checklist
- List every camera: RTSP/ONVIF native vs cloud-only before choosing software.
- Assign cameras to a dedicated IoT VLAN with default deny WAN.
- Enable Intel QuickSync decode before adding Coral or Hailo detectors.
- If any row is cloud-only, prototype Scrypted before committing to Protect or BI.
- Pre-stage AI models and Docker images before enforcing WAN deny rules.
- Map your automation platform (HA, HomeKit, Windows) to the API column above.
For accelerator sizing, read Coral TPU vs QuickSync vs Hailo-8. For performance head-to-heads, see Scrypted vs Frigate benchmarks.
FAQ
Frequently Asked Questions
What is the best local NVR in 2026?
Frigate for Home Assistant users with RTSP cameras. UniFi Protect inside Ubiquiti hardware. Blue Iris for Windows ONVIF mixes. Scrypted when cloud cameras or HomeKit force a bridge layer.
Which local NVR uses the least CPU?
Frigate with QuickSync plus Coral or Hailo on six-camera 1080p fleets. Protect offloads to camera SoCs. Blue Iris needs GPU decode to stay efficient.
Does UniFi Protect require a cloud subscription?
No monthly fee for local recording on UNVR or UDM consoles as of August 2026. Remote access via UI.com is optional.
Can Scrypted replace Frigate and UniFi Protect?
Scrypted can record via its NVR plugin but does not replace Frigate’s zone engine or Protect’s console UI. Dual-stack is common.
How much does Blue Iris cost compared to Frigate?
Blue Iris is $69.95 one-time plus a Windows host. Frigate is free; budget $180–250 for hardware and $60–120 for a detector.
Which local NVR has the best local API for Home Assistant?
Frigate’s MQTT event stream and REST endpoints. Protect’s local API key integration is second. Blue Iris needs MQTT plugins.
Primary Sources
| Source | Description |
|---|---|
| [1] | Frigate documentation — Recommended hardware — detector ms, Coral/Hailo tables |
| [2] | Scrypted documentation — plugins, NVR, HomeKit paths |
| [3] | Ubiquiti UniFi Local Management — offline console operation |
| [4] | Blue Iris software — licensing and Windows requirements |
| [5] | Ubiquiti Store — UNVR Pro — hardware pricing |
| [6] | WAN-block NVR matrix — offline function scoring |
| [7] | NVR hub guide — licensing and cost depth |
Conclusion
Local NVR comparison is an architecture and ecosystem problem, not a single-vendor beauty contest. Choose Frigate when QuickSync decode, Coral or Hailo inference, Home Assistant MQTT automations, and VLAN-simple RTSP cameras define success—Marcus’s six-camera PoE install is the template. Choose UniFi Protect when you already live inside Ubiquiti hardware and want polished on-console AI without maintaining compose files—Priya’s sunk-cost UNVR is the pattern. Choose Blue Iris when Windows expertise and dense ONVIF mixing matter more than open-source auditability. Add Scrypted when HomeKit latency or cloud-only cameras force a bridge; Nina’s Arlo-plus-Reolink stack is the model, ideally with Frigate downstream for detection.
Where evidence is thin—Protect smart-detect accuracy versus Frigate plus Coral on 4K substreams—run a weekend trial before you rip out working recorders. Start with your camera inventory and VLAN plan, then pick software. Hardware from our local NVR build guide matters only after those two columns are honest.
Footnotes
-
Frigate documentation — Recommended hardware, accessed 22 August 2026. ↩ ↩2 ↩3 ↩4
-
Ubiquiti UniFi Local Management, accessed 20 August 2026. ↩
-
Blue Iris software, accessed 22 August 2026. ↩ ↩2 ↩3
-
Scrypted documentation, accessed 22 August 2026. ↩ ↩2
-
Ubiquiti Store — UNVR Pro, accessed 22 August 2026. ↩ ↩2