A
arcane
87.8
9,189 stars · BSD-3-Clause
Self-Hosted
uptime-kuma leads by 10.1 · clear
A
87.8
9,189 stars · BSD-3-Clause
B · leads
97.9
94,538 stars · MIT
arcane 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. arcane is written mainly in Go; uptime-kuma is written mainly in JavaScript. The composite score is 87.8 for arcane and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to arcane's 9,189, a gap of 85,349 (10.29×). Forks are 501 for arcane and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 68 versus 100.
Push history: arcane was last pushed on 17 November 2026 (0 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 11 for arcane (0.001 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
arcane is listed as BSD-3-Clause, 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. License scores in this pair are 96 for arcane and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both arcane (9,189 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: arcane is open source, uptime-kuma is open source.
The lead is split. arcane is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on fork community (100 to 68). Choose the dimension a rollout cannot compromise on.
uptime-kuma finishes ahead at 97.9 against arcane 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 | arcane | uptime-kuma |
|---|---|---|
| GitHub stars | 9,189 | 94,538 |
| Forks | 501 | 8,860 |
| Open issues | 11 | 852 |
| Adoption | 80 | 100 |
| Activity | 100 | 100 |
| Community | 68 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.8 | 97.9 |
Modern Docker Management, Designed for Everyone
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 9,189 for arcane. The gap is 85,349 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both arcane and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
arcane is listed as BSD-3-Clause, 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 arcane scores 87.8. This page calls that a clear lead for uptime-kuma.