Buku vs Cubox (Hoarder)
| Tagline | Powerful command-line bookmark manager with a personal mini-web | AI-powered self-hosted bookmarking and read-it-later with automatic tagging |
| Category | Feeds & Read-Later | Feeds & Read-Later |
| Replaces | Pocket, Raindrop.io, Instapaper | Raindrop.io, Pocket, Instapaper |
| GitHub stars | 7.2k | 28k |
| Language | Python | TypeScript |
| License | GPL-3.0 | AGPL-3.0 |
| Self-host difficulty | 2/5 Easy | 2/5 Easy |
| Deploy options | Docker Manual | Docker Compose One-Click |
| Managed hosting | ||
| Last updated | 29 days ago | 6 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.
Buku
- Primarily a CLI tool; web UI (Bukuserver) is functional but not polished
- No article archiving, reader mode, or offline content snapshots
- No native mobile apps; sync between devices is manual
- No RSS subscription or feed reading functionality
Cubox (Hoarder)
- AI tagging requires Ollama or an OpenAI-compatible API; adds resource overhead
- RSS reader features are basic compared to dedicated feed readers like Miniflux
- Relatively young project; some rough edges in mobile app stability
Bottom line
Both are a similar lift to self-host; choose Cubox (Hoarder) for the larger community and ecosystem. Cubox (Hoarder) has seen more recent development. Open each guide below for deploy steps and the full feature gap.
Cubox (Hoarder)
AI-powered self-hosted bookmarking and read-it-later with automatic tagging