A · leads
gogs
97.9
47,942 stars · MIT
Self-Hosted
gogs leads by 9.9 · clear
A · leads
97.9
47,942 stars · MIT
B
88.0
30,641 stars · AGPL-3.0
gogs versus karakeep is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. gogs is written mainly in Go; karakeep is written mainly in TypeScript. The composite score is 97.9 for gogs and 88.0 for karakeep.
gogs has 47,942 GitHub stars to karakeep's 30,641, a gap of 17,301 (1.56×). Forks are 5,081 for gogs and 1,657 for karakeep. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 87.
Push history: gogs was last pushed on 17 November 2026 (0 days ago), and karakeep was last pushed on 15 November 2026 (2 days ago). Open issues stand at 837 for gogs (0.017 per star) and 726 for karakeep (0.024 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
gogs 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. 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. License scores in this pair are 96 for gogs and 52 for karakeep. This is a procurement signal, not legal advice.
In Self-Hosted, both gogs (47,942 stars) and karakeep (30,641 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: gogs is open source, karakeep is open source.
gogs is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
gogs finishes ahead at 97.9 against karakeep at 88.0, a 9.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 | gogs | karakeep |
|---|---|---|
| GitHub stars | 47,942 | 30,641 |
| Forks | 5,081 | 1,657 |
| Open issues | 837 | 726 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 87 |
| Issue health | 84 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 88.0 |
The painless way to host your own Git service
A self-hostable bookmark-everything app (links, notes and images) with AI-based automatic tagging and full text search
gogs has more GitHub stars: 47,942 versus 30,641 for karakeep. The gap is 17,301 stars.
gogs was pushed more recently: 17 November 2026 versus 15 November 2026 for karakeep. That is 2 days apart.
Yes. This catalog marks both gogs and karakeep as self-hostable. Confirm each project's deploy docs before you plan a migration.
gogs 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
gogs scores 97.9 and karakeep scores 88.0. This page calls that a clear lead for gogs.