Cubox (Hoarder) vs Fusion
| Tagline | AI-powered self-hosted bookmarking and read-it-later with automatic tagging | Lightweight self-hosted RSS aggregator and reader written in Go |
| Category | Feeds & Read-Later | Feeds & Read-Later |
| Replaces | Raindrop.io, Pocket, Instapaper | Feedly, Pocket |
| GitHub stars | 28k | 2.1k |
| Language | TypeScript | Go |
| License | AGPL-3.0 | MIT |
| Self-host difficulty | 2/5 Easy | 2/5 Easy |
| Deploy options | Docker Compose One-Click | Docker Manual |
| Managed hosting | ||
| Last updated | 6 days ago | 15 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
Fusion
- Very minimal feature set; lacks tagging, folders, and advanced filtering found in Feedly
- No read-later or article archiving functionality
- No third-party client API or mobile app support
- Fewer integrations and plugin ecosystem compared to mature readers
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