A · leads
uptime-kuma
97.9
94,538 stars · MIT
Self-Hosted
uptime-kuma leads by 10.1 · clear
A · leads
97.9
94,538 stars · MIT
B
87.8
8,729 stars · Apache-2.0
uptime-kuma versus utopia 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; utopia is written mainly in Rust. The composite score is 97.9 for uptime-kuma and 87.8 for utopia.
uptime-kuma has 94,538 GitHub stars to utopia's 8,729, a gap of 85,809 (10.83×). Forks are 8,860 for uptime-kuma and 1,192 for utopia. On the log scale used inside this pair, adoption is 100 versus 79, and the fork community is 100 versus 78.
Push history: uptime-kuma was last pushed on 17 November 2026 (0 days ago), and utopia was last pushed on 17 November 2026 (0 days ago). Open issues stand at 852 for uptime-kuma (0.009 per star) and 70 for utopia (0.008 per star). Issue-health scores are 84 and 84; 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. utopia is listed as Apache-2.0, 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 96 for uptime-kuma and 96 for utopia. This is a procurement signal, not legal advice.
In Self-Hosted, both uptime-kuma (94,538 stars) and utopia (8,729 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, utopia 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 (100 vs 78), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against utopia at 87.8, a 10.1 point clear 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 | utopia |
|---|---|---|
| GitHub stars | 94,538 | 8,729 |
| Forks | 8,860 | 1,192 |
| Open issues | 852 | 70 |
| Adoption | 100 | 79 |
| Activity | 100 | 100 |
| Community | 100 | 78 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 87.8 |
A fancy self-hosted monitoring tool
World's first open-source enterprise world model.
uptime-kuma has more GitHub stars: 94,538 versus 8,729 for utopia. The gap is 85,809 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both uptime-kuma and utopia 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. utopia is listed as Apache-2.0, 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 utopia scores 87.8. This page calls that a clear lead for uptime-kuma.