A
core
85.1
8,853 stars · AGPL-3.0
Self-Hosted
memos leads by 14.0 · clear
A
85.1
8,853 stars · AGPL-3.0
B · leads
99.1
64,520 stars · MIT
core versus memos is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. core is written mainly in PHP; memos is written mainly in Go. The composite score is 85.1 for core and 99.1 for memos.
memos has 64,520 GitHub stars to core's 8,853, a gap of 55,667 (7.29×). Forks are 2,061 for core and 4,972 for memos. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 90 versus 100.
Push history: core was last pushed on 16 November 2026 (1 day ago), and memos was last pushed on 17 November 2026 (0 days ago). Open issues stand at 146 for core (0.016 per star) and 63 for memos (0.001 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
core 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. memos 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 core and 96 for memos. This is a procurement signal, not legal advice.
In Self-Hosted, both core (8,853 stars) and memos (64,520 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: core is open source, memos is open source.
memos 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 (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
memos finishes ahead at 99.1 against core at 85.1, a 14.0 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 | core | memos |
|---|---|---|
| GitHub stars | 8,853 | 64,520 |
| Forks | 2,061 | 4,972 |
| Open issues | 146 | 63 |
| Adoption | 82 | 100 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 84 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 85.1 | 99.1 |
:cloud: ownCloud web server core (Files, DAV, etc.)
Memos is an open-source, self-hosted note-taking app that brings your everyday thoughts together in a personal timeline. Your data stays yours, and you choose what to keep private or share.
memos has more GitHub stars: 64,520 versus 8,853 for core. The gap is 55,667 stars.
memos was pushed more recently: 17 November 2026 versus 16 November 2026 for core. That is 1 days apart.
Yes. This catalog marks both core and memos as self-hostable. Confirm each project's deploy docs before you plan a migration.
core 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. memos 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.
memos scores 99.1 and core scores 85.1. This page calls that a clear lead for memos.