Documents and notes decision
BazQux Reader
A competent developer can build a useful self-hosted RSS reader (parsing, full-text extraction, UI) over several weeks using existing libraries, but reproducing the complete paid product (hosted fetch infrastructure, native apps, image proxy at scale, social-media scraping and support) is larger work — so consider building a narrow replacement and keep paying for the full hosted experience while you iterate.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
Code BazQux Reader publishes itself
Not a way out of the subscription — these are the vendor’s own repositories. Worth a look for how they build, and for anything you would have to integrate with.
What a replacement has to do
- Poll subscribed feed URLs (and tracked social pages), fetch and parse feed items, convert truncated feeds to full-text, store items and user read/star/tag state, render web UI with list/mosaic/magazine views and search/filters.
What it still won’t have
- Hosted feed-fetching infrastructure that updates paid users only
- Built-in secure image proxy provided by the service
- Native mobile apps (iOS, macOS, Android) and their offline sync
- Customer support from the paid service
- Prebuilt social-media-to-feed parsing for Facebook/Telegram/VK
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 12 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a self-hosted RSS + social-feed reader using: Postgres for storage, a Python/Node background worker for fetch/parse, Go or Node service for an image proxy, and a React web client. In scope: feed discovery and subscription, OPML import/export, periodic background fetcher, RSS/Atom/JSON Feed parsing (reuse an existing library), full-text extraction for truncated entries, storage of items/users/subscriptions/tags/stars/read-state, search and filter endpoints, mixed view UI modes (list/mosaic/magazine/expanded), login (email + optional OAuth), and a cached image proxy to strip tracking. Out of scope: native mobile apps and paid multi-tenant scaling. Include error handling for transient fetch failures, rate-limiting/backoff, unit tests for parsers and DB logic, and end-to-end smoke tests for the core feed-to-UI flow.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score64
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productBazQux Reader — official product page
- open sourceFreshRSS/FreshRSS
- open sourcesamuelclay/NewsBlur
Integrity checks
What held up, and what did not.
