A · level
karakeep
89.2
30,641 stars · AGPL-3.0
Self-Hosted
Too close to call · 89.2 to 88.6
A · level
89.2
30,641 stars · AGPL-3.0
B · level
88.6
33,441 stars · license n/a
karakeep versus onyx 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; onyx is written mainly in Python. The composite score is 89.2 for karakeep and 88.6 for onyx.
onyx has 33,441 GitHub stars to karakeep's 30,641, a gap of 2,800 (1.09×). Forks are 1,657 for karakeep and 4,754 for onyx. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 88 versus 100.
Push history: karakeep was last pushed on 15 November 2026 (2 days ago), and onyx was last pushed on 17 November 2026 (0 days ago). Open issues stand at 726 for karakeep (0.024 per star) and 730 for onyx (0.022 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.
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. onyx is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 52 for karakeep and 30 for onyx. This is a procurement signal, not legal advice.
In Self-Hosted, both karakeep (30,641 stars) and onyx (33,441 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, onyx is unpriced in this catalog.
The lead is split. karakeep is furthest ahead on license flexibility (52 to 30), while onyx is furthest ahead on fork community (100 to 88). Choose the dimension a rollout cannot compromise on.
Composite score: karakeep 89.2, onyx 88.6. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | onyx |
|---|---|---|
| GitHub stars | 30,641 | 33,441 |
| Forks | 1,657 | 4,754 |
| Open issues | 726 | 730 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 88 | 100 |
| Issue health | 70 | 70 |
| License | 52 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 89.2 | 88.6 |
A self-hostable bookmark-everything app (links, notes and images) with AI-based automatic tagging and full text search
Open Source AI Platform - AI Chat with advanced features that works with every LLM
onyx has more GitHub stars: 33,441 versus 30,641 for karakeep. The gap is 2,800 stars.
onyx 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 onyx 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. onyx is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. karakeep scores 89.2 and onyx scores 88.6.