Skip to content
DevUtils Online

Self-Hosted

navidrome vs new-api

new-api leads by 2.3 · narrow

B · leads

new-api

91.2

52,087 stars · AGPL-3.0

navidrome versus new-api 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 88.9 for navidrome and 91.2 for new-api.

new-api has 52,087 GitHub stars to navidrome's 24,808, a gap of 27,279 (2.10×). Forks are 1,822 for navidrome and 12,719 for new-api. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 79 versus 100.

Push history: navidrome was last pushed on 17 November 2026 (0 days ago), and new-api was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for navidrome (0.013 per star) and 1,474 for new-api (0.028 per star). Issue-health scores are 84 and 70; 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. new-api 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 new-api. This is a procurement signal, not legal advice.

In Self-Hosted, both navidrome (24,808 stars) and new-api (52,087 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, new-api is open source.

The lead is split. navidrome is furthest ahead on issue health (84 to 70), while new-api is furthest ahead on fork community (100 to 79). Choose the dimension a rollout cannot compromise on.

new-api finishes ahead at 91.2 against navidrome at 88.9, a 2.3 point narrow 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 new-api metrics
Signal navidrome new-api
GitHub stars 24,808 52,087
Forks 1,822 12,719
Open issues 318 1,474
Adoption 93 100
Activity 100 100
Community 79 100
Issue health 84 70
License 64 52
Self-hosting 100 100
Composite 88.9 91.2

new-api

Open-source AI gateway. Self-hosted LLM gateway with OpenAI-, Claude- and Gemini-compatible APIs, model routing, access control, usage tracking and cost accounting.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, navidrome or new-api?

new-api has more GitHub stars: 52,087 versus 24,808 for navidrome. The gap is 27,279 stars.

Which was updated more recently, navidrome or new-api?

Both were last pushed on 17 November 2026.

Can I self-host both navidrome and new-api?

Yes. This catalog marks both navidrome and new-api 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 new-api?

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. new-api 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.

Who wins the navidrome vs new-api score?

new-api scores 91.2 and navidrome scores 88.9. This page calls that a narrow lead for new-api.

Related comparisons