How to Self-Host Frigate
Frigate local network video recorder with real-time object detection, camera event review, hardware acceleration, and Home Assistant integration. It was added to SelfHub after appearing in What I Self-Host, What I Don't, and Why; the product facts below were checked against the project's official site and source repository.
When Frigate is a good fit
Choose Frigate when you want this capability on infrastructure you control and are prepared to own updates, access control, monitoring, and recovery. Review the upstream documentation before selecting a version because deployment requirements can change between releases.
Deployment notes
Start from the official compose example, mount configuration and recording storage, allocate shared memory, and pass through supported acceleration hardware when available.
Place any browser-accessible interface behind HTTPS. Pin a release rather than an unqualified latest tag, apply updates deliberately, and keep the service reachable only from the networks and users that need it.
Data and recovery
Keep configuration backups separate from high-volume recordings and set explicit retention rules for clips, snapshots, and continuous footage.
Write down the restore sequence, required secrets, exposed ports, and external dependencies. A scheduled backup is not complete until a clean host can restore it and pass a functional check.
Important limitation
Camera credentials and footage are highly sensitive; isolate the camera network and follow local surveillance and privacy law.
Production checklist
- Pin and record the deployed version.
- Persist every documented data and configuration path.
- Terminate TLS at a maintained reverse proxy or trusted tunnel.
- Restrict administrative interfaces and rotate default credentials.
- Monitor uptime, disk space, certificate expiry, and failed jobs.
- Test an off-host backup with a real restore.
