A
new-api
91.2
52,087 stars · AGPL-3.0
Self-Hosted
reactive-resume leads by 6.1 · narrow
A
91.2
52,087 stars · AGPL-3.0
B · leads
97.3
45,854 stars · MIT
new-api versus reactive-resume 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; reactive-resume is written mainly in TypeScript. The composite score is 91.2 for new-api and 97.3 for reactive-resume.
new-api has 52,087 GitHub stars to reactive-resume's 45,854, a gap of 6,233 (1.14×). Forks are 12,719 for new-api and 4,959 for reactive-resume. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 90.
Push history: new-api was last pushed on 17 November 2026 (0 days ago), and reactive-resume was last pushed on 16 November 2026 (1 day ago). Open issues stand at 1,474 for new-api (0.028 per star) and 7 for reactive-resume (0.000 per star). Issue-health scores are 70 and 96; 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. reactive-resume 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 reactive-resume. This is a procurement signal, not legal advice.
In Self-Hosted, both new-api (52,087 stars) and reactive-resume (45,854 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, reactive-resume is open source.
The lead is split. new-api is furthest ahead on fork community (100 to 90), while reactive-resume is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
reactive-resume finishes ahead at 97.3 against new-api at 91.2, a 6.1 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 | reactive-resume |
|---|---|---|
| GitHub stars | 52,087 | 45,854 |
| Forks | 12,719 | 4,959 |
| Open issues | 1,474 | 7 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 100 | 90 |
| Issue health | 70 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.2 | 97.3 |
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 one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
new-api has more GitHub stars: 52,087 versus 45,854 for reactive-resume. The gap is 6,233 stars.
new-api was pushed more recently: 17 November 2026 versus 16 November 2026 for reactive-resume. That is 1 days apart.
Yes. This catalog marks both new-api and reactive-resume 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. reactive-resume 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.
reactive-resume scores 97.3 and new-api scores 91.2. This page calls that a narrow lead for reactive-resume.