A
beszel
91.2
27,434 stars · MIT
Self-Hosted
uptime-kuma leads by 6.7 · narrow
A
91.2
27,434 stars · MIT
B · leads
97.9
94,538 stars · MIT
beszel 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. beszel is written mainly in Go; uptime-kuma is written mainly in JavaScript. The composite score is 91.2 for beszel and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to beszel's 27,434, a gap of 67,104 (3.45×). Forks are 1,188 for beszel and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 89 versus 100, and the fork community is 78 versus 100.
Push history: beszel 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 399 for beszel (0.015 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both beszel and uptime-kuma are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Self-Hosted, both beszel (27,434 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: beszel is open source, uptime-kuma is open source.
uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 22 points (78 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against beszel at 91.2, a 6.7 point narrow 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 | beszel | uptime-kuma |
|---|---|---|
| GitHub stars | 27,434 | 94,538 |
| Forks | 1,188 | 8,860 |
| Open issues | 399 | 852 |
| Adoption | 89 | 100 |
| Activity | 100 | 100 |
| Community | 78 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.2 | 97.9 |
Lightweight server monitoring with historical data, docker stats, and alerts.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 27,434 for beszel. The gap is 67,104 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 15 November 2026 for beszel. That is 2 days apart.
Yes. This catalog marks both beszel and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
beszel 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. 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 beszel scores 91.2. This page calls that a narrow lead for uptime-kuma.