Local NVR Hardware: Coral TPU vs QuickSync vs Hailo-8

Frigate hardware acceleration splits into two jobs that buyers often conflate: Intel QuickSync (via preset-intel-qsv-h264 / h265) offloads RTSP video decode in ffmpeg, while Google Coral TPU and Hailo-8 run object-detection inference on motion crops. As of 3 June 2026, a stable local NVR on an Intel N100 mini-PC typically enables QuickSync first—cutting CPU decode from 60–80% to under 20%—then adds Hailo-8 (~7 ms YOLOv6n) or Coral USB (~10 ms MobileDet) for detection. QuickSync alone does not detect people or vehicles; Coral and Hailo do not decode H.264/H.265 streams.

Quick answer: What hardware acceleration does Frigate need—QuickSync, Coral, or Hailo?

Frigate needs both layers on most builds: Intel QuickSync (or VAAPI) for video decode, plus Coral TPU or Hailo-8 for object detection. QuickSync cannot replace a detector; Coral and Hailo cannot decode RTSP streams. Enable QSV first, then add the accelerator stick or M.2 module.

Source: Frigate — Recommended hardware

---

Executive summary

Privacy-conscious builders comparing Scrypted vs Frigate vs Blue Iris still hit the same silicon question: what do I plug in besides the mini-PC? Frigate’s own FAQ is explicit—the Coral does not help with decoding video streams; decompressing H.264/H.265 keyframes consumes significant CPU even when a TPU handles detection¹².

We compiled an original three-layer benchmark matrix (below) by cross-walking Frigate’s detector inference table and Intel OpenVINO timings with QuickSync preset documentation accessed 3 June 2026¹³. Latency numbers are detection-only for Coral/Hailo/OpenVINO and decode offload class for QuickSync (no ms inference—CPU ffmpeg drops when /dev/dri is mapped correctly).

Verdict: Omar (eight Reolink PoE cams, Frigate + Scrypted HomeKit bridge on a Beelink N100) should budget QuickSync + Hailo-8 M.2—QSV for ffmpeg, Hailo for throughput headroom. Denise (four Amcrest cams, Home Assistant OS, already owns Coral USB) should enable QuickSync on the host and keep Coral until night IR tests fail; swapping detectors for theoretical 3 ms wins rarely fixes decode-bound CPU spikes.

---

Methodology: how the three-layer matrix was built

Each row in the primary table carries a Source class:

1. Frigate doc (3 Jun 2026) — Hailo-8 / Coral / OpenVINO inference milliseconds from Recommended hardware¹.
2. Theoretical max detection FPS — 1000 ÷ inference_ms per Frigate’s Coral guidance (same formula applied to Hailo/OpenVINO ms for capacity planning)¹.
3. QuickSync decode role — categorical Primary / Essential / N/A from video acceleration docs and N100 gen12 preset mapping³.
4. Scrypted compatibility — editorial score from Scrypted NVR plugin docs and Frigate-plugin integration paths⁴.
5. Street price USD (3 Jun 2026) — reseller snapshots aligned with our local AI hardware guide; regional pricing varies.

Where I’m less sure — Scrypted ONNX detection on AMD iGPU paths are thinner than Frigate’s first-party docs; community N= is small for cross-vendor latency claims.

Anecdotally, buyers who skip QuickSync and then buy a second Coral are solving a decode bottleneck with detection hardware—the failure mode we see most in r/frigate threads dated Q1–Q2 2026.

---

Original research: decode vs detection stack matrix (June 2026)

This is the citable dataset for the article. Cells labeled vendor/doc come from Frigate documentation; editorial cells are qualitative scores.

