A · leads
memos
99.1
64,520 stars · MIT
Self-Hosted
memos leads by 18.5 · decisive
A · leads
99.1
64,520 stars · MIT
B
80.6
9,469 stars · AGPL-3.0
memos versus wealthfolio 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; wealthfolio is written mainly in Rust. The composite score is 99.1 for memos and 80.6 for wealthfolio.
memos has 64,520 GitHub stars to wealthfolio's 9,469, a gap of 55,051 (6.81×). Forks are 4,972 for memos and 829 for wealthfolio. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 79.
Push history: memos was last pushed on 17 November 2026 (0 days ago), and wealthfolio was last pushed on 17 November 2026 (0 days ago). Open issues stand at 63 for memos (0.001 per star) and 537 for wealthfolio (0.057 per star). Issue-health scores are 96 and 52; 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. wealthfolio 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. License scores in this pair are 96 for memos and 52 for wealthfolio. This is a procurement signal, not legal advice.
In Self-Hosted, both memos (64,520 stars) and wealthfolio (9,469 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, wealthfolio is open source.
memos is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is issue health at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
memos finishes ahead at 99.1 against wealthfolio at 80.6, a 18.5 point decisive 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 | wealthfolio |
|---|---|---|
| GitHub stars | 64,520 | 9,469 |
| Forks | 4,972 | 829 |
| Open issues | 63 | 537 |
| Adoption | 100 | 83 |
| Activity | 100 | 100 |
| Community | 100 | 79 |
| Issue health | 96 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 80.6 |
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 beautiful, private, local-first personal finance tracker. Investments, net worth, spending, and simulations.
memos has more GitHub stars: 64,520 versus 9,469 for wealthfolio. The gap is 55,051 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both memos and wealthfolio 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. wealthfolio 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
memos scores 99.1 and wealthfolio scores 80.6. This page calls that a decisive lead for memos.