Documents and notes decision

Reeder

A competent developer can reproduce the core Reeder functionality (feed parsing, unified timeline, tagging and cross-device state) in about a week and run it with modest hosting; the main proprietary pieces (iCloud sync and hosted shared feeds) are not blockers for a useful replacement.

Visit website
You pay

$1/mo

$12/yr

Not verified against a pricing page.

You’d pay instead

$50one-off30 h to build

$10/mo6 h/mo upkeep

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

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. All Reeder alternatives, with the arithmetic →

What a replacement has to do

  • Aggregate feeds and social/video sources, parse items into a unified timeline, store subscriptions/tags/timeline position, present filters and playback/open actions, sync timeline position across devices (via a server or cloud sync).

What it still won’t have

  • iCloud-based sync (native Apple iCloud integration and its privacy model)
  • Hosted public shared feeds on reederapp.net
  • Tight native UI polish and OS-level integrations present in the iOS/macOS app

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 15 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 minimal unified feed reader web app using TypeScript/React for the frontend, Node.js/Express for the backend, and Postgres for storage. In scope: (1) background worker that fetches and parses RSS/JSON feeds and extracts media links, (2) APIs to manage subscriptions, tags, saved items and timeline position, (3) a React timeline UI with filters (by keyword, media type, feed), tagging, saving/bookmarking and open/play actions, (4) a simple sync layer: user auth (email+password) and per-user timeline position persisted on the server, and (5) tests (unit for parsers and API, integration for sync). Out of scope: native iCloud integration, hosting public feeds on reederapp.net, deep macOS/iOS native UI. Include error handling for feed fetch failures, malformed feeds, rate limits and duplicate items; include automated tests and a Dockerfile for local deployment.
How we checked7 sources · 2/3 runs agreed · evidence score 86

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 7 cited sources+3
  • Evidence score86

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

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! Price not confirmed on the page - this pricing page renders its price in the browser! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded