A
glance
85.5
38,270 stars · AGPL-3.0
Self-Hosted
uptime-kuma leads by 12.4 · clear
A
85.5
38,270 stars · AGPL-3.0
B · leads
97.9
94,538 stars · MIT
glance 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. glance is written mainly in Go; uptime-kuma is written mainly in JavaScript. The composite score is 85.5 for glance and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to glance's 38,270, a gap of 56,268 (2.47×). Forks are 1,524 for glance and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 81 versus 100.
Push history: glance was last pushed on 07 November 2026 (10 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 323 for glance (0.008 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 92 and 100.
glance 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 glance and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both glance (38,270 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: glance is open source, uptime-kuma 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 license flexibility at 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against glance at 85.5, a 12.4 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 | glance | uptime-kuma |
|---|---|---|
| GitHub stars | 38,270 | 94,538 |
| Forks | 1,524 | 8,860 |
| Open issues | 323 | 852 |
| Adoption | 92 | 100 |
| Activity | 92 | 100 |
| Community | 81 | 100 |
| Issue health | 84 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 85.5 | 97.9 |
A self-hosted dashboard that puts all your feeds in one place
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 38,270 for glance. The gap is 56,268 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 07 November 2026 for glance. That is 10 days apart.
Yes. This catalog marks both glance and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
glance 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 glance scores 85.5. This page calls that a clear lead for uptime-kuma.