BentoPDF vs Memos
| Tagline | Privacy-first client-side PDF toolkit — edit, merge, and process in the browser | Lightweight, self-hosted note-taking and memo hub |
| Category | Notes & Knowledge Base | Notes & Knowledge Base |
| Replaces | Notion | Evernote, Notion |
| GitHub stars | 14k | 61k |
| Language | Nodejs | Go |
| License | AGPL-3.0 | MIT |
| Self-host difficulty | 2/5 Easy | 2/5 Easy |
| Deploy options | Docker Manual | Docker Manual |
| Managed hosting | ||
| Last updated | yesterday | 3 days ago |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
BentoPDF
- Client-side WASM processing is slower than server-side tools for very large PDFs.
- No OCR or text extraction capabilities.
- No user accounts, history, or saved workflows between sessions.
- Feature set is narrower than server-side tools like Stirling-PDF for batch or automated use.
Memos
- Designed for short notes/memos, not long structured documents or wikis.
- No nested page hierarchy, databases, or board views.
- No real-time collaboration.
- Limited rich formatting compared to block editors.
Bottom line
Both are a similar lift to self-host; choose Memos for the larger community and ecosystem. BentoPDF has seen more recent development. Open each guide below for deploy steps and the full feature gap.
BentoPDF
Privacy-first client-side PDF toolkit — edit, merge, and process in the browser