Frigate NVR 2026: UK Buyer and Installer Guide

Frigate NVR is a free, open-source recorder that runs AI object detection locally on your IP cameras, so it suits a tech-savvy owner who will maintain it, or works as a hybrid add-on for smarter alerts on top of a standard recorder.

For most UK commercial jobs, though, a supported NVR should remain the system of record, because the installer and the customer carry the support, retention and evidence risk when something fails. There is no per-camera licence fee, but there is also no vendor behind the install, so the real cost is hardware, setup time and ongoing upkeep.

What is Frigate NVR, and what does it actually do?

Frigate NVR is open-source recorder software that runs AI object detection locally on IP camera feeds, identifying objects rather than raw motion. It also handles retention based on detected objects, re-streams over RTSP, sends events over MQTT and integrates tightly with Home Assistant.

An NVR (network video recorder) is the device or software that records video from IP cameras over a network. Per frigate.video, Frigate is built around real-time AI object detection, with all processing on your own hardware.

The Frigate docs and project page describe five core behaviours:

• Object detection: it works out whether motion is a person, a car or another object of interest, instead of alerting on every moving shadow.
• Retention: recordings are kept based on the objects detected.
• Re-streaming: camera feeds can be re-streamed over RTSP.
• MQTT: detection events go out over MQTT. A broker is optional, but the docs make it a requirement for the Home Assistant integration.
• Home Assistant: the integration is tight, though the docs are explicit that the Home Assistant App and the integration are separate things.

The code lives at blakeblackshear/frigate under an MIT licence. For the latest version, check the GitHub releases page rather than a number in an article. The install docs describe Frigate as a Docker container that runs on any Docker host.

There is no per-camera licence fee, but there is also no vendor behind your install. The real cost is the host machine, storage and an optional AI accelerator, plus your own time on setup and upkeep. Frigate still needs good IP cameras feeding it, and our Best CCTV Cameras UK 2026: IP, Analogue & Wireless Compared guide covers how to choose them.

What hardware and setup does a Frigate install need?

A Frigate install needs a Docker host, ideally bare-metal Debian-based, plus a Coral TPU or GPU for detection and wired PoE cameras.

Install route and MQTT

Frigate is a Docker container that runs on any Docker host, and the Home Assistant add-on is the same container packaged for that platform. The Frigate installation documentation is explicit that the add-on is not the same as the integration. The integration is still what connects Frigate to Home Assistant, whichever route you take.

An MQTT broker is optional for Frigate itself but required for the Home Assistant integration. In that case, Frigate and Home Assistant must use the same broker.

Host and detector

The docs recommend Docker on a bare-metal Debian-based distribution, because Frigate needs low-overhead access to Coral and GPU hardware. Running it in a VM on Proxmox, ESXi or VirtualBox is not recommended, though some users have had success with Proxmox. Windows is not officially supported either, although some users have got it running.

CPU-only detection is for testing only. The docs strongly recommend a dedicated detector, either a Coral TPU or a GPU.

Cameras

The camera advice here is one creator's experience, not a rule from the Frigate docs. In a Home Assistant-focused video, Home Automation Guy says to check which codec your camera sends. He had a newer Reolink model that only offered H.265, it performed poorly with Frigate, and he returned it. Confirm your model's stream options before buying in quantity.

The same creator prefers wired PoE to battery or Wi-Fi cameras for 24/7 recording, saying battery units drain quickly and are less reliable. One cable then carries both data and power.

If any camera sees beyond your own boundary, data-protection duties can apply. Our guide to UK CCTV Law 2026: What Owners Must Know covers when.

Where does a traditional NVR still win on UK jobs?

A traditional NVR wins on support, offering a vendor warranty, manufacturer firmware and an RMA route, which open-source Frigate does not provide. With Frigate, the installer becomes the support desk for failed disks, bad updates and camera stream problems.

A traditional NVR wins on support: a vendor warranty, manufacturer firmware and an RMA route, none of which open source Frigate ships with. As general guidance, with Frigate the installer becomes the support desk. Every failed disk, bad update or camera that stops negotiating a stream lands on you, with no helpdesk behind you.

