A
navidrome
87.5
24,808 stars · GPL-3.0
Self-Hosted
Stirling-PDF leads by 3.7 · narrow
A
87.5
24,808 stars · GPL-3.0
B · leads
91.2
96,832 stars · license n/a
navidrome versus Stirling-PDF 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; Stirling-PDF is written mainly in TypeScript. The composite score is 87.5 for navidrome and 91.2 for Stirling-PDF.
Stirling-PDF has 96,832 GitHub stars to navidrome's 24,808, a gap of 72,024 (3.90×). Forks are 1,822 for navidrome and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 82 versus 100.
Push history: navidrome was last pushed on 17 November 2026 (0 days ago), and Stirling-PDF was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for navidrome (0.013 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 84 and 96; 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. Stirling-PDF is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 64 for navidrome and 30 for Stirling-PDF. This is a procurement signal, not legal advice.
In Self-Hosted, both navidrome (24,808 stars) and Stirling-PDF (96,832 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, Stirling-PDF is unpriced in this catalog.
The lead is split. navidrome is furthest ahead on license flexibility (64 to 30), while Stirling-PDF is furthest ahead on fork community (100 to 82). Choose the dimension a rollout cannot compromise on.
Stirling-PDF finishes ahead at 91.2 against navidrome at 87.5, a 3.7 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 | navidrome | Stirling-PDF |
|---|---|---|
| GitHub stars | 24,808 | 96,832 |
| Forks | 1,822 | 9,373 |
| Open issues | 318 | 448 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 82 | 100 |
| Issue health | 84 | 96 |
| License | 64 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 87.5 | 91.2 |
🎧 Your Personal Streaming Service
#1 PDF Application on GitHub that lets you edit PDFs on any device anywhere
Stirling-PDF has more GitHub stars: 96,832 versus 24,808 for navidrome. The gap is 72,024 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both navidrome and Stirling-PDF as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. Stirling-PDF is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Stirling-PDF scores 91.2 and navidrome scores 87.5. This page calls that a narrow lead for Stirling-PDF.