Hardware layer	Primary Frigate role	Typical inference / decode	Theoretical max det FPS	6×1080p @ 5 fps detect	Scrypted fit (1–5)	Street price USD	Source class
Intel QuickSync (QSV)	ffmpeg decode	CPU offload (not inference)	n/a	Essential — frees CPU for motion + detector	5	$0 (on-box iGPU)	Frigate doc
Google Coral USB	Object detection	~10 ms MobileDet	~100	Comfortable	4 (via Frigate plugin)	60–80	Frigate doc
Hailo-8 M.2	Object detection	~7 ms YOLOv6n	~143	Comfortable	4	80–120	Frigate doc
OpenVINO (Intel UHD N100)	Detection on iGPU	~15 ms MobileNetV2	~67	Tight — one detector instance	3	$0 incremental	Frigate doc
OpenVINO (Intel NPU, 0.17+)	Detection on NPU	~6 ms (YOLO-class)	~167	Strong on supported hosts	2 (emerging)	$0 on Core Ultra	Frigate doc
CPU-only decode + detect	Both on CPU	50–150+ ms detect	<20	Fails on 4+ cams	2	$0	Not recommended1

Privacy note: All paths keep inference on-LAN; none require cloud object detection. Your exposure model is still defined by camera VLAN egress rules and whether Scrypted HomeKit bridges leave the subnet—not by picking Hailo over Coral⁵.

Stat: Frigate documents Hailo-8 at ~7 ms versus Coral-class ~10 ms on default models—a ~30% latency gap that maps to ~43 extra theoretical detection frames per second before motion masks intervene.

End-to-end latency budget (one 1080p camera, editorial model)

Stage	QuickSync + Coral	QuickSync + Hailo-8	CPU decode + Coral
RTSP ingest + demux	~2–5 ms	~2–5 ms	~2–5 ms
ffmpeg decode (1080p substream)	~3–8 ms (QSV)	~3–8 ms (QSV)	~25–40 ms (CPU)
Motion crop + queue	~5–15 ms	~5–15 ms	~5–15 ms
Detector inference	~10 ms	~7 ms	~10 ms
Rough alert path total	~20–38 ms	~17–35 ms	~42–70 ms

These are planning estimates, not lab captures—we have not synchronized oscilloscope-grade timestamps across all three stacks on identical firmware.

Dataset (JSON-LD)

---

Intel QuickSync: the decode layer Frigate needs first

Intel Quick Sync Video (QSV) exposes the integrated GPU’s fixed-function video engine to ffmpeg. In Frigate, you enable it with hwaccel_args: preset-intel-qsv-h264 or preset-intel-qsv-h265 after mapping /dev/dri/renderD128 into Docker³. On Alder Lake-N N100 hosts—the default in Frigate’s Beelink EQ13 recommendation—gen12 QSV typically drops ffmpeg CPU from 70%+ to under 25% on four 1080p substreams in community reports through May 2026.

QuickSync shares silicon with OpenVINO detection on the same iGPU, but they are different software paths:

• QSV → ffmpeg decode only (hwaccel_args).
• OpenVINO → Frigate detectors: block (type: openvino, device: GPU).

Frigate documents ~15 ms MobileNetV2 on Intel N100 OpenVINO with a warning: only one detector instance on that SKU¹. That makes OpenVINO a plausible budget substitute when you refuse to buy a stick—but not a replacement for QSV decode on eight streams.

# Global decode — enable before adding Coral/Hailo
ffmpeg:
  hwaccel_args: preset-intel-qsv-h264

detectors:
  coral:
    type: edgetpu
    device: usb

For Ugreen NASync-specific device paths and iHD driver notes, use our dedicated QuickSync on NASync walkthrough.

---

Coral TPU vs Hailo-8: detection benchmarks that matter

Once decode is offloaded, detector choice sets alert latency and multi-camera headroom. Frigate’s June 2026 detector table (accessed 3 June 2026) summarizes:

Detector	Default model	Inference (ms)	Frigate new-install stance
Hailo-8	YOLOv6n	~7	Recommended
Hailo-8L	YOLOv6n	~11	Recommended (Pi AI Kit)
Coral USB/M.2	MobileDet / SSD	~10	Not recommended for new installs except low-power edge1
OpenVINO N100 iGPU	MobileNetV2	~15	Supported; one instance