ONVIF and PoE in one box

A recorder with built-in PoE ports removes the separate switch and the separate host from the job. The ANNKE 16-channel 12MP PoE NVR (H.265+) is our first-party example. It handles 16 channels at up to 12MP, powers the cameras itself and records in H.265+.

Its smart playback skips still footage and shows only movement in the area and period you select, which saves a client from scrubbing through hours of video. Pricing on the product page applies to signed-in trade accounts, and live stock status is shown there too.

Dahua recorders are the supported-ecosystem alternative. Pairing them with Dahua cameras keeps recorder, cameras and firmware under one manufacturer.

Both routes suit the job where the customer wants a box on the wall that works and a number to ring when it doesn't. The rest of that job, such as patch leads and connectors, is worth carrying in the van, and our CCTV accessories wholesale van stock guide is a useful place to start.

What are the UK compliance and liability blockers?

The blockers are mostly handover gaps: exporting footage on request, documented retention, and whether an insurer or monitoring centre will accept a community-supported recorder. The duties themselves are covered in our UK CCTV law guide, so this section sticks to what an installer must hand over.

Handover points

• Export. The customer, as data controller, must be able to produce footage for subject access and police requests. Frigate runs as a Docker container, so how clips get out depends on your deployment and who holds access. Prove the export route works before sign-off, and make sure the customer's named person can do it without you.
• Retention. Set it per site and write it into the handover pack. Don't leave it on the defaults.
• Signage and access. These stay with the customer. Record who holds logins to the Frigate UI and the host machine.
• Domestic use. The household exemption is not a blanket answer. It depends on what the cameras capture and how the footage is used, so don't promise it covers a site.

Insurance and monitoring

Some insurers and underwriters may ask for recorders with named support and documentation, and Frigate is an open-source project under the MIT licence per its GitHub repository. That is general guidance, not a rule, so check the policy wording and ask the insurer in writing.

The same applies to any alarm receiving centre connection. Confirm what it accepts before you quote.

If the customer expects a supported, documented recorder, a conventional NVR avoids these questions. Our NVR training guide for CCTV installers covers the handover basics that apply either way.

When should you quote Frigate, a hybrid add-on or a standard NVR?

Quote Frigate alone only for a tech-savvy home owner who accepts self-support; for everyone else, a supported NVR stays the recorder and Frigate is an optional layer.

Customer	Frigate standalone	Hybrid add-on	Standard NVR
Tech-savvy domestic owner	Reasonable, if they accept self-support	Safe default	Perfectly sound, without the AI tuning
Small business	Avoid	Only if Frigate is an optional AI-alert layer	Recorder of record
Multi-site or commercial	Avoid	Secondary analytics layer, if at all	Default, once ARC and insurer requirements are met

Quote Frigate when…

• The customer owns the maintenance. Frigate is a Docker container, also runnable as a Home Assistant add-on, and the installation documentation says Windows is not officially supported and VMs are not recommended. Nobody on the end of a support line fixes it.
• There is no ARC or insurer dependency. If a monitoring centre or policy specifies the recorder, that settles it.
• Existing IP cameras can be reused. Frigate reads RTSP streams, so the question is what the current cameras expose, including codec support. Check this before you quote.
• Alert fatigue is the problem. Frigate classifies person or vehicle events locally instead of relying on simple motion detection, and a supported accelerator is what makes that practical on modest hardware.
• The customer wants local-only processing. Analysis stays on their own hardware.

Flip any of these and quote a standard NVR instead. The software itself is free under an MIT licence, so Frigate NVR cost is really the host machine, an accelerator and the customer's time.

The hybrid pattern

The supported NVR records every camera continuously and holds the evidence. Frigate takes a separate stream from the same cameras, runs detection and sends person or vehicle alerts, typically through MQTT to Home Assistant.

If Frigate fails, recording carries on. Check how many simultaneous streams each camera allows before promising this.

A 16-channel recorder such as the ANNKE 16 Channel 12MP PoE NVR H.265+ can fill that recorder role, with smart playback that skips footage without movement. The customer's own accredited installer should do the fitting.