Home Builds Best Frigate Server Build 2026: NVR Hardware for AI Object Detection

Best Frigate Server Build 2026: NVR Hardware for AI Object Detection

Best Frigate Server Build 2026: NVR Hardware for AI Object Detection

Introduction

If you are building a security camera system that actually understands what it sees—distinguishing a person from a falling leaf at 3 AM—you need a Frigate server built for AI object detection. The right hardware choice, particularly between a Google Coral TPU, an Intel CPU with Quick Sync, or a dedicated NVIDIA GPU, determines whether your system runs reliably on 15 watts or requires a 300-watt power budget. This guide covers three build tiers for 2–4 cameras, 6–10 cameras, and 10+ camera setups, with exact hardware picks, storage sizing, and network planning so you can make a confident purchase today.

Frigate Hardware Requirements: Why CPU-Only Detection Fails Past 2 Cameras

Frigate offloads object detection from the main CPU to a dedicated accelerator. Running detection purely on a modern CPU like an Intel i5-12400 might handle one or two 1080p streams at 5–10 frames per second (FPS), but add a third stream and inference latency spikes past 100ms, causing missed detections and high CPU load (often 70–90%).

For anything beyond a single test camera, you need either a Google Coral TPU, an Intel processor with integrated graphics (Quick Sync), or a discrete NVIDIA GPU. The accelerator handles the neural network inference—the actual “is that a person or a shadow?” math—while the CPU manages stream decoding, recording, and the web interface.

5–15WCoral TPU Power Draw
15–30WIntel Quick Sync (iGPU) Power
75–200WNVIDIA GPU (e.g., P4, T4) Power

Google Coral TPU vs GPU Detection: Core Trade-Offs

The Google Coral TPU (a USB or M.2 accelerator) is the most power-efficient and cost-effective option for Frigate. It delivers about 4 TOPS (trillions of operations per second) per chip, enough for 6–8 camera streams at 5 FPS detection. A dual-Coral setup can handle 12–16 streams. The catch? Coral availability fluctuates, and it only handles inference—it cannot decode video streams.

GPU-based detection (using Intel Quick Sync or an NVIDIA card) combines stream decoding and inference in one device. Intel Quick Sync on a 12th-gen or newer i3/i5 handles 4–6 streams with decent accuracy, while an NVIDIA GTX 1650 or Tesla P4 can manage 10+ streams but draws significantly more power.

Coral TPU Pros

  • Ultra-low power (5–15W)
  • Dedicated inference, low latency
  • Supports 6–8 streams per chip
  • USB plug-and-play setup

Coral TPU Cons

  • Cannot decode video streams
  • Availability can be spotty
  • Single-chip bottleneck for 10+ cameras
  • Requires separate decoding hardware

GPU (Quick Sync/NVIDIA) Pros

  • Combines decode + inference in one chip
  • Handles 10+ streams easily
  • Better for high-resolution (4K) streams
  • Widely available

GPU (Quick Sync/NVIDIA) Cons

  • Higher power draw (75–200W for NVIDIA)
  • More complex driver setup
  • Intel Quick Sync limited to ~6 streams
  • NVIDIA requires docker driver install
Expert Note:

For a 6–10 camera build, a single Coral TPU paired with an Intel CPU (for decoding) is the sweet spot. It keeps total system power under 40W while handling detection lag-free. Only jump to an NVIDIA GPU if you exceed 10 cameras or need 4K resolution at 15+ FPS detection.

RAM and Storage Scaling by Camera Count

Frigate uses RAM for event buffers and decoded frames. For 2–4 cameras, 8GB of RAM is sufficient; for 6–10 cameras, 16GB is recommended; for 10+ cameras, 32GB ensures smooth operation, especially if you run additional services like Home Assistant alongside Frigate.

Storage is the bigger variable. Each camera recording 24/7 at 1080p with H.265 encoding consumes roughly 50–100 GB per day. At 4K, that jumps to 150–300 GB per day. Retention periods scale linearly—30 days of footage for four 1080p cameras requires about 6–12 TB.

Camera Count Resolution Daily Storage (H.265) 30-Day Storage
2 cameras 1080p 100–200 GB 3–6 TB
4 cameras 1080p 200–400 GB 6–12 TB
6 cameras 1080p 300–600 GB 9–18 TB
8 cameras 4K 1.2–2.4 TB 36–72 TB
Tip:

