Skip to content
DevUtils Online

Self-Hosted

beszel vs new-api

beszel leads by 1.2 · narrow

A · leads

beszel

92.4

27,434 stars · MIT

B

new-api

91.2

52,087 stars · AGPL-3.0

beszel 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 92.4 for beszel and 91.2 for new-api.

new-api has 52,087 GitHub stars to beszel's 27,434, a gap of 24,653 (1.90×). Forks are 1,188 for beszel and 12,719 for new-api. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 75 versus 100.

Push history: beszel was last pushed on 15 November 2026 (2 days ago), and new-api was last pushed on 17 November 2026 (0 days ago). Open issues stand at 399 for beszel (0.015 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.

beszel is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. 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 96 for beszel and 52 for new-api. This is a procurement signal, not legal advice.

In Self-Hosted, both beszel (27,434 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: beszel is open source, new-api is open source.

The lead is split. beszel is furthest ahead on license flexibility (96 to 52), while new-api is furthest ahead on fork community (100 to 75). Choose the dimension a rollout cannot compromise on.

beszel finishes ahead at 92.4 against new-api at 91.2, a 1.2 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.

beszel versus new-api metrics
Signal beszel new-api
GitHub stars 27,434 52,087
Forks 1,188 12,719
Open issues 399 1,474
Adoption 94 100
Activity 100 100
Community 75 100
Issue health 84 70
License 96 52
Self-hosting 100 100
Composite 92.4 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, beszel or new-api?

new-api has more GitHub stars: 52,087 versus 27,434 for beszel. The gap is 24,653 stars.

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

new-api was pushed more recently: 17 November 2026 versus 15 November 2026 for beszel. That is 2 days apart.

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

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

beszel is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. 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 beszel vs new-api score?

beszel scores 92.4 and new-api scores 91.2. This page calls that a narrow lead for beszel.

Related comparisons