Frigate NVR Updates: DeGirum Detector Removed
Frigate has fully removed support for the DeGirum detector after the company ceased operations on August 1st, 2026, cleaning up related requirements, model references, and detector code in PR #23882.
Duration: PT1M39S
Episode overview
This episode is a short developer briefing from Frigate NVR Updates.
It explains recent repository work in plain language.
- Show: Frigate NVR Updates
- Published: 2026-08-02T13:09:25Z
- Audio duration: PT1M39S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good day, and welcome to Frigate NVR Updates for August 2nd, 2026.
Today's story is simple, but worth knowing if you're running DeGirum hardware: that detector integration is gone from Frigate.
The change comes down to one fact - DeGirum ceased operations on August 1st. Maintainer Josh Hawkins moved quickly, merging PR #23882 to strip out all references to DeGirum across the codebase. That touched the detector implementation itself, related model files, and the requirements wheels that pulled in DeGirum's…
This isn't a bug fix or a feature - it's housekeeping in response to a vendor disappearing. When a detector backend's company shuts down, keeping the integration around creates dead weight: unused dependencies, unmaintained code paths, and a false impression that the option still works. Removing it cleanly, in one…
If you were using DeGirum for object detection, this update means you'll need to move to a different detector backend going forward. There's nothing in this change that suggests a replacement or migration path was included - just removal. Worth checking your configuration if you have DeGirum references sitting in…
What's next: with DeGirum gone, expect the supported…