Use H.265 encoding if your cameras support it—it cuts storage by 30–50% compared to H.264 with no visible quality loss for security footage. Also, set Frigate to record only on motion events (not 24/7) to reduce storage needs by 80–90%.

Network and Bandwidth Planning for Multiple RTSP Streams

Each camera streams an RTSP feed to the Frigate server. A single 1080p camera at 15 FPS uses about 4–8 Mbps. Four cameras = 16–32 Mbps, well within a gigabit LAN. However, if you also stream to a separate NVR or view live feeds via the Frigate web interface, bandwidth doubles. For 8 cameras at 4K, expect 40–80 Mbps total—still fine for gigabit Ethernet, but Wi-Fi can struggle.

Always use wired Ethernet for cameras. PoE switches simplify power and data in one cable. For the Frigate server itself, a dedicated gigabit port (or better, a 2.5GbE port if you have 10+ cameras) prevents bottlenecks.

Build Tier 1: 2–4 Cameras (Budget Setup)

This tier targets a small home or apartment with 2–4 1080p cameras. The goal is low power, low cost, and silent operation.

  • CPU: Intel N100 (6W TDP, includes Quick Sync for decoding)
  • RAM: 8GB DDR4 or DDR5
  • Storage: 1x 4TB SSD or HDD (enough for 30–60 days of events)
  • Accelerator: Google Coral USB (M.2 if motherboard has slot)
  • Case/PSU: Mini PC (e.g., Beelink S12 Pro) or custom ITX build with 60W PSU
  • OS: Debian 12 + Docker or Proxmox LXC
  • Estimated Cost: $200–$350

This build idles around 8–12W. The Coral handles detection for up to 4 streams easily. The N100’s Quick Sync decodes the video streams, keeping CPU load under 20%.

Build Tier 2: 6–10 Cameras (Mid-Range Workhorse)

For a larger home or small office with 6–10 cameras (mix of 1080p and 4K), you need more CPU grunt for decoding and a dual-accelerator option for detection.

  • CPU: Intel i5-12400 or i5-13500 (65W TDP, strong Quick Sync)
  • RAM: 16GB DDR4
  • Storage: 2x 8TB HDD in RAID 1 (mirror) for 8TB usable, or single 12TB for event-only recording
  • Accelerator: 2x Google Coral M.2 (dual TPU for up to 16 streams) OR 1x Coral + Intel iGPU
  • Case/PSU: Fractal Design Node 804 or Jonsbo N2 with 250W PSU
  • OS: TrueNAS Scale (for ZFS storage) or Unraid (for flexibility) — see our TrueNAS vs Unraid guide for comparison
  • Estimated Cost: $600–$900

Power draw sits around 30–50W idle, 60–80W under load. The dual Coral setup provides redundancy—if one fails, detection continues on the second.

Warning:

RAID 1 protects against a single drive failure, but it is not a backup. If you accidentally delete footage or a camera is stolen, RAID won’t help. Maintain a separate backup (e.g., to a cloud service or external drive) for critical clips.

Build Tier 3: 10+ Cameras (Heavy-Duty NVR)

For 10–20 cameras at 4K resolution with 24/7 recording and 30+ day retention, you need enterprise-grade hardware.

  • CPU: Intel i7-13700 or AMD Ryzen 7 7700 (for high decode throughput)
  • RAM: 32GB DDR5
  • Storage: 4x 12TB or 16TB HDD in RAID 5 (ZFS RAIDZ1) for 36–48 TB usable
  • Accelerator: NVIDIA Tesla P4 (75W, 5.5 TOPS) or Intel Arc A380 (for AV1 decode)
  • Network: 2.5GbE or 10GbE NIC
  • Case/PSU: Fractal Design Define 7 XL or Supermicro SC846 with 500W+ PSU
  • OS: Proxmox (virtualize Frigate + other services) or Ubuntu Server + Docker
  • Estimated Cost: $1,500–$2,500

This build idles at 60–80W and draws 150–250W under full load. The NVIDIA GPU handles both decoding and inference for 15+ streams with sub-30ms latency.

Good to Know:

For storage sizing, use our NAS storage calculator guide to estimate exact TB needed for your camera count and retention period. A 10-camera 4K system recording 24/7 for 30 days needs roughly 45–90 TB, which means 4x 20TB drives in RAID 5 or a larger array.

