Gitnessvshome-screens
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Gitness | home-screens | |
|---|---|---|
| Score | 80/100 | 50/100 |
| Rank in category | #2 of 14 in Code Hosting | #63 of 104 in Home Automation |
| GitHub stars | 38 759 | 96 |
| Stars, last 30 days | +325 | +27 |
| Stable releases, 12 months | 6 | 9 |
| Latest release | v2.28.2 · 20 Apr 2026 | v1.14.0 · 25 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | No |
| License | Apache-2.0 | MIT |
| Main language | Go | Typescript |
Which one should you pick?
Gitness scores 80/100 against 50/100 for home-screens, so it is the safer default.
home-screens ships more often: 9 stable releases in the past year, against 6 for Gitness.
If you want the quickest setup, Gitness is easier to run; home-screens needs more configuration.
Gitness is growing faster right now (+325 stars in 30 days).
Gitness details →home-screens details →