A
karakeep
86.6
30,641 stars · AGPL-3.0
Self-Hosted
new-api leads by 4.6 · narrow
A
86.6
30,641 stars · AGPL-3.0
B · leads
91.2
52,087 stars · AGPL-3.0
karakeep 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. karakeep is written mainly in TypeScript; new-api is written mainly in Go. The composite score is 86.6 for karakeep and 91.2 for new-api.
new-api has 52,087 GitHub stars to karakeep's 30,641, a gap of 21,446 (1.70×). Forks are 1,657 for karakeep and 12,719 for new-api. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 78 versus 100.
Push history: karakeep was last pushed on 15 November 2026 (2 days ago), and new-api was last pushed on 17 November 2026 (0 days ago). Open issues stand at 726 for karakeep (0.024 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.
Both karakeep and new-api are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Self-Hosted, both karakeep (30,641 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: karakeep is open source, new-api is open source.
new-api is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 22 points (78 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
new-api finishes ahead at 91.2 against karakeep at 86.6, a 4.6 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 | karakeep | new-api |
|---|---|---|
| GitHub stars | 30,641 | 52,087 |
| Forks | 1,657 | 12,719 |
| Open issues | 726 | 1,474 |
| Adoption | 95 | 100 |
| Activity | 100 | 100 |
| Community | 78 | 100 |
| Issue health | 70 | 70 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 86.6 | 91.2 |
A self-hostable bookmark-everything app (links, notes and images) with AI-based automatic tagging and full text search
Open-source AI gateway. Self-hosted LLM gateway with OpenAI-, Claude- and Gemini-compatible APIs, model routing, access control, usage tracking and cost accounting.
new-api has more GitHub stars: 52,087 versus 30,641 for karakeep. The gap is 21,446 stars.
new-api was pushed more recently: 17 November 2026 versus 15 November 2026 for karakeep. That is 2 days apart.
Yes. This catalog marks both karakeep and new-api as self-hostable. Confirm each project's deploy docs before you plan a migration.
karakeep 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. 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.
new-api scores 91.2 and karakeep scores 86.6. This page calls that a narrow lead for new-api.