A
new-api
89.9
52,087 stars · AGPL-3.0
Self-Hosted
unsloth leads by 7.2 · clear
A
89.9
52,087 stars · AGPL-3.0
B · leads
97.1
79,671 stars · Apache-2.0
new-api versus unsloth is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. new-api is written mainly in Go; unsloth is written mainly in Python. The composite score is 89.9 for new-api and 97.1 for unsloth.
unsloth has 79,671 GitHub stars to new-api's 52,087, a gap of 27,584 (1.53×). Forks are 12,719 for new-api and 7,439 for unsloth. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 100 versus 94.
Push history: new-api was last pushed on 17 November 2026 (0 days ago), and unsloth was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,474 for new-api (0.028 per star) and 469 for unsloth (0.006 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
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. unsloth 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. License scores in this pair are 52 for new-api and 96 for unsloth. This is a procurement signal, not legal advice.
In Self-Hosted, both new-api (52,087 stars) and unsloth (79,671 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: new-api is open source, unsloth is open source.
The lead is split. new-api is furthest ahead on fork community (100 to 94), while unsloth is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
unsloth finishes ahead at 97.1 against new-api at 89.9, a 7.2 point clear margin under the published weights.
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 | new-api | unsloth |
|---|---|---|
| GitHub stars | 52,087 | 79,671 |
| Forks | 12,719 | 7,439 |
| Open issues | 1,474 | 469 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 94 |
| Issue health | 70 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.9 | 97.1 |
Open-source AI gateway. Self-hosted LLM gateway with OpenAI-, Claude- and Gemini-compatible APIs, model routing, access control, usage tracking and cost accounting.
Local UI to run and train LLMs and diffusion models. Supports GGUF, MLX, Qwen3.8, DeepSeek-V4.1, MiniMax-H3, Gemma 4, FLUX and more.
unsloth has more GitHub stars: 79,671 versus 52,087 for new-api. The gap is 27,584 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both new-api and unsloth as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. unsloth 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
unsloth scores 97.1 and new-api scores 89.9. This page calls that a clear lead for unsloth.