Frigate NVR Setup: 5 Easy Steps to Ditch Cloud Cameras

I canceled my last cloud camera subscription two months ago, and my security cameras have never worked better. If you’ve been eyeing the same move, this Frigate NVR setup is the way out — five steps, one afternoon, and every second of footage stays on hardware you own. No monthly fee, no “your video history is only 60 days” email, no footage of your front porch sitting on someone else’s server.

Frigate is a free, open-source network video recorder that runs on your own machine and uses AI object detection to tell you the difference between a person walking up your driveway and a tree branch waving at the camera for six hours. It’s the same core trick Ring and Nest charge you for every month — except it happens locally, in milliseconds, with zero cloud dependency.

Here’s the part that sold me: the hardware pays for itself. A Ring Protect Pro plan runs about $200 a year. The mini PC in this guide costs roughly that once, and it’ll happily run your cameras (plus half a dozen other self-hosted apps) for years. If you’ve already got a Docker home server humming in a closet, you’re most of the way there.

Why This Frigate NVR Setup Beats a Cloud Camera Kit

Three reasons, and they’re not subtle. Privacy: your footage never leaves your network unless you decide it should. Cost: zero subscription, forever — the whole build below, with two 4K cameras, costs about two years of cloud fees. Speed and reliability: detection happens on your hardware, so alerts fire in under a second and keep working when your internet goes down. Try getting any of those three from a cloud kit, let alone all of them.

The trade-off is an afternoon of tinkering. That’s the honest price. But Frigate in 2026 is dramatically easier to stand up than it was even two years ago, and the five steps below are the exact Frigate NVR setup I’d follow starting from zero today.

Step 1: Grab a Mini PC That Sips Power

You don’t need a rack server for this. Frigate’s own docs point at efficient Intel N100 mini PCs as the sweet spot, because the N100’s integrated GPU handles AI object detection through OpenVINO with room to spare for a handful of cameras. Translation: the cheap little box is enough, and it idles at less than 10 watts.

My pick is the Beelink Mini S12 Pro — N100, 16GB of RAM, 500GB SSD, and it’s the same box I recommend for general homelab duty. One note on storage: 500GB holds roughly a week of continuous 4K recording from a couple of cameras, so plan to bolt on a cheap external drive if you want longer retention.

Quick word on the Google Coral USB Accelerator, because every older Frigate guide swears by it: the official docs no longer recommend it for new installs. The N100’s built-in GPU does the same job now. Skip the Coral unless you’re building on a Raspberry Pi or chasing absolute minimum power draw.

Step 2: Pick Cameras That Don’t Phone Home

Any camera that speaks RTSP works with Frigate, but wired PoE cameras are the move — one cable for power and data, and no WiFi dropouts at the exact moment something happens. Frigate’s docs lean toward Dahua, Hikvision, and Amcrest; of those three, Amcrest is the easiest to actually buy in the US.

The Amcrest UltraHD 4K Turret (IP8M-T2599EW-AI-V3) is my primary pick: 8MP, solid night vision, IP67 weatherproof, and clean RTSP streams that Frigate ingests without drama.

If you’d rather go with the bigger consumer name, the Reolink RLC-810A is a hugely popular 4K PoE bullet that plays nicely with Frigate — just know the Frigate community usually routes Reolink streams through go2rtc (built into Frigate) for stability.

Here’s how the two compare at a glance:

To power them, a small PoE switch like the TP-Link TL-SG1005P gives you four PoE+ ports for about fifty bucks — plug the cameras in, plug the switch into your router, done.

Step 3: Spin Up Frigate with Docker Compose

With Docker installed on the mini PC (my Docker Compose home server guide covers that in ten minutes), Frigate is one compose file away. This is the official template, trimmed to what matters:

services:
  frigate:
    container_name: frigate
    privileged: true
    restart: unless-stopped
    stop_grace_period: 30s
    image: ghcr.io/blakeblackshear/frigate:stable
    shm_size: "512mb"
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ./config:/config
      - ./storage:/media/frigate
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "8971:8971"
      - "8554:8554"

