A
new-api
89.5
52,087 stars · AGPL-3.0
Self-Hosted
uptime-kuma leads by 7.9 · clear
A
89.5
52,087 stars · AGPL-3.0
B · leads
97.4
94,538 stars · MIT
new-api versus uptime-kuma 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; uptime-kuma is written mainly in JavaScript. The composite score is 89.5 for new-api and 97.4 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to new-api's 52,087, a gap of 42,451 (1.82×). Forks are 12,719 for new-api and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 100 versus 96.
Push history: new-api was last pushed on 17 November 2026 (0 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,474 for new-api (0.028 per star) and 852 for uptime-kuma (0.009 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. uptime-kuma 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 uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both new-api (52,087 stars) and uptime-kuma (94,538 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, uptime-kuma is open source.
The lead is split. new-api is furthest ahead on fork community (100 to 96), while uptime-kuma is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
uptime-kuma finishes ahead at 97.4 against new-api at 89.5, a 7.9 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 | uptime-kuma |
|---|---|---|
| GitHub stars | 52,087 | 94,538 |
| Forks | 12,719 | 8,860 |
| Open issues | 1,474 | 852 |
| Adoption | 95 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 96 |
| Issue health | 70 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.5 | 97.4 |
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 fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 52,087 for new-api. The gap is 42,451 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both new-api and uptime-kuma 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. uptime-kuma 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.
uptime-kuma scores 97.4 and new-api scores 89.5. This page calls that a clear lead for uptime-kuma.