A · leads
memos
99.1
64,520 stars · MIT
Self-Hosted
memos leads by 7.7 · clear
A · leads
99.1
64,520 stars · MIT
B
91.4
15,349 stars · Apache-2.0
memos versus openship is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. memos is written mainly in Go; openship is written mainly in TypeScript. The composite score is 99.1 for memos and 91.4 for openship.
memos has 64,520 GitHub stars to openship's 15,349, a gap of 49,171 (4.20×). Forks are 4,972 for memos and 1,415 for openship. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 85.
Push history: memos was last pushed on 17 November 2026 (0 days ago), and openship was last pushed on 17 November 2026 (0 days ago). Open issues stand at 63 for memos (0.001 per star) and 177 for openship (0.012 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
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. openship is listed as Apache-2.0, 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 96 for memos and 96 for openship. This is a procurement signal, not legal advice.
In Self-Hosted, both memos (64,520 stars) and openship (15,349 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: memos is open source, openship is open source.
memos is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 15 points (100 vs 85), and the tightest is self-hosting at 0 points (100 vs 100).
memos finishes ahead at 99.1 against openship at 91.4, a 7.7 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 | memos | openship |
|---|---|---|
| GitHub stars | 64,520 | 15,349 |
| Forks | 4,972 | 1,415 |
| Open issues | 63 | 177 |
| Adoption | 100 | 87 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 91.4 |
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.
Self-hosted deployment platform
memos has more GitHub stars: 64,520 versus 15,349 for openship. The gap is 49,171 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both memos and openship as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. openship is listed as Apache-2.0, 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 openship scores 91.4. This page calls that a clear lead for memos.