Learn how Gladys Assistant and Home Assistant differ in their key features, development activity, technology stack and community adoption, so you can decide which of these smart home automation is best for you.
Last 30 days
Last commit
Repository age
Version
License
Self-hosted
Repository

Last 30 days
Last commit
Repository age
Version
License
Self-hosted
Repository

Both Gladys Assistant and Home Assistant have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Home Assistant significantly outpaces Gladys Assistant in community adoption with 90,228 stars compared to 3,174 stars on GitHub. This 28.4x difference suggests Home Assistant has a much larger and more active community. In terms of developer contributions, Home Assistant has 38,489 forks, indicating strong developer engagement.
Gladys Assistant is growing faster, adding 75 stars in the last 30 days (+2.4%) against adding 540 stars for Home Assistant (+0.6%). Gladys Assistant is the smaller project of the two, so it is closing the gap rather than extending a lead.
Both projects show recent activity, with Gladys Assistant last updated 2 days ago and Home Assistant 42 minutes ago.
Both tools share common technology foundations, being built with JavaScript. However, they differ in their additional technology choices: Gladys Assistant uses CSS, JSX while Home Assistant leverages Bash, Python.
Home Assistant has been in development longer, starting 13 years ago, compared to Gladys Assistant which began 11 years ago. This 1.7-year head start suggests Home Assistant may have more mature features and established processes.
Both projects use the Apache-2.0 license, providing identical terms for usage and distribution.
Both tools serve similar use cases in Smart Home Automation.
Both Gladys Assistant and Home Assistant offer self-hosting capabilities, giving you full control over your data and infrastructure.