The devices line passes the N100’s iGPU into the container so OpenVINO can use it for detection, and the tmpfs cache keeps constant camera writes off your SSD. Run docker compose up -d, then open https://your-server-ip:8971 and Frigate greets you with a login screen. That’s it — the app is alive.

Step 4: Point Frigate at Your Cameras

Frigate reads a single config.yml from the config folder you mapped above. Here’s a working starter for one camera with OpenVINO detection on the N100:

mqtt:
  enabled: false

detectors:
  ov:
    type: openvino
    device: GPU

cameras:
  front_yard:
    ffmpeg:
      inputs:
        - path: rtsp://admin:PASSWORD@192.168.1.50:554/cam/realmonitor?channel=1&subtype=0
          roles:
            - record
        - path: rtsp://admin:PASSWORD@192.168.1.50:554/cam/realmonitor?channel=1&subtype=1
          roles:
            - detect

record:
  enabled: true
  retain:
    days: 7

Two streams per camera is the trick everyone misses: the full-resolution main stream gets recorded, while the lower-resolution sub stream feeds the AI detector. That split is why a modest mini PC can handle multiple 4K cameras without breaking a sweat. Swap in your camera’s IP and credentials (the RTSP path above is Amcrest’s format; Reolink and others are listed in the official Frigate docs), restart the container, and your camera feed appears in the dashboard.

Step 5: Tune Detection and Wire It Into Your Smart Home

Out of the box, Frigate detects people. In the UI you can add cars, dogs, cats, and more per camera, then draw motion masks over things that cause false alerts — the street behind your driveway, a flag, your neighbor’s very active wind chimes. Ten minutes of mask-drawing is the difference between “alerts I trust” and “alerts I mute.”

Then comes the fun part. Frigate has a first-class Home Assistant integration: live feeds on your dashboard, and automations like “if a person is detected in the backyard after 10pm, turn every outdoor light on.” For notifications on your phone, the Home Assistant companion app delivers rich alerts with a snapshot of exactly what triggered — same experience as Ring, minus the fee. And if you want to check your cameras from anywhere without opening ports, run it through Tailscale like the rest of your homelab.

The Takeaway

A complete Frigate NVR setup in 2026 comes down to this: one efficient N100 mini PC, wired PoE cameras, a compose file, and a short config. Call it two years of cloud fees, all-in, for a two-camera system that out-detects the cloud kits, answers to nobody, and never sends you a renewal notice. The subscription camera companies are betting you won’t spend one afternoon learning this. Take the bet.

Got a Frigate build running, or stuck on a step? Drop it in the comments — config questions welcome. And if this saved you a subscription, share it with the friend still paying for cloud storage of their own driveway.

Frequently Asked Questions

Do I need a Google Coral USB Accelerator to run Frigate?

No, not on modern hardware. The official Frigate docs no longer recommend it for new installs — an Intel N100 mini PC’s built-in GPU handles AI object detection through OpenVINO on its own. Only consider a Coral if you’re building on a Raspberry Pi or chasing the absolute minimum power draw.

How much does a full Frigate NVR setup cost?

Roughly two years’ worth of a cloud camera subscription like Ring Protect Pro, which runs about $200 a year, except you only pay once.

How much storage do I need for footage?

A 500GB SSD holds roughly a week of continuous 4K recording from a couple of cameras. Budget for a cheap external drive if you want longer retention.

Why does Frigate need two video streams per camera?

The full-resolution main stream gets recorded, while a lower-resolution sub stream feeds the AI detector. That split is why a budget mini PC can handle multiple 4K cameras without breaking a sweat — the detector never has to chew through full-resolution frames.

Can Frigate integrate with Home Assistant?

Yes — it’s a first-class integration, with live camera feeds on your Home Assistant dashboard and automations like turning on outdoor lights when a person is detected after 10pm. The Home Assistant companion app can also deliver rich phone notifications with a snapshot of what triggered the alert.