Cubox (Hoarder) vs RSS-Bridge
| Tagline | AI-powered self-hosted bookmarking and read-it-later with automatic tagging | Generate RSS and Atom feeds for sites that don't provide them |
| Category | Feeds & Read-Later | Feeds & Read-Later |
| Replaces | Raindrop.io, Pocket, Instapaper | Feedly, Pocket, Instapaper |
| GitHub stars | 28k | 9.1k |
| Language | TypeScript | PHP |
| License | AGPL-3.0 | Unlicense |
| Self-host difficulty | 2/5 Easy | 2/5 Easy |
| Deploy options | Docker Compose One-Click | Docker Manual |
| Managed hosting | ||
| Last updated | 7 days ago | 9 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.
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
RSS-Bridge
- Generates feeds only; no reading interface, saved articles, or annotations
- Bridges break frequently when upstream sites change their HTML structure
- No authentication layer by default — publicly exposed instances are open to abuse
- No mobile apps or browser extensions for capturing pages
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