A · leads
memos
99.1
64,520 stars · MIT
Self-Hosted
memos leads by 4.0 · narrow
A · leads
99.1
64,520 stars · MIT
B
95.1
58,707 stars · MIT
memos versus serviette 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; serviette is written mainly in Python. The composite score is 99.1 for memos and 95.1 for serviette.
memos has 64,520 GitHub stars to serviette's 58,707, a gap of 5,813 (1.10×). Forks are 4,972 for memos and 1,551 for serviette. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 86.
Push history: memos was last pushed on 17 November 2026 (0 days ago), and serviette was last pushed on 10 November 2026 (7 days ago). Open issues stand at 63 for memos (0.001 per star) and 6 for serviette (0.000 per star). Issue-health scores are 96 and 96; activity scores are 100 and 92.
Both memos and serviette are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Self-Hosted, both memos (64,520 stars) and serviette (58,707 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, serviette is open source.
memos is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is fork community at 14 points (100 vs 86), and the tightest is self-hosting at 0 points (100 vs 100).
memos finishes ahead at 99.1 against serviette at 95.1, a 4.0 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 | memos | serviette |
|---|---|---|
| GitHub stars | 64,520 | 58,707 |
| Forks | 4,972 | 1,551 |
| Open issues | 63 | 6 |
| Adoption | 100 | 99 |
| Activity | 100 | 92 |
| Community | 100 | 86 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 95.1 |
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.
A no-code RAG server that keeps answers in sync with your documents. Works with 8 vector databases. Built on Pathway.
memos has more GitHub stars: 64,520 versus 58,707 for serviette. The gap is 5,813 stars.
memos was pushed more recently: 17 November 2026 versus 10 November 2026 for serviette. That is 7 days apart.
Yes. This catalog marks both memos and serviette 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. serviette 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 serviette scores 95.1. This page calls that a narrow lead for memos.