Documents and notes decision
Readwise Reader
A minimal Readwise-like workflow (ingest highlights, search/tag, daily spaced-review email, and basic exports) is realistic for a competent developer to build and maintain; reproducing the full product (Reader app polish, many maintained connectors, and brand/scale) is not practical for a one-person effort.
Visit website↗$5.59/mo
$67/yr
Read off the official pricing page.
$50one-off30 h to build
$60/mo6 h/mo upkeep
On cash alone, building overtakes the subscription at 12 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 Readwise Reader alternatives, with the arithmetic →
What a replacement has to do
- Ingest highlights from reader sources, store and index them, surface a scheduled daily review email with spaced-repetition selection, allow search/tag/annotation, and export/sync highlights to other apps.
What it still won’t have
- Polish and UX of the official Reader app (mobile/web)
- Official native integrations and maintained connectors to many reading platforms
- Brand reputation and userbase-driven trust/support
- Early access to Readwise feature roadmap and locked-in pricing
What remains hard
- Brand trust
Readwise helps thousands of readers get the most out of their digital highlights.
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 highlights manager using Node.js (Express), Postgres, and a small React UI. In scope: (1) an import endpoint that accepts uploaded Kindle/Instapaper highlight exports and a simple OAuth-based connector stub; (2) store highlights and metadata in Postgres and add full-text search (Postgres tsvector); (3) a background worker (Bull/Redis) that picks highlights per a simple spaced-repetition schedule and sends a daily email via SendGrid; (4) a React web UI to browse, search, tag, and annotate highlights; (5) an export worker that writes to Notion via its API. Out of scope: mobile apps, large-scale connector coverage, proprietary Reader UI polish, and synchronization edge-cases. Include error handling for failed imports, retries for email and export jobs, authentication (magic links or simple account/password), and unit/integration tests for import, scheduling, email sending, and export flows.
How we checked
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
- 3/3 assessment runs agreed+4
- Evidence score67
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.
- official productReadwise
- official pricingPricing | Readwise
- open sourceomnivore-app/omnivore
- open sourcelinkwarden/linkwarden
Integrity checks
What held up, and what did not.
