Skip to content
DevUtils Online

Self-Hosted

memos vs rakazo

memos leads by 10.5 · clear

A · leads

memos

99.1

64,520 stars · MIT

B

rakazo

88.6

8,995 stars · Apache-2.0

memos versus rakazo 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; rakazo is written mainly in TypeScript. The composite score is 99.1 for memos and 88.6 for rakazo.

memos has 64,520 GitHub stars to rakazo's 8,995, a gap of 55,525 (7.17×). Forks are 4,972 for memos and 1,614 for rakazo. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 87.

Push history: memos was last pushed on 17 November 2026 (0 days ago), and rakazo was last pushed on 17 November 2026 (0 days ago). Open issues stand at 63 for memos (0.001 per star) and 236 for rakazo (0.026 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. rakazo 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 rakazo. This is a procurement signal, not legal advice.

In Self-Hosted, both memos (64,520 stars) and rakazo (8,995 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, rakazo 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 rakazo at 88.6, a 10.5 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

memos versus rakazo metrics
Signal memos rakazo
GitHub stars 64,520 8,995
Forks 4,972 1,614
Open issues 63 236
Adoption 100 82
Activity 100 100
Community 100 87
Issue health 96 70
License 96 96
Self-hosting 100 100
Composite 99.1 88.6

memos

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, memos or rakazo?

memos has more GitHub stars: 64,520 versus 8,995 for rakazo. The gap is 55,525 stars.

Which was updated more recently, memos or rakazo?

Both were last pushed on 17 November 2026.

Can I self-host both memos and rakazo?

Yes. This catalog marks both memos and rakazo as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, memos or rakazo?

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. rakazo 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.

Who wins the memos vs rakazo score?

memos scores 99.1 and rakazo scores 88.6. This page calls that a clear lead for memos.

Related comparisons