nostr-watchvsuptime-kuma
Two self-hosted Monitoring & observability projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| nostr-watch | uptime-kuma | |
|---|---|---|
| Score | 42/100 | 88/100 |
| Rank in category | #84 of 104 in Monitoring & observability | #3 of 104 in Monitoring & observability |
| GitHub stars | 199 | 93 040 |
| Stars, last 30 days | +0 | +1 246 |
| Stable releases, 12 months | 3 | 19 |
| Latest release | nocap-info-adapter-default@v1.2.0 · 11 Mar 2026 | 2.5.8 · 26 Oct 2026 |
| Setup | Advanced | Easy |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Typescript | JavaScript |
Which one should you pick?
uptime-kuma scores 88/100 against 42/100 for nostr-watch, so it is the safer default.
uptime-kuma ships more often: 19 stable releases in the past year, against 3 for nostr-watch.
If you want the quickest setup, uptime-kuma is easier to run; nostr-watch needs more configuration.
uptime-kuma is growing faster right now (+1 246 stars in 30 days).
nostr-watch details →uptime-kuma details →All Monitoring & observability projects →
Swap a project
Keep nostr-watch, compare it with
Keep uptime-kuma, compare it with