A
self-hosted
80.9
9,656 stars · license n/a
Self-Hosted
uptime-kuma leads by 17.0 · decisive
A
80.9
9,656 stars · license n/a
B · leads
97.9
94,538 stars · MIT
self-hosted versus uptime-kuma is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. self-hosted is written mainly in Shell; uptime-kuma is written mainly in JavaScript. The composite score is 80.9 for self-hosted and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to self-hosted's 9,656, a gap of 84,882 (9.79×). Forks are 1,955 for self-hosted and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 83 versus 100.
Push history: self-hosted was last pushed on 15 November 2026 (2 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 140 for self-hosted (0.014 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
self-hosted is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. uptime-kuma is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 30 for self-hosted and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both self-hosted (9,656 stars) and uptime-kuma (94,538 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: self-hosted is unpriced in this catalog, uptime-kuma is open source.
uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against self-hosted at 80.9, a 17.0 point decisive margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | self-hosted | uptime-kuma |
|---|---|---|
| GitHub stars | 9,656 | 94,538 |
| Forks | 1,955 | 8,860 |
| Open issues | 140 | 852 |
| Adoption | 80 | 100 |
| Activity | 100 | 100 |
| Community | 83 | 100 |
| Issue health | 84 | 84 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 80.9 | 97.9 |
Sentry, feature-complete and packaged up for low-volume deployments and proofs-of-concept
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 9,656 for self-hosted. The gap is 84,882 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 15 November 2026 for self-hosted. That is 2 days apart.
Yes. This catalog marks both self-hosted and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
self-hosted is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. uptime-kuma is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
uptime-kuma scores 97.9 and self-hosted scores 80.9. This page calls that a decisive lead for uptime-kuma.