A · level
memos
97.8
64,520 stars · MIT
Self-Hosted
Too close to call · 97.8 to 97.9
A · level
97.8
64,520 stars · MIT
B · level
97.9
79,671 stars · Apache-2.0
memos versus unsloth 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; unsloth is written mainly in Python. The composite score is 97.8 for memos and 97.9 for unsloth.
unsloth has 79,671 GitHub stars to memos's 64,520, a gap of 15,151 (1.23×). Forks are 4,972 for memos and 7,439 for unsloth. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 96 versus 100.
Push history: memos was last pushed on 17 November 2026 (0 days ago), and unsloth was last pushed on 17 November 2026 (0 days ago). Open issues stand at 63 for memos (0.001 per star) and 469 for unsloth (0.006 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. unsloth 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 unsloth. This is a procurement signal, not legal advice.
In Self-Hosted, both memos (64,520 stars) and unsloth (79,671 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, unsloth is open source.
The lead is split. memos is furthest ahead on issue health (96 to 84), while unsloth is furthest ahead on fork community (100 to 96). Choose the dimension a rollout cannot compromise on.
Composite score: memos 97.8, unsloth 97.9. 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 | memos | unsloth |
|---|---|---|
| GitHub stars | 64,520 | 79,671 |
| Forks | 4,972 | 7,439 |
| Open issues | 63 | 469 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 96 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.8 | 97.9 |
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.
Local UI to run and train LLMs and diffusion models. Supports GGUF, MLX, Qwen3.8, DeepSeek-V4.1, MiniMax-H3, Gemma 4, FLUX and more.
unsloth has more GitHub stars: 79,671 versus 64,520 for memos. The gap is 15,151 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both memos and unsloth 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. unsloth 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.
Neither tool clears a one-point margin. memos scores 97.8 and unsloth scores 97.9.