head to head · open source
integration vs vacuum-card
integration has 7,837 GitHub stars, 1,611 forks, 164 open issues and last shipped 2 days ago. vacuum-card has 1,262 stars, 634 forks, 23 open issues and last shipped 10 days ago. integration leads on adoption by 521% (7,837 vs 1,262 stars). integration is written in Python under MIT; vacuum-card is written in TypeScript under MIT. integration has attracted 21% as many forks as stars, vacuum-card 50%. integration was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (hacs, home-assistant), 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
| integration | vacuum-card | |
|---|---|---|
| GitHub stars | ★ 7.8K | ★ 1.3K |
| License | MIT | MIT |
| Written in | Python | TypeScript |
| Last push | 2026-10-24 | 2026-10-16 |
| Forks | ⑂ 1.6K | ⑂ 634 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick integration if
- You weight community size — 7.8K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick vacuum-card if
- You want the vacuum-card feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and vacuum-card fits your workflow better
About integration
HACS (Home Assistant Community Store) Manage (Install, track, upgrade) and discover custom elements for Home Assistant directly from the UI. What? HACS is an integration that gives the user a powerful UI to handle downloads of custom needs. Highlights of what HACS can do: Help you discover new custom elements. Help you download new custom elements. Help you keep track of your custom elements. Manage(download/update/remove) Shortcuts to repositories/issue tracker Useful links General documentation Configuration FAQ GitHub Discord Become a GitHub sponsor? ❤️ BuyMe Coffee Beer? 🍺🙈 Issues If When you experience…
read the full integration overview →
About vacuum-card
Vacuum Card [![npm version][npm image]][npm url] [![hacs][hacs image]][hacs url] [![GitHub Sponsors][gh sponsors image]][gh sponsors url] [![Patreon][patreon image]][patreon url] [![Buy Me A Coffee][buymeacoffee image]][buymeacoffee url] [![Twitter][twitter image]][twitter url] Vacuum cleaner card for [Home Assistant][home assistant] Lovelace UI By default, Home Assistant does not provide any card for controlling vacuum cleaners. This card displays the state and allows to control your robot. ![Preview of vacuum card][preview image] Installing 💡 Tip: If you like this project, consider giving me a tip for the…
read the full vacuum-card 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 integration or vacuum-card more popular?
integration has 7,837 GitHub stars and vacuum-card has 1,262. integration has the larger community by that measure.
Are integration and vacuum-card free?
Both are open source. integration is licensed under MIT and vacuum-card under MIT. Neither carries a licence fee.
What is the difference between integration and vacuum-card?
integration is written in Python and vacuum-card in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, integration or vacuum-card?
Choose integration if you want the larger community (7,837 stars) or its MIT licence terms. Choose vacuum-card if its feature set, stack or MIT licence fits better. Both are self-hostable.