head to head · open source
frigate vs local_roborock_server
frigate has 37,457 GitHub stars, 3,833 forks, 95 open issues and last shipped yesterday. local_roborock_server has 1,300 stars, 79 forks, 25 open issues and last shipped 13 days ago. frigate leads on adoption by 2,781% (37,457 vs 1,300 stars). frigate is written in Python under MIT; local_roborock_server is written in Python under MIT. frigate has attracted 10% as many forks as stars, local_roborock_server 6%. frigate was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (home-assistant, mqtt), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| frigate | local_roborock_server | |
|---|---|---|
| GitHub stars | ★ 37K | ★ 1.3K |
| License | MIT | MIT |
| Written in | Python | Python |
| Last push | 2026-11-13 | 2026-11-01 |
| Forks | ⑂ 3.8K | ⑂ 79 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick frigate if
- You weight community size — 37K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick local_roborock_server if
- You want the local_roborock_server feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Python
- You evaluated both and local_roborock_server fits your workflow better
About frigate
Frigate NVR™ Realtime Object Detection for IP Cameras \[English\] 简体中文 A complete and local NVR designed for Home Assistant with AI object detection. Uses OpenCV and Tensorflow to perform realtime object detection locally for IP cameras. Use of a GPU or AI accelerator is highly recommended. AI accelerators will outperform even the best CPUs with very little overhead. See Frigate's supported object detectors. Tight integration with Home Assistant via a custom component Designed to minimize resource use and maximize performance by only looking for objects when and where it is necessary Leverages multiprocessing…
read the full frigate overview →
About local_roborock_server
Roborock Local Server [![GHCR][badge ghcr]][link ghcr] Run Roborock's cloud backend on your own local network. Your vacuum keeps live maps and local controls on an isolated LAN without internet access, requiring no hardware modifications or firmware rooting. Why this exists While Home Assistant communicates with Roborock vacuums over a local protocol, two constraints previously prevented running them completely offline: 1. Cloud locked maps: Roborock routes all map data strictly through their cloud servers (despite the vacuum storing the map locally). 2. Cloud health checks: If a vacuum cannot reach Roborock's…
read the full local_roborock_server overview →
More in Miscellaneous
Related comparisons
More Internet of Things (IoT) projects
Compare either of these against the rest of the Internet of Things (IoT) field.
Frequently asked questions
Is frigate or local_roborock_server more popular?
frigate has 37,457 GitHub stars and local_roborock_server has 1,300. frigate has the larger community by that measure.
Are frigate and local_roborock_server free?
Both are open source. frigate is licensed under MIT and local_roborock_server under MIT. Neither carries a licence fee.
What is the difference between frigate and local_roborock_server?
frigate is written in Python and local_roborock_server in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, frigate or local_roborock_server?
Choose frigate if you want the larger community (37,457 stars) or its MIT licence terms. Choose local_roborock_server if its feature set, stack or MIT licence fits better. Both are self-hostable.