Cubox (Hoarder) vs Wallabag
| Tagline | AI-powered self-hosted bookmarking and read-it-later with automatic tagging | Self-hosted read-it-later application to save web articles offline |
| Category | Feeds & Read-Later | Feeds & Read-Later |
| Replaces | Raindrop.io, Pocket, Instapaper | Pocket, Instapaper, Raindrop.io |
| GitHub stars | 28k | 13k |
| Language | TypeScript | PHP |
| License | AGPL-3.0 | MIT |
| Self-host difficulty | 2/5 Easy | 2/5 Easy |
| Deploy options | Docker Compose One-Click | Docker Docker Compose Manual |
| Managed hosting | ||
| Last updated | 8 days ago | today |
| 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
Wallabag
- Article fetching can fail on JavaScript-heavy pages that require a headless browser
- The mobile apps lag slightly behind native apps in polish and offline sync speed
- No built-in social or sharing features
Bottom line
Both are a similar lift to self-host; choose Cubox (Hoarder) for the larger community and ecosystem. Wallabag 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