Skip to content
DevUtils Online

Self-Hosted

jan vs new-api

new-api leads by 3.7 · narrow

A

jan

87.5

45,760 stars · license n/a

B · leads

new-api

91.2

52,087 stars · AGPL-3.0

jan 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. jan is written mainly in Rust; new-api is written mainly in Go. The composite score is 87.5 for jan and 91.2 for new-api.

new-api has 52,087 GitHub stars to jan's 45,760, a gap of 6,327 (1.14×). Forks are 3,179 for jan and 12,719 for new-api. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 85 versus 100.

Push history: jan 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 580 for jan (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.

jan 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. 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 30 for jan and 52 for new-api. This is a procurement signal, not legal advice.

In Self-Hosted, both jan (45,760 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: jan is unpriced in this catalog, new-api is open source.

The lead is split. jan is furthest ahead on issue health (84 to 70), while new-api is furthest ahead on license flexibility (52 to 30). Choose the dimension a rollout cannot compromise on.

new-api finishes ahead at 91.2 against jan at 87.5, a 3.7 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.

jan versus new-api metrics
Signal jan new-api
GitHub stars 45,760 52,087
Forks 3,179 12,719
Open issues 580 1,474
Adoption 99 100
Activity 100 100
Community 85 100
Issue health 84 70
License 30 52
Self-hosting 100 100
Composite 87.5 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, jan or new-api?

new-api has more GitHub stars: 52,087 versus 45,760 for jan. The gap is 6,327 stars.

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

Both were last pushed on 17 November 2026.

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

Yes. This catalog marks both jan 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, jan or new-api?

jan 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. 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 jan vs new-api score?

new-api scores 91.2 and jan scores 87.5. This page calls that a narrow lead for new-api.

Related comparisons