Cubox (Hoarder) vs Readeck
| Tagline | AI-powered self-hosted bookmarking and read-it-later with automatic tagging | Lightweight self-hosted read-it-later and bookmarks app |
| Category | Feeds & Read-Later | Feeds & Read-Later |
| Replaces | Raindrop.io, Pocket, Instapaper | Pocket, Instapaper, Raindrop.io |
| GitHub stars | 28k | 0 |
| Language | TypeScript | Go |
| License | AGPL-3.0 | AGPL-3.0 |
| Self-host difficulty | 2/5 Easy | 1/5 Effortless |
| Deploy options | Docker Compose One-Click | Docker Manual |
| Managed hosting | ||
| Last updated | 8 days ago | 2 months 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.
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
Readeck
- Hosted on Codeberg, not GitHub, so star count and community tooling differ
- No mobile native app — relies on progressive web app
- RSS feed aggregation is not a built-in feature; it is purely read-later focused
Bottom line
Choose Readeck if you want the lower-effort setup; 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