A · level
navidrome
92.0
24,808 stars · GPL-3.0
Self-Hosted
Too close to call · 92.0 to 92.6
A · level
92.0
24,808 stars · GPL-3.0
B · level
92.6
38,974 stars · AGPL-3.0
navidrome versus Trilium 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; Trilium is written mainly in TypeScript. The composite score is 92.0 for navidrome and 92.6 for Trilium.
Trilium has 38,974 GitHub stars to navidrome's 24,808, a gap of 14,166 (1.57×). Forks are 1,822 for navidrome and 2,630 for Trilium. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 95 versus 100.
Push history: navidrome was last pushed on 17 November 2026 (0 days ago), and Trilium was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for navidrome (0.013 per star) and 574 for Trilium (0.015 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. Trilium 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. License scores in this pair are 64 for navidrome and 52 for Trilium. This is a procurement signal, not legal advice.
In Self-Hosted, both navidrome (24,808 stars) and Trilium (38,974 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, Trilium is open source.
The lead is split. navidrome is furthest ahead on license flexibility (64 to 52), while Trilium is furthest ahead on fork community (100 to 95). Choose the dimension a rollout cannot compromise on.
Composite score: navidrome 92.0, Trilium 92.6. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | Trilium |
|---|---|---|
| GitHub stars | 24,808 | 38,974 |
| Forks | 1,822 | 2,630 |
| Open issues | 318 | 574 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 84 | 84 |
| License | 64 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 92.0 | 92.6 |
🎧 Your Personal Streaming Service
Build your personal knowledge base with Trilium Notes
Trilium has more GitHub stars: 38,974 versus 24,808 for navidrome. The gap is 14,166 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both navidrome and Trilium 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. Trilium 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. navidrome scores 92.0 and Trilium scores 92.6.