Frigate NVR · setup we actually use
Let Frigate watch the room so you do not have to sit there.
This is how we run Frigate NVR on a 24/7 cat cam. Install it, add one camera per job, turn on cat detection, and treat each hit as a visit you can cut.
Frigate is an open-source camera watcher people use at home. It looks at the cameras you already have, notices when something it was asked to find walks into the picture, and keeps a short record of that moment. We ask it to find a cat. It runs on a regular Windows PC that stays on. No graphics card, no Coral stick: since August 2026 the finding is done by the Intel graphics built into the processor itself, through OpenVINO, at about 12 milliseconds a look. The project lives at frigate.video. If you want the one-paragraph version of what Frigate is before the steps, read what Frigate NVR actually does all day.
| The question | The page that answers only that |
|---|---|
| What is Frigate, in plain words? | What is Frigate NVR? Detect stream, record stream, detector, retention: the three ideas, one sentence each. |
| Can I run it on Windows? | Frigate on Windows with WSL2 and Docker, the way we run it 24/7 on a desktop PC. The exact files are on the setup page. |
| How do I add a camera? | Camera setup: RTSP, sub-streams, go2rtc, with a Tapo example. |
| Can I see your whole config? | The full config.yml for eleven cameras, annotated line by line. |
| Do I need a Coral? | Probably not. CPU, Intel iGPU, Coral and NVIDIA compared with what we measured. |
| How does the iGPU do it under WSL2? | An OpenVINO detector over ZMQ: the full server, unit file and numbers. |
| How much disk will this eat? | Retention and storage math from a real 3.7 TB drive. |
| How do I put a camera on a public site safely? | The public cam proxy: four cameras public, Frigate never on the internet. |
| How do the visits become Shorts? | The Shorts pipeline, and the two 24/7 streams that never stop. |
| Ordinary part | What it does |
|---|---|
| A regular Windows PC that stays on | Watches the streams while we sleep. No one sits at a desk calling action. How Frigate runs on Windows. |
| No graphics card. No Coral. | Frigate’s cat detection runs on the Intel graphics inside the processor, through OpenVINO. We did not add a graphics card, a Coral stick, or a cloud GPU. Which detector you actually need. |
| The same camera streams the maker’s app already shows | Frigate uses that address. You do not need a second special camera. |
| Detection set to cat | A hit is a visit. We cut the visit. We do not keep a 24-hour tape as the show. |
| The path she walked through the frame | A tall phone crop can follow her instead of pinning the middle of an empty room. |
| Same computer cuts the Short | Python and ffmpeg. Wide 2560×1440 at 20 fps in. 1080×1920 Short out. Then YouTube Studio uploads it. |
A Frigate camera is not a leftover box on a shelf. It is a job in the room. Water watches the drink. Food watches the meal. Treat watches the quilt when a treat fires. Court watches the whole floor. Face is close enough to be a portrait. If you cannot say the job in one word, the camera is not ready to add.
Name the camera after that job. Do not keep a factory label, a room number, or the name of the last house it sat in. When a visit lands, you need to know which station she used without decoding leftover hardware.
objects: block, and why we do track person on the cat cams, is on the annotated config.
Frigate NVR watches. A visit is a detection. Pictures decide if the visit is real. Then you cut. How the cameras sit. How the cut is judged. The pipeline that cuts without a person.
The pages above are the plain-language layer. The pasteable layer, with every file as it runs: the WSL2 and Docker files, the full config.yml, and the OpenVINO detector over ZMQ.