A · leads
memos
99.1
64,520 stars · MIT
Self-Hosted
memos leads by 4.9 · narrow
A · leads
99.1
64,520 stars · MIT
B
94.2
37,875 stars · Apache-2.0
memos versus QwenPaw 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; QwenPaw is written mainly in TypeScript. The composite score is 99.1 for memos and 94.2 for QwenPaw.
memos has 64,520 GitHub stars to QwenPaw's 37,875, a gap of 26,645 (1.70×). Forks are 4,972 for memos and 3,293 for QwenPaw. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 95.
Push history: memos was last pushed on 17 November 2026 (0 days ago), and QwenPaw was last pushed on 17 November 2026 (0 days ago). Open issues stand at 63 for memos (0.001 per star) and 1,167 for QwenPaw (0.031 per star). Issue-health scores are 96 and 70; 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. QwenPaw 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 QwenPaw. This is a procurement signal, not legal advice.
In Self-Hosted, both memos (64,520 stars) and QwenPaw (37,875 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, QwenPaw 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 issue health at 26 points (96 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).
memos finishes ahead at 99.1 against QwenPaw at 94.2, a 4.9 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 | QwenPaw |
|---|---|---|
| GitHub stars | 64,520 | 37,875 |
| Forks | 4,972 | 3,293 |
| Open issues | 63 | 1,167 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 95 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 94.2 |
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.
Your Personal AI Assistant; easy to install, deploy on your own machine or on the cloud; supports multiple chat apps with easily extensible capabilities.
memos has more GitHub stars: 64,520 versus 37,875 for QwenPaw. The gap is 26,645 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both memos and QwenPaw 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. QwenPaw 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 QwenPaw scores 94.2. This page calls that a narrow lead for memos.