arewedownvsuptime-kuma
Two self-hosted Monitoring & observability projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| arewedown | uptime-kuma | |
|---|---|---|
| Score | 43/100 | 90/100 |
| Rank in category | #84 of 105 in Monitoring & observability | #2 of 105 in Monitoring & observability |
| GitHub stars | 205 | 94 481 |
| Stars, last 30 days | +0 | +2 105 |
| Stable releases, 12 months | 0 | 22 |
| Latest release | — | 2.5.11 · 12 Nov 2026 |
| Setup | Moderate | Easy |
| Official Docker image | Yes | Yes |
| License | GPL-3.0 | MIT |
| Main language | JavaScript | JavaScript |
Which one should you pick?
uptime-kuma scores 90/100 against 43/100 for arewedown, so it is the safer default.
uptime-kuma ships more often: 22 stable releases in the past year, against 0 for arewedown.
If you want the quickest setup, uptime-kuma is easier to run; arewedown needs more configuration.
uptime-kuma is growing faster right now (+2 105 stars in 30 days).
Key differences
- License: arewedown is GPL-3.0, uptime-kuma is MIT.
- Features only arewedown lists: ARM and x86 support, Custom script tests, Dead man's switch (date in file), Disk Usage Monitoring and 10 more.
- Features only uptime-kuma lists: 20-second intervals, Badges, Browser engine monitoring, Certificate info and 8 more.
arewedown details →uptime-kuma details →All Monitoring & observability projects →
Swap a project
Keep arewedown, compare it with
Keep uptime-kuma, compare it with