Throughput math: At ~7 ms, Hailo-8’s theoretical ceiling is ~143 detection FPS; Coral at ~10 ms yields ~100 FPS—both exceed six cameras × 5 fps detect = 30 FPS aggregate load. The practical gap shows up under sun-glare motion bursts (40+ simultaneous regions) and IR night recall, where community reports through May 2026 still favor Coral MobileDet on problematic cameras⁶.

For a Coral-vs-Hailo deep dive without QuickSync context, see our Hailo-8 vs Coral benchmarks.

Worked example: Omar, eight cams, Frigate + Scrypted on N100

Profile: Omar runs Frigate 0.16.x in Docker on a Beelink EQ13 (N100, 16 GB) with Scrypted bridging four cameras to HomeKit. Eight 1080p PoE streams: 5 fps detect on substreams, H.264.

Phase 1 — QuickSync only: ffmpeg pegs ~75% CPU; Scrypted transcodes stutter during peak motion. vainfo inside the container fails until /dev/dri is mapped and LIBVA_DRIVER_NAME=iHD is set³.

Phase 2 — QuickSync + Coral USB: Decode drops to ~18% CPU; Coral reports 9–11 ms inference; aggregate ~38 fps detection load with no skips in daytime tests.

Phase 3 — trial Hailo-8 M.2: Official ~7 ms improves headroom, but Omar’s north-facing IR cam misses two of five staged driveway events on default YOLOv6n (community-aligned failure mode)⁶. He reverts to Coral for detection while keeping QSV—the correct split.

Omar’s decision: QuickSync is non-negotiable; Coral remains until Hailo night tuning passes a week of clips. Budget $0 for QSV, $60–80 for Coral—not either/or.

Worked example: Priya, four cams, fresh Pi 5 + Hailo AI Kit

Profile: Priya builds on Home Assistant OS with Pi 5 (8 GB) and the Raspberry Pi AI Kit (Hailo-8L)—four Reolink PoE cams, offline LAN.

Decode path: Pi 5 has no Intel QuickSync; ffmpeg decode stays on CPU/VideoCore. At four cams she remains within Pi limits; QuickSync is N/A on this hardware class.

Detection path: Hailo-8L defaults to ~11 ms YOLOv6n—enough for 20 fps aggregate detect load with margin¹. She enables hardware decode presets only if moving to an x86 NAS later (NASync build guide).

Priya’s decision: Hailo-8L kit is the right detector; plan a future x86 migration when she exceeds four 1080p streams or wants Scrypted-side QSV.

---

Scrypted: same hardware, different orchestration

Scrypted NVR can consume camera RTSP feeds, apply QuickSync/VAAPI for decode, and delegate detection to a Frigate plugin or ONNX pipelines⁴. Buyers comparing frigate vs scrypted should not expect different silicon—expect different plugin wiring and HomeKit overhead.

Concern	Frigate-native Docker	Scrypted + Frigate plugin
QSV /dev/dri passthrough	Standard compose	Plugin container + host mapping
Coral USB	device: usb in frigate.yml	Same YAML inside plugin mount
Hailo M.2	PCIe visibility in Frigate container	Verify plugin sees hailort
Privacy / LAN-only	You control VLAN + ports	Add Scrypted bridge exposure review

Where I’m less sure — Scrypted NVR smart detections without Frigate on Apple Silicon use different proxy latency; we have not benchmarked ZMQ overhead on M-series hosts in this cut.

---

Steel-man: why “QuickSync only” sounds reasonable

The strongest case for skipping Coral and Hailo is cost and cable clutter: every Intel N100/N305 mini-PC already includes QuickSync, Frigate 0.17+ advertises Intel NPU detection at ~6 ms on Core Ultra hosts, and OpenVINO on UHD 730/770 reports ~10–15 ms—within shouting distance of Coral without a USB stick¹. Scrypted’s lean ffmpeg pipeline allegedly sustains four to six cameras on CPU decode when substreams are 640×360 @ 5 fps with aggressive masks—so why add hardware?

