head to head · open source
integration vs button-card
integration has 7,869 GitHub stars, 1,613 forks, 164 open issues and last shipped yesterday. button-card has 2,523 stars, 285 forks, 31 open issues and last shipped 2 months ago. integration leads on adoption by 212% (7,869 vs 2,523 stars). integration is written in Python under MIT; button-card is written in TypeScript under MIT. integration has attracted 20% as many forks as stars, button-card 11%. integration was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (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 | button-card | |
|---|---|---|
| GitHub stars | ★ 7.9K | ★ 2.5K |
| License | MIT | MIT |
| Written in | Python | TypeScript |
| Last push | 2026-11-02 | 2026-09-09 |
| Forks | ⑂ 1.6K | ⑂ 285 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick integration if
- You weight community size — 7.9K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick button-card if
- You want the button-card feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and button-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 button-card
Button Card by @RomRider [![Stable][releases shield]][releases] [![Beta][releases dev shield]][releases dev] [![HACS Badge][hacs badge]][hacs link] ![Project Maintenance][maintenance shield] ![Downloads][downloads] [![GitHub Activity][commits shield]][commits] [![License][license shield]](LICENSE.md) [![Discord][discord shield]][discord] [![Community Forum][forum shield]][forum] [commits shield]: [commits]: [discord]: [discord shield]: [forum shield]: [forum]: [license shield]: [maintenance shield]: [releases shield]: [releases]: [releases dev shield]: [releases dev]: [hacs badge]: [downloads]: [hacs link]…
read the full button-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 button-card more popular?
integration has 7,869 GitHub stars and button-card has 2,523. integration has the larger community by that measure.
Are integration and button-card free?
Both are open source. integration is licensed under MIT and button-card under MIT. Neither carries a licence fee.
What is the difference between integration and button-card?
integration is written in Python and button-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 button-card?
Choose integration if you want the larger community (7,869 stars) or its MIT licence terms. Choose button-card if its feature set, stack or MIT licence fits better. Both are self-hostable.