Skip to content
DevUtils Online

Self-Hosted

navidrome vs uptime-kuma

uptime-kuma leads by 10.2 · clear

navidrome 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. navidrome is written mainly in Go; uptime-kuma is written mainly in JavaScript. The composite score is 87.7 for navidrome and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to navidrome's 24,808, a gap of 69,730 (3.81×). Forks are 1,822 for navidrome and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 83 versus 100.

Push history: navidrome 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 318 for navidrome (0.013 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

navidrome 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. 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 64 for navidrome and 96 for uptime-kuma. This is a procurement signal, not legal advice.

In Self-Hosted, both navidrome (24,808 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: navidrome is open source, uptime-kuma is open source.

uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 32 points (64 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).

uptime-kuma finishes ahead at 97.9 against navidrome at 87.7, a 10.2 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

navidrome versus uptime-kuma metrics
Signal navidrome uptime-kuma
GitHub stars 24,808 94,538
Forks 1,822 8,860
Open issues 318 852
Adoption 88 100
Activity 100 100
Community 83 100
Issue health 84 84
License 64 96
Self-hosting 100 100
Composite 87.7 97.9

Questions this page answers

Which has more GitHub stars, navidrome or uptime-kuma?

uptime-kuma has more GitHub stars: 94,538 versus 24,808 for navidrome. The gap is 69,730 stars.

Which was updated more recently, navidrome or uptime-kuma?

Both were last pushed on 17 November 2026.

Can I self-host both navidrome and uptime-kuma?

Yes. This catalog marks both navidrome and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, navidrome or uptime-kuma?

navidrome 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. 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.

Who wins the navidrome vs uptime-kuma score?

uptime-kuma scores 97.9 and navidrome scores 87.7. This page calls that a clear lead for uptime-kuma.

Related comparisons