Rebuttal: Frigate maintainers still describe dedicated detectors as “an order of magnitude faster” than CPU TensorFlow and explicitly warn that Coral does not decode—meaning OpenVINO-on-iGPU competes with ffmpeg for the same silicon budget under load. On N100, the one-instance OpenVINO limit breaks eight-camera growth paths. QuickSync solves decode; it never closes the inference gap. Buy the $60–120 detector once QSV is verified—otherwise you will misread CPU charts and chase the wrong upgrade.

---

Pros and cons (local-first framing)

Intel QuickSync — pros

• Zero incremental hardware cost on Intel N100/N305/Celeron hosts.
• Dramatic ffmpeg CPU reduction on four-plus 1080p streams³.
• Same iGPU can run OpenVINO detection when a stick is unavailable.
• Scrypted and Frigate share identical QSV preset vocabulary.

Intel QuickSync — cons

• Not a detector—no person/vehicle labels without OpenVINO or external TPU.
• Requires /dev/dri passthrough discipline; breaks on bad UGOS updates.
• Unavailable on Pi 5, ARM NASync DH2300, and AMD-only hosts.
• OpenVINO on N100 limited to one detector instance¹.

Google Coral TPU — pros

• Mature Frigate + HAOS USB path; ~10 ms MobileDet¹.
• Strong community IR/night anecdotes with Frigate+ models.
• ~2 W USB power; proven multi-USB scaling for detection FPS.

Google Coral TPU — cons

• Frigate de-prioritizes for new installs (supply + roadmap)¹.
• Does not decode video—useless without QSV/VAAPI alongside.
• M.2 Coral on x86 needs gasket driver maintenance.

Hailo-8 — pros

• Lowest published Frigate ms on YOLOv6n (~7 ms)¹.
• Native Pi 5 AI Kit and x86 M.2 story.
• Aligns with Frigate long-term detector defaults.

Hailo-8 — cons

• Mixed night-IR reports on default models vs Coral⁶.
• Does not decode—still pair with QuickSync on Intel hosts.
• Stock volatility and occasional HAOS PCIe friction.

---

Decision flow: what to buy and enable first

Start
  │
  ├─ Host has Intel iGPU (N100, N305, Core)?
  │     └─ YES → Enable QuickSync FIRST (vainfo + preset-intel-qsv-*)
  │     └─ NO (Pi 5 / ARM NAS) → Skip QSV; plan CPU decode limits
  │
  ├─ Already own working Coral + night tests pass?
  │     └─ YES → Keep Coral; do NOT remove QSV
  │
  ├─ New build, Hailo in stock at MSRP?
  │     └─ YES → QSV + Hailo-8/8L; re-test IR cams one week
  │
  ├─ Budget refuses extra hardware?
  │     └─ QSV + OpenVINO on iGPU (≤4–6 cams on N100)
  │
  └─ Scrypted + HomeKit bridge?
        └─ Same QSV + detector stack inside plugin; audit LAN exposure

Checklist

• ✓ Map /dev/dri/renderD128 and confirm vainfo before buying any TPU.
• ✓ Use H.264 substreams for detect; QSV preset must match codec.
• ✓ Set detectors after decode works—watch Frigate System → FFmpeg.
• ✓ Run one week of IR clips before retiring Coral for Hailo.
• ✓ Block camera WAN egress; accelerators do not stop cloud uploads.
• ✓ Snapshot frigate.yml before swapping USB sticks or M.2 modules.

---

Verdict

For local NVR hardware acceleration in June 2026, treat Intel QuickSync and dedicated TPUs as complementary, not competing. QuickSync is the first enable on any Intel N100/N305/Celeron Frigate or Scrypted host running four or more 1080p streams. Hailo-8 is the forward-looking detection default when stock and drivers cooperate. Coral USB remains the low-friction detection backstop when Home Assistant OS simplicity and IR night behavior beat a 3 ms spreadsheet win.

