A
glance
90.5
38,270 stars · AGPL-3.0
Self-Hosted
navidrome leads by 2.2 · narrow
A
90.5
38,270 stars · AGPL-3.0
B · leads
92.7
24,808 stars · GPL-3.0
glance versus navidrome is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 90.5 for glance and 92.7 for navidrome.
glance has 38,270 GitHub stars to navidrome's 24,808, a gap of 13,462 (1.54×). Forks are 1,524 for glance and 1,822 for navidrome. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 98 versus 100.
Push history: glance was last pushed on 07 November 2026 (10 days ago), and navidrome was last pushed on 17 November 2026 (0 days ago). Open issues stand at 323 for glance (0.008 per star) and 318 for navidrome (0.013 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. 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. License scores in this pair are 52 for glance and 64 for navidrome. This is a procurement signal, not legal advice.
In Self-Hosted, both glance (38,270 stars) and navidrome (24,808 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, navidrome is open source.
The lead is split. glance is furthest ahead on adoption (100 to 96), while navidrome is furthest ahead on license flexibility (64 to 52). Choose the dimension a rollout cannot compromise on.
navidrome finishes ahead at 92.7 against glance at 90.5, a 2.2 point narrow 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 | navidrome |
|---|---|---|
| GitHub stars | 38,270 | 24,808 |
| Forks | 1,524 | 1,822 |
| Open issues | 323 | 318 |
| Adoption | 100 | 96 |
| Activity | 92 | 100 |
| Community | 98 | 100 |
| Issue health | 84 | 84 |
| License | 52 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 90.5 | 92.7 |
A self-hosted dashboard that puts all your feeds in one place
🎧 Your Personal Streaming Service
glance has more GitHub stars: 38,270 versus 24,808 for navidrome. The gap is 13,462 stars.
navidrome 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 navidrome 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
navidrome scores 92.7 and glance scores 90.5. This page calls that a narrow lead for navidrome.