A · leads
memos
97.0
64,520 stars · MIT
Self-Hosted
memos leads by 5.8 · narrow
A · leads
97.0
64,520 stars · MIT
B
91.2
96,832 stars · license n/a
memos versus Stirling-PDF 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; Stirling-PDF is written mainly in TypeScript. The composite score is 97.0 for memos and 91.2 for Stirling-PDF.
Stirling-PDF has 96,832 GitHub stars to memos's 64,520, a gap of 32,312 (1.50×). Forks are 4,972 for memos and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 93 versus 100.
Push history: memos was last pushed on 17 November 2026 (0 days ago), and Stirling-PDF was last pushed on 17 November 2026 (0 days ago). Open issues stand at 63 for memos (0.001 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 96 and 96; 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. Stirling-PDF is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for memos and 30 for Stirling-PDF. This is a procurement signal, not legal advice.
In Self-Hosted, both memos (64,520 stars) and Stirling-PDF (96,832 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, Stirling-PDF is unpriced in this catalog.
The lead is split. memos is furthest ahead on license flexibility (96 to 30), while Stirling-PDF is furthest ahead on fork community (100 to 93). Choose the dimension a rollout cannot compromise on.
memos finishes ahead at 97.0 against Stirling-PDF at 91.2, a 5.8 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 | Stirling-PDF |
|---|---|---|
| GitHub stars | 64,520 | 96,832 |
| Forks | 4,972 | 9,373 |
| Open issues | 63 | 448 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 93 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 97.0 | 91.2 |
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.
#1 PDF Application on GitHub that lets you edit PDFs on any device anywhere
Stirling-PDF has more GitHub stars: 96,832 versus 64,520 for memos. The gap is 32,312 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both memos and Stirling-PDF 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. Stirling-PDF is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
memos scores 97.0 and Stirling-PDF scores 91.2. This page calls that a narrow lead for memos.