MarcA711/frigate-rockchip
slowing
significant_divergence
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.
DMontgomery40/frigate
stale
significant_divergence
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.
deeptesh-rout/frigate
stale
significant_divergence
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.
harakas/frigate
stale
significant_divergence
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.
kcembrey/frigate
stale
significant_divergence
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.
ryanh7/frigate
stale
significant_divergence
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.
AXERA-TECH/frigate
active
significant_divergence
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.
parvin528/frigate
stale
significant_divergence
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.
DeGirum/frigate
stale
significant_divergence
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.