A · leads
uptime-kuma
97.9
94,538 stars · MIT
Self-Hosted
uptime-kuma leads by 18.9 · decisive
A · leads
97.9
94,538 stars · MIT
B
79.0
9,469 stars · AGPL-3.0
uptime-kuma versus wealthfolio 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; wealthfolio is written mainly in Rust. The composite score is 97.9 for uptime-kuma and 79.0 for wealthfolio.
uptime-kuma has 94,538 GitHub stars to wealthfolio's 9,469, a gap of 85,069 (9.98×). Forks are 8,860 for uptime-kuma and 829 for wealthfolio. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 74.
Push history: uptime-kuma was last pushed on 17 November 2026 (0 days ago), and wealthfolio was last pushed on 17 November 2026 (0 days ago). Open issues stand at 852 for uptime-kuma (0.009 per star) and 537 for wealthfolio (0.057 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
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. wealthfolio 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. License scores in this pair are 96 for uptime-kuma and 52 for wealthfolio. This is a procurement signal, not legal advice.
In Self-Hosted, both uptime-kuma (94,538 stars) and wealthfolio (9,469 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, wealthfolio is open source.
uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against wealthfolio at 79.0, a 18.9 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 | wealthfolio |
|---|---|---|
| GitHub stars | 94,538 | 9,469 |
| Forks | 8,860 | 829 |
| Open issues | 852 | 537 |
| Adoption | 100 | 80 |
| Activity | 100 | 100 |
| Community | 100 | 74 |
| Issue health | 84 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 79.0 |
A fancy self-hosted monitoring tool
A beautiful, private, local-first personal finance tracker. Investments, net worth, spending, and simulations.
uptime-kuma has more GitHub stars: 94,538 versus 9,469 for wealthfolio. The gap is 85,069 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both uptime-kuma and wealthfolio 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. wealthfolio 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
uptime-kuma scores 97.9 and wealthfolio scores 79.0. This page calls that a decisive lead for uptime-kuma.