Skip to content
DevUtils Online

Self-Hosted

CasaOS vs new-api

CasaOS leads by 1.7 · narrow

A · leads

CasaOS

92.9

37,656 stars · Apache-2.0

B

new-api

91.2

52,087 stars · AGPL-3.0

CasaOS 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.9 for CasaOS and 91.2 for new-api.

new-api has 52,087 GitHub stars to CasaOS's 37,656, a gap of 14,431 (1.38×). Forks are 2,222 for CasaOS and 12,719 for new-api. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 82 versus 100.

Push history: CasaOS 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 844 for CasaOS (0.022 per star) and 1,474 for new-api (0.028 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.

CasaOS is listed as Apache-2.0, 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 CasaOS and 52 for new-api. This is a procurement signal, not legal advice.

In Self-Hosted, both CasaOS (37,656 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: CasaOS is open source, new-api is open source.

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

CasaOS finishes ahead at 92.9 against new-api at 91.2, a 1.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.

CasaOS versus new-api metrics
Signal CasaOS new-api
GitHub stars 37,656 52,087
Forks 2,222 12,719
Open issues 844 1,474
Adoption 97 100
Activity 100 100
Community 82 100
Issue health 70 70
License 96 52
Self-hosting 100 100
Composite 92.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, CasaOS or new-api?

new-api has more GitHub stars: 52,087 versus 37,656 for CasaOS. The gap is 14,431 stars.

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

Both were last pushed on 17 November 2026.

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

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

CasaOS is listed as Apache-2.0, 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 CasaOS vs new-api score?

CasaOS scores 92.9 and new-api scores 91.2. This page calls that a narrow lead for CasaOS.

Related comparisons