Software Setup: Frigate on Docker or LXC

Frigate runs best in Docker on a Linux host (Debian, Ubuntu, or Proxmox LXC). The official container includes all dependencies. Key steps:

1
Install Docker and Docker Compose

On Debian/Ubuntu: sudo apt install docker.io docker-compose-v2. On Proxmox, create a Debian LXC and install Docker inside it.

2
Configure docker-compose.yml

Map the Coral device (e.g., /dev/apex_0 for USB Coral or /dev/bus/usb for M.2), set shm-size: 128m, and mount your storage directory.

3
Set up Frigate config.yml

Define each camera with its RTSP URL, detection resolution (e.g., 1280×720 for detection, 1920×1080 for recording), and object filters (person, car, animal).

4
Test detection latency

Run docker logs frigate and check for inference times under 50ms. If above 100ms, reduce detection FPS or add a second Coral.

Which Should You Choose: Coral, Intel iGPU, or NVIDIA?

For most homelab setups (2–10 cameras), a single Google Coral TPU paired with an Intel CPU (N100 or i5) is the best balance of cost, power, and performance. It delivers reliable sub-30ms detection on 6–8 streams while drawing under 15W for the accelerator itself.

If you exceed 10 cameras or need 4K detection at high frame rates, switch to an NVIDIA GPU (Tesla P4 or RTX 3050) for combined decode and inference. The power cost is higher, but the performance ceiling is much higher.

Intel Quick Sync alone is only viable for 2–4 cameras on a tight budget where a Coral is unavailable—it works but detection accuracy and latency suffer compared to a dedicated TPU.

Frequently Asked Questions

Do I need a Coral TPU for Frigate?

You do not strictly need a Coral TPU for Frigate, but for anything beyond 1–2 cameras, it is highly recommended. Without a Coral, CPU-based detection on a modern Intel i5 can handle 2–3 1080p streams at 5 FPS before latency becomes noticeable (over 100ms). A Coral USB costs around $60 and handles 6–8 streams at sub-30ms latency while drawing 5–10W. For a 2–4 camera setup on a tight budget, you can start with Intel Quick Sync alone, but expect to add a Coral later as you add cameras.

How many cameras can a basic Frigate build handle?

A basic build using an Intel N100 (6W TDP) with a single Coral TPU can reliably handle 4–6 1080p cameras at 5 FPS detection. If you drop to 3 FPS, you can push to 8 cameras. The bottleneck is not the Coral but the CPU’s ability to decode multiple video streams simultaneously. The N100’s Quick Sync can decode about 4–6 1080p streams before hitting 80% CPU load. For more cameras, step up to an i5-12400 or use a separate GPU for decoding.

How much storage do I need for 30 days of NVR footage?

Storage depends on camera count, resolution, encoding, and whether you record 24/7 or only on motion. For 4 cameras at 1080p with H.265 encoding recording 24/7, you need about 6–12 TB for 30 days. If you record only motion events (which Frigate does by default), storage drops to 1–3 TB for the same period. For 8 cameras at 4K recording 24/7, expect 36–72 TB for 30 days. Use our NAS storage sizing guide for a precise calculation based on your specific cameras.

Is a GPU better than a Coral TPU for Frigate?

A GPU (NVIDIA or Intel Quick Sync) is better for high-camera-count setups (10+ cameras) or 4K streams because it handles both video decoding and AI inference in one chip, reducing CPU load. However, a Coral TPU is better for power efficiency and cost—it draws 5–15W versus 75–200W for an NVIDIA GPU. For 2–8 cameras, a Coral TPU is the better choice. For 10+ cameras or if you already have a GPU for other tasks (like Plex transcoding), using that GPU for Frigate is practical—see our Best Plex Server Build guide for GPU recommendations that dual-task well.

Sources & Last Verified:

Last verified: July 09, 2026. Specifications cross-checked against manufacturer documentation where available.

🛡 Shop Recommended Hardware

Prices and stock verified regularly by our affiliate partners. As an affiliate, HomeLabCost may earn a commission on qualifying purchases at no extra cost to you.

Browse Hardware Picks →

homelabcost

HomeLabCost editor covering NAS builds, hardware selection, and homelab server setup guides.

Leave a Reply

Your email address will not be published. Required fields are marked *