A · leads
memos
99.0
64,520 stars · MIT
Self-Hosted
memos leads by 6.4 · narrow
A · leads
99.0
64,520 stars · MIT
B
92.6
65,557 stars · AGPL-3.0
memos versus NocoDB 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; NocoDB is written mainly in TypeScript. The composite score is 99.0 for memos and 92.6 for NocoDB.
NocoDB has 65,557 GitHub stars to memos's 64,520, a gap of 1,037 (1.02×). Forks are 4,972 for memos and 5,142 for NocoDB. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 100.
Push history: memos was last pushed on 17 November 2026 (0 days ago), and NocoDB was last pushed on 17 November 2026 (0 days ago). Open issues stand at 63 for memos (0.001 per star) and 526 for NocoDB (0.008 per star). Issue-health scores are 96 and 84; 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. NocoDB 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 NocoDB. This is a procurement signal, not legal advice.
In Self-Hosted, both memos (64,520 stars) and NocoDB (65,557 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, NocoDB is freemium.
The lead is split. memos is furthest ahead on license flexibility (96 to 52), while NocoDB is furthest ahead on fork community (100 to 100). Choose the dimension a rollout cannot compromise on.
memos finishes ahead at 99.0 against NocoDB at 92.6, a 6.4 point narrow 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 | NocoDB |
|---|---|---|
| GitHub stars | 64,520 | 65,557 |
| Forks | 4,972 | 5,142 |
| Open issues | 63 | 526 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 99.0 | 92.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.
NocoDB turns a relational database into a spreadsheet-style workspace with views, forms, and an API. It is used when the system of record should stay in Postgres or MySQL.
NocoDB has more GitHub stars: 65,557 versus 64,520 for memos. The gap is 1,037 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both memos and NocoDB 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. NocoDB 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.0 and NocoDB scores 92.6. This page calls that a narrow lead for memos.