Discofork
Repository brief

usememos/memos

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T11:57:44.319Z
3mo ago

usememos/memos

usememos/memos is an actively maintained, open-source self-hosted note-taking app focused on quick capture. It is large and popular, with 58,366 stars and 4,226 forks, and it was updated and pushed on 2026-03-30. The repo is MIT-licensed, written in Go, and includes web, server, store, proto, plugin, and docs components.

GitHub
Loading tags...
Stars58,366
Forks4,226
Default branchmain
Last pushed2026-03-30T11:56:44Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Adopt this fork if you want Memos plus deeper integration and operator tooling, and you are willing to manage divergence from upstream. Avoid it if you want the safest, most up-to-date upstream baseline with minimal maintenance burden.

Choose this fork only if you specifically want the Docker reproduction path or its downstream UI/localization changes. For most adopters, upstream is the safer choice because this fork is stale, heavily diverged, and likely missing recent fixes and security-related behavior.

Choose this fork if the added media support and UI polish matter more than staying close to upstream. Avoid it if you want the safest path for integrations, plugins, or low-maintenance upgrades from upstream Memos.

Choose this fork only if its custom search/filter behavior or tag-based release workflow is the reason you need it. For general adoption, upstream is the safer default because this fork is stale and materially behind on recent fixes and API behavior.

Choose this fork only if you specifically want its older custom API/workflow direction and are prepared to maintain it yourself. If you want a current, low-risk self-hosted notes app, upstream is the better fit.

Choose this fork if the added timestamp and filtering behavior matters more than staying fully current with upstream. If you want the newest upstream fixes and a larger support ecosystem, upstream is the safer default.

Choose this fork if shared-note rendering, signed image exports, and custom attachment/share behavior matter more than staying current with upstream. If you want the broadest ecosystem compatibility and the newest upstream fixes, upstream is the safer default.

Choose this fork only if you need its specific downstream changes and are prepared to maintain a large divergence. If you want the most current, low-friction Memos experience, upstream is the safer default.

Choose this fork only if its memo display and API customizations matter more than staying current with upstream. For most adopters, the 200-commit lag and large divergence make upstream the safer default.

Prefer upstream if you want a current, lower-maintenance self-hosted notes app. Prefer this fork only if you specifically need its custom memo-hub direction and are willing to own a stale, high-divergence codebase.