Documents and notes decision

Feedbin

A competent developer can recreate the core RSS fetch + full-text + reading UI functionality, but reproducing Feedbin’s complete hosted features (newsletter email ingest, app sync, push reliability and polish) is significant extra work.

Visit website
Subscription$7/month ✓ verified
Initial build80 hours
Monthly upkeep6 hours + $0
Evidence2/3 runs agree

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 Feedbin 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

  • Continuously fetch RSS/YouTube/newsletter sources, extract full article text, store articles, present chronological reading UI with search and saved actions.

What it still won’t have

  • Hosted reliability, uptime and backups (you must host/monitor yourself)
  • Built-in email-to-RSS newsletter ingest (requires inbound email handling)
  • Seamless sync with third-party native apps (Reeder/NetNewsWire) unless you implement and maintain API compatibility
  • Push notification infrastructure and polished mobile behavior
  • Ongoing feature improvements and content-updated diffs

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 2 seats.

Paid seatsseats

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

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

Not run yet
Build a self-hosted minimal Feedbin clone using: Node.js (Express) backend, Postgres, Redis for job queue, and a React web UI. Implement: user signup/login, background job workers that poll RSS/Atom and YouTube feeds, fetch article HTML and run full-text extraction, store articles and feed subscriptions in Postgres with deduplication and updated-article diffing, a chronological reading UI with mark-read/star and saved searches, and a simple actions system (mark-as-read, star, webhook). Out of scope: inbound email-to-RSS processing and native mobile apps. Include input validation, retry/backoff for fetches, basic metrics logging, tests for fetcher, extractor and API endpoints, and Docker Compose for local deployment.
How we checked4 sources · 2/3 runs agreed · evidence score 63

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 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 · 4

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded