Documents and notes decision
Inoreader
A single developer can replace the core feed-fetch-and-read experience in about a week, but reproducing Inoreader's monitoring, guaranteed refresh SLAs, Intelligence (AI summaries/reports), integrations and polished multi-platform apps requires much more effort or infrastructure, so keeping the paid service is reasonable if you need those features.
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.
What a replacement has to do
- Continuously fetch subscribed feeds and web pages, extract and store full article content, index/search and present articles in a web UI, mark/save/read-later and tag articles, run simple filter/rule actions on incoming articles.
What it still won’t have
- Monitoring feeds (prebuilt monitoring workflows and large-language intelligence tuned for brand/market monitoring)
- Inoreader Intelligence features (summaries, transcript generation, multi-article reports, model selection)
- Guaranteed refresh SLA / boosted feeds (hourly refresh guarantees and increased refresh intervals)
- Built-in integrations and export features (pre-integrated exports to many services and mobile apps)
- Web feeds / track changes for sites without RSS (prebuilt site-change detection and visual-diff features)
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 3 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 single-user RSS/web-feed reader using FastAPI + Postgres + Redis + worker (RQ/Celery) and a React front-end. In-scope: feed subscription management (OPML import/export), periodic feed and webfeed fetcher, readability-based full-text extraction, article storage with tags/read-state, simple rules engine (match by title/body -> apply tag/send push), search indexing (Postgres full-text or Elasticsearch), read-later and basic mobile-responsive UI, background scheduler, API endpoints for all UI actions, and tests for fetcher, extractor, rule engine, and API. Out of scope: multi-tenant billing, advanced site visual-change diffs, offline mobile apps, and built-in LLM summarization. Include error handling for HTTP failures, rate-limiting, and duplicate entries; provide configuration for refresh intervals and a small deployment script (Docker Compose) and unit + integration tests.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- Evidence score63
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 · 5
Every page the run actually retrieved.
- official productInoreader – Build your own newsfeed
- official pricingPricing | Inoreader
- official docsFeatures | Inoreader
- open sourceFreshRSS/FreshRSS
- open sourceminiflux/v2
Integrity checks
What held up, and what did not.
