A
dashbeam
81.4
10,351 stars · AGPL-3.0
Self-Hosted
uptime-kuma leads by 16.5 · decisive
A
81.4
10,351 stars · AGPL-3.0
B · leads
97.9
94,538 stars · MIT
dashbeam 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. dashbeam is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 81.4 for dashbeam and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to dashbeam's 10,351, a gap of 84,187 (9.13×). Forks are 627 for dashbeam and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 71 versus 100.
Push history: dashbeam was last pushed on 10 November 2026 (6 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 49 for dashbeam (0.005 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.
dashbeam is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for dashbeam and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both dashbeam (10,351 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: dashbeam is open source, uptime-kuma is open source.
The lead is split. dashbeam is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
uptime-kuma finishes ahead at 97.9 against dashbeam at 81.4, a 16.5 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 | dashbeam | uptime-kuma |
|---|---|---|
| GitHub stars | 10,351 | 94,538 |
| Forks | 627 | 8,860 |
| Open issues | 49 | 852 |
| Adoption | 81 | 100 |
| Activity | 92 | 100 |
| Community | 71 | 100 |
| Issue health | 96 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 81.4 | 97.9 |
Share files nearby and beyond.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 10,351 for dashbeam. The gap is 84,187 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 10 November 2026 for dashbeam. That is 6 days apart.
Yes. This catalog marks both dashbeam and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
dashbeam is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 dashbeam scores 81.4. This page calls that a decisive lead for uptime-kuma.