Skip to content
DevUtils Online

Self-Hosted

bore vs memos

memos leads by 23.0 · decisive

A

bore

76.1

11,615 stars · MIT

B · leads

memos

99.1

64,520 stars · MIT

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

memos has 64,520 GitHub stars to bore's 11,615, a gap of 52,905 (5.55×). Forks are 531 for bore and 4,972 for memos. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 74 versus 100.

Push history: bore was last pushed on 04 February 2026 (286 days ago), and memos was last pushed on 17 November 2026 (0 days ago). Open issues stand at 19 for bore (0.002 per star) and 63 for memos (0.001 per star). Issue-health scores are 96 and 96; activity scores are 36 and 100.

Both bore and memos are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Self-Hosted, both bore (11,615 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: bore is open source, memos is open source.

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

memos finishes ahead at 99.1 against bore at 76.1, a 23.0 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.

bore versus memos metrics
Signal bore memos
GitHub stars 11,615 64,520
Forks 531 4,972
Open issues 19 63
Adoption 84 100
Activity 36 100
Community 74 100
Issue health 96 96
License 96 96
Self-hosting 100 100
Composite 76.1 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, bore or memos?

memos has more GitHub stars: 64,520 versus 11,615 for bore. The gap is 52,905 stars.

Which was updated more recently, bore or memos?

memos was pushed more recently: 17 November 2026 versus 04 February 2026 for bore. That is 286 days apart.

Can I self-host both bore and memos?

Yes. This catalog marks both bore 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, bore or memos?

bore 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. 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 bore vs memos score?

memos scores 99.1 and bore scores 76.1. This page calls that a decisive lead for memos.

Related comparisons