Documents and notes decision
Readwise
A capable developer can recreate the core highlight import, storage, spaced-repetition daily email, and basic sync/export in ~30 hours and maintain it cheaply, but reproducing Readwise's full connector coverage, polished Reader app, and SaaS reliability is larger and would likely require ongoing investment.
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. All Readwise alternatives, with the arithmetic →
What a replacement has to do
- Import highlights from reading sources, store and index highlights, surface highlights via a spaced-repetition daily email and simple app UI, and sync/export highlights to note-taking tools.
What it still won’t have
- Polished mobile/desktop Reader app and ongoing feature work
- All built-in third-party connector coverage and frictionless OAuth flows
- Polish, analytics, and reliability of a production SaaS (scaling, retries, monitoring)
- Customer support and account management 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 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 'Readwise-lite' service using Node.js + Express, Postgres, and React for a minimal web UI. Implement: (1) OAuth/import connectors for Kindle and Instapaper (or file-import fallback) that store highlights in Postgres; (2) a highlights schema with tags, notes, and full-text indexing (Postgres tsvector); (3) a spaced-repetition scheduler that selects N highlights per user/day and records review responses; (4) a daily email worker (SendGrid/Mailgun) that renders the scheduled review set and queues sends; (5) HTTP endpoints and a small React app for search, tagging, and manual export; (6) export jobs to push highlights to Notion/Obsidian (API/file). Out of scope: building a native mobile Reader app, writing many third-party connectors, and training ML models. Include error handling, retries for network jobs, migrations, tests for scheduler and import flows, and Docker-based deployment scripts.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 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 · 3
Every page the run actually retrieved.
- official productReadwise (home)
- official pricingReadwise - Pricing
- open sourcezmister2016/MrDoc
Integrity checks
What held up, and what did not.
