Discofork
Repository brief

blakeblackshear/frigate

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:26:15.755Z
1mo ago

blakeblackshear/frigate

Frigate is an actively maintained MIT-licensed NVR for IP cameras with realtime local object detection, built around Home Assistant integration and low-latency live viewing. It appears to be a large, popular project with 31k+ stars, 2.9k forks, and very recent commits on 2026-03-30.

GitHub
Loading tags...
Stars31,143
Forks2,970
Default branchdev
Last pushed2026-03-30T14:29:19Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if your priority is Rockchip support and hardware-specific acceleration. Choose upstream if you want the newest general Frigate fixes, broad platform support, and lower maintenance risk.

Choose this fork if you value the added GUI/configuration and experimental workflow features more than staying current with upstream Frigate. Stick with upstream if you want the fastest access to fixes, the cleanest Home Assistant compatibility path, and lower upgrade risk.

Choose this fork if AMD/ROCm support is the priority and you can accept being behind upstream. Stick with upstream if you want the broadest compatibility, freshest fixes, and the least maintenance risk.

Prefer upstream unless you specifically need this fork’s custom behavior and are prepared to own a large maintenance burden. This fork is best for advanced adopters who value customization over stability, support, and staying current.

Choose this fork only if ROCm support, AGPL licensing, or its custom analytics path is the main requirement. If you want the current Frigate feature set, recent bug fixes, and easier community support, upstream is the safer choice.

Adopt this fork only if its hardware-specific changes solve a concrete deployment problem you have now. For most users, upstream Frigate is the safer choice because this fork is stale and heavily diverged.

Choose this fork if your priority is TensorRT-accelerated inference and Chinese support and you can tolerate being far behind upstream. Choose upstream if you want active maintenance, newer fixes, and less divergence risk.

Choose this fork if your primary goal is AXERA-optimized Frigate on supported hardware and you value the added accelerator, media-pipeline, and UI workflow work. Choose upstream if you want the newest Frigate fixes, broader compatibility, and lower maintenance risk.

Choose this fork only if you need the added AI workflows or hardware/model support; otherwise upstream Frigate is the safer and more current choice.

Prefer this fork if you need DeGirum-centric detector support or the added classification/audio/accelerator workflows. Prefer upstream if you want the latest Frigate fixes, lower maintenance risk, and the most broadly supported path.