Skip to content
DevUtils Online

Self-Hosted

feishin vs memos

memos leads by 15.5 · decisive

A

feishin

83.6

10,433 stars · GPL-3.0

B · leads

memos

99.1

64,520 stars · MIT

feishin versus memos is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. feishin is written mainly in TypeScript; memos is written mainly in Go. The composite score is 83.6 for feishin and 99.1 for memos.

memos has 64,520 GitHub stars to feishin's 10,433, a gap of 54,087 (6.18×). Forks are 609 for feishin and 4,972 for memos. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 75 versus 100.

Push history: feishin was last pushed on 16 November 2026 (1 day ago), and memos was last pushed on 17 November 2026 (0 days ago). Open issues stand at 329 for feishin (0.032 per star) and 63 for memos (0.001 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.

feishin is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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. License scores in this pair are 64 for feishin and 96 for memos. This is a procurement signal, not legal advice.

In Self-Hosted, both feishin (10,433 stars) and memos (64,520 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: feishin is open source, memos is open source.

memos is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 32 points (64 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).

memos finishes ahead at 99.1 against feishin at 83.6, a 15.5 point decisive 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.

feishin versus memos metrics
Signal feishin memos
GitHub stars 10,433 64,520
Forks 609 4,972
Open issues 329 63
Adoption 84 100
Activity 100 100
Community 75 100
Issue health 70 96
License 64 96
Self-hosting 100 100
Composite 83.6 99.1

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, feishin or memos?

memos has more GitHub stars: 64,520 versus 10,433 for feishin. The gap is 54,087 stars.

Which was updated more recently, feishin or memos?

memos was pushed more recently: 17 November 2026 versus 16 November 2026 for feishin. That is 1 days apart.

Can I self-host both feishin and memos?

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

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

feishin is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the feishin vs memos score?

memos scores 99.1 and feishin scores 83.6. This page calls that a decisive lead for memos.

Related comparisons