Documents and notes decision
Instapaper Premium
A single developer can build a usable personal read-it-later service (save, fetch, render, sync) in a few weeks, but reproducing Instapaper's cross-platform polish, scale, and apps is more work and likely not worth rebuilding for a paying user.
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
- Save a webpage (bookmarklet/extension) -> fetch & sanitize article HTML -> store article and metadata in a database -> render a clean, readable view in a web/mobile client -> sync reading position across devices
What it still won’t have
- Polished native mobile apps and app-store distribution
- Long-running cross-device sync at scale (large-scale conflict resolution, millions of devices)
- Brand-recognition and existing user base
- Enterprise features (team accounts, advanced analytics, integrations)
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 2 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 minimal read-it-later web service using Next.js (React) + Node + Postgres + Fly.io (or Heroku) that implements: 1) a browser bookmarklet and simple Chrome extension that POSTs the current page URL and title to your API; 2) a server endpoint that fetches the URL, extracts the article body using Mozilla Readability (or readability-js), downloads/relays inline images to object storage, and stores article HTML and metadata in Postgres; 3) user auth (email/password) and a per-user articles list with pagination and search; 4) a responsive reader page that sanitizes and renders stored article HTML and records reading position via an API; 5) background worker to fetch new articles and prune old ones. Out of scope: native iOS/Android apps, paid subscription billing, OCR or TTS. Include error handling for failed fetches, duplicate URLs, and auth failures, and provide unit tests for server endpoints and integration tests for the extraction pipeline.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- Evidence score60
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 productInstapaper homepage
- open sourceomnivore-app/omnivore
- open sourcewallabag/wallabag
Integrity checks
What held up, and what did not.
