A
new-api
90.9
52,087 stars · AGPL-3.0
Self-Hosted
serviette leads by 3.3 · narrow
A
90.9
52,087 stars · AGPL-3.0
B · leads
94.2
58,707 stars · MIT
new-api versus serviette 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; serviette is written mainly in Python. The composite score is 90.9 for new-api and 94.2 for serviette.
serviette has 58,707 GitHub stars to new-api's 52,087, a gap of 6,620 (1.13×). Forks are 12,719 for new-api and 1,551 for serviette. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 78.
Push history: new-api was last pushed on 17 November 2026 (0 days ago), and serviette was last pushed on 10 November 2026 (7 days ago). Open issues stand at 1,474 for new-api (0.028 per star) and 6 for serviette (0.000 per star). Issue-health scores are 70 and 96; activity scores are 100 and 92.
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. serviette 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. License scores in this pair are 52 for new-api and 96 for serviette. This is a procurement signal, not legal advice.
In Self-Hosted, both new-api (52,087 stars) and serviette (58,707 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, serviette is open source.
The lead is split. new-api is furthest ahead on fork community (100 to 78), while serviette is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
serviette finishes ahead at 94.2 against new-api at 90.9, a 3.3 point narrow 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 | serviette |
|---|---|---|
| GitHub stars | 52,087 | 58,707 |
| Forks | 12,719 | 1,551 |
| Open issues | 1,474 | 6 |
| Adoption | 99 | 100 |
| Activity | 100 | 92 |
| Community | 100 | 78 |
| Issue health | 70 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.9 | 94.2 |
Open-source AI gateway. Self-hosted LLM gateway with OpenAI-, Claude- and Gemini-compatible APIs, model routing, access control, usage tracking and cost accounting.
A no-code RAG server that keeps answers in sync with your documents. Works with 8 vector databases. Built on Pathway.
serviette has more GitHub stars: 58,707 versus 52,087 for new-api. The gap is 6,620 stars.
new-api was pushed more recently: 17 November 2026 versus 10 November 2026 for serviette. That is 7 days apart.
Yes. This catalog marks both new-api and serviette 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. serviette 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
serviette scores 94.2 and new-api scores 90.9. This page calls that a narrow lead for serviette.