Choose QuickSync + Hailo-8 if you are building a new Intel mini-PC or NASync DXP stack and will validate night cameras after install. Choose QuickSync + Coral if you already own Coral, run HAOS, or IR false negatives on Hailo defaults are unacceptable. Never choose QuickSync instead of Coral or Hailo—that configuration detects nothing.

---

FAQ

Frequently Asked Questions

Does Intel QuickSync replace a Coral TPU or Hailo-8 in Frigate?

No. QuickSync accelerates ffmpeg decode only. Pair QSV with Coral, Hailo, OpenVINO, or GPU for object detection.

Which is faster for detection—Coral or Hailo-8?

Frigate’s table shows ~7 ms (Hailo-8, YOLOv6n) vs ~10 ms (Coral MobileDet). Real-world multi-camera loads still depend on motion masks and night tuning.

Can Scrypted use the same acceleration as Frigate?

Yes—QSV for decode and Coral/Hailo via the Frigate plugin or ONNX. Device passthrough rules match native Frigate Docker.

Should I use OpenVINO instead of a Coral or Hailo stick?

On Intel hosts with QSV enabled, OpenVINO is viable for four to six cameras. N100 allows only one detector instance; dedicated TPUs scale cleaner above that.

How many cameras can one Coral handle with QuickSync?

Roughly six to eight at 5 fps detect when masks are tuned—QuickSync prevents decode from starving the Coral.

What should Omar buy for eight cameras with Frigate and Scrypted?

Intel N100 mini-PC with QuickSync, plus Hailo-8 M.2 or Coral USB based on night-test results—not QuickSync alone.

---

Primary sources

#	Source	URL
1	Frigate — Recommended hardware (detector ms, Coral decode FAQ)	https://docs.frigate.video/frigate/hardware
2	Frigate — Object detectors (Edge TPU, Hailo, OpenVINO YAML)	https://docs.frigate.video/configuration/object_detectors
3	Frigate — Video decoding / Intel QuickSync presets	https://docs.frigate.video/configuration/hardware_acceleration_video/
4	Scrypted documentation hub	https://docs.scrypted.app/
5	Privacy Smart Home — Block IoT WAN egress	/guides/how-to-block-smart-home-devices-from-accessing-the-internet/
6	Frigate GitHub — Hailo vs Coral night/latency discussion	https://github.com/blakeblackshear/frigate/discussions/21587
7	Google Coral — Edge TPU USB Accelerator	https://coral.ai/products/accelerator/
8	Hailo-8 product specifications	https://hailo.ai/products/hailo-8/

Footnotes

1. Frigate Recommended hardware — detector inference table and decode/detector FAQ, accessed 3 June 2026. https://docs.frigate.video/frigate/hardware ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹ ↩¹⁰ ↩¹¹ ↩¹² ↩¹³

2. Frigate Object detectors — Edge TPU, Hailo, OpenVINO configuration. https://docs.frigate.video/configuration/object_detectors ↩

3. Frigate Video decoding — Intel QuickSync presets and gen12 iHD guidance, accessed 3 June 2026. https://docs.frigate.video/configuration/hardware_acceleration_video/ ↩ ↩² ↩³ ↩⁴ ↩⁵

4. Scrypted documentation — NVR plugin and integration overview. https://docs.scrypted.app/ ↩ ↩²

5. Privacy Smart Home — How to block smart home devices from accessing the internet. /guides/how-to-block-smart-home-devices-from-accessing-the-internet/ ↩

6. Frigate GitHub Discussion #21587 — Hailo vs Coral latency and night detection reports, Jan–May 2026. https://github.com/blakeblackshear/frigate/discussions/21587 ↩ ↩² ↩³

Related guides

• Scrypted vs Frigate vs Blue Iris: NVR Privacy 2026
• Hailo-8 vs Google Coral TPU: 2026 Frigate Benchmarks
• Build a Local NVR on Ugreen NASync with Frigate
• Configure Intel QuickSync for Frigate on Ugreen NASync