head to head · open source
frigate vs HomeAssistant-Tapo-Control
frigate has 37,160 GitHub stars, 3,782 forks, 95 open issues and last shipped yesterday. HomeAssistant-Tapo-Control has 2,043 stars, 167 forks, 29 open issues and last shipped 11 days ago. frigate leads on adoption by 1,719% (37,160 vs 2,043 stars). frigate is written in Python under MIT; HomeAssistant-Tapo-Control is written in Python under Apache-2.0. frigate has attracted 10% as many forks as stars, HomeAssistant-Tapo-Control 8%. frigate was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 3 topic tags (camera, home-assistant, home-automation), 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 | HomeAssistant-Tapo-Control | |
|---|---|---|
| GitHub stars | ★ 37K | ★ 2.0K |
| License | MIT | Apache-2.0 |
| Written in | Python | Python |
| Last push | 2026-11-02 | 2026-10-23 |
| Forks | ⑂ 3.8K | ⑂ 167 |
| 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 HomeAssistant-Tapo-Control if
- You want the HomeAssistant-Tapo-Control feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Python
- You evaluated both and HomeAssistant-Tapo-Control 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 HomeAssistant-Tapo-Control
HomeAssistant Tapo: Cameras Control Custom component Tapo: Cameras Control to add Tapo cameras, doorbells and chimes into Home Assistant ⭐ Now also exposing a stream for devices that have no RTSP or ONVIF capabilities. Contributing Before opening a pull request, read CONTRIBUTING.md, especially if the work used an AI assistant. AI assisted contributions are welcome when the author has reviewed, understood, and can explain the changes. Purely AI generated or "vibe coded" PRs where the author did not review the code and behavior are not welcome and may be closed. Reviewing unverified generated code often takes…
read the full HomeAssistant-Tapo-Control 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 HomeAssistant-Tapo-Control more popular?
frigate has 37,160 GitHub stars and HomeAssistant-Tapo-Control has 2,043. frigate has the larger community by that measure.
Are frigate and HomeAssistant-Tapo-Control free?
Both are open source. frigate is licensed under MIT and HomeAssistant-Tapo-Control under Apache-2.0. Neither carries a licence fee.
What is the difference between frigate and HomeAssistant-Tapo-Control?
frigate is written in Python and HomeAssistant-Tapo-Control 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 HomeAssistant-Tapo-Control?
Choose frigate if you want the larger community (37,160 stars) or its MIT licence terms. Choose HomeAssistant-Tapo-Control if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.