A · leads
uptime-kuma
97.9
94,538 stars · MIT
Self-Hosted
uptime-kuma leads by 17.1 · decisive
A · leads
97.9
94,538 stars · MIT
B
80.8
8,852 stars · GPL-3.0
uptime-kuma versus Wallos is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. uptime-kuma is written mainly in JavaScript; Wallos is written mainly in PHP. The composite score is 97.9 for uptime-kuma and 80.8 for Wallos.
uptime-kuma has 94,538 GitHub stars to Wallos's 8,852, a gap of 85,686 (10.68×). Forks are 8,860 for uptime-kuma and 472 for Wallos. On the log scale used inside this pair, adoption is 100 versus 79, and the fork community is 100 versus 68.
Push history: uptime-kuma was last pushed on 17 November 2026 (0 days ago), and Wallos was last pushed on 07 November 2026 (9 days ago). Open issues stand at 852 for uptime-kuma (0.009 per star) and 77 for Wallos (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 92.
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. Wallos is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for uptime-kuma and 64 for Wallos. This is a procurement signal, not legal advice.
In Self-Hosted, both uptime-kuma (94,538 stars) and Wallos (8,852 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: uptime-kuma is open source, Wallos is open source.
uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: issue health, self-hosting. The widest gap is fork community at 32 points (100 vs 68), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against Wallos at 80.8, a 17.1 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 | uptime-kuma | Wallos |
|---|---|---|
| GitHub stars | 94,538 | 8,852 |
| Forks | 8,860 | 472 |
| Open issues | 852 | 77 |
| Adoption | 100 | 79 |
| Activity | 100 | 92 |
| Community | 100 | 68 |
| Issue health | 84 | 84 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 80.8 |
A fancy self-hosted monitoring tool
Wallos: Open-source, self-hostable personal subscription tracker. Visualize your recurring expenses, manage your budget, and save money.
uptime-kuma has more GitHub stars: 94,538 versus 8,852 for Wallos. The gap is 85,686 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 07 November 2026 for Wallos. That is 9 days apart.
Yes. This catalog marks both uptime-kuma and Wallos as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. Wallos is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
uptime-kuma scores 97.9 and Wallos scores 80.8. This page calls that a decisive lead for uptime-kuma.