Should you build your own Readwise?
Import highlights from user-exported files, review them with spaced repetition, and export notes
The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Readwise, import highlights from user-exported files, review them with spaced repetition, and export notes. The hard boundary is broad source integrations, sync, daily review polish, and knowledge-tool exports, plus capture polish, sync, and content partnerships.
ENOriginal research content in English. Original prompt preserved in English.
Build a personal replacement for Readwise in an empty repository.
Use Next.js 15, TypeScript, SQLite, Drizzle ORM, Readability.js, and a local background worker; do not offer alternative stacks.
The core loop is: import highlights from user-exported files, tag and search the archive, review highlights with spaced repetition, and export notes in open formats.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Support manual URL save, RSS or Atom subscriptions, OPML import, and a simple bookmarklet.
Fetch politely with a clear user agent, rate limits, conditional requests, and robots-aware behavior.
Extract title, author, date, canonical URL, readable HTML, and selected images.
Provide inbox, unread, archive, favorites, tags, highlights, notes, and full-text search.
Keep the original URL prominent and never attempt to bypass authentication or paywalls.
Export OPML, bookmarks HTML, Markdown, and a complete JSON backup.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out paywall circumvention.
Deliberately leave out licensed publisher content and recommendation networks.
Deliberately leave out native mobile clients and seamless commercial sync.
Finish by running the tests and listing the exact commands used.The prompt opens pre-filled in your agent. Review it before running. · this prompt is generated from the build plan · improve it via PR
What would building your own look like?
Import highlights from user-exported files, tag and search the archive, review highlights with spaced repetition, and export notes in open formats.
What you will need
- Node.js 22
- local disk
- optional browser bookmarklet
- user-supplied RSS feeds
People still pay for Readwise because people pay when capture works everywhere, reading state syncs instantly, and the archive remains clean without constant parser repairs. The recurring cost buys feed quirks, parsing, paywalls, canonical URLs, deduplication, images, search, sync, browser extensions, and publisher changes, not just the visible interface.
xbroad source integrations, sync, daily review polish, and knowledge-tool exports
xpublisher bypasses
xcross-device mobile capture
xhigh-quality recommendation graph
xlicensed full-text feeds
How much does Readwise cost?
- Monthly billing
- $9.99/mo$9.99/mo
- Per year
- $120/yr$120/yr
- On a Brazilian card, with 3.5% IOF
- R$52.20/moR$626/yr
Saved to My list. You will see a notice on this site when the price changes.
You complete the purchase on Readwise’s site. Vibe Radar does not handle payments.
| Plan | Monthly | Annual (per month) | What is included |
|---|---|---|---|
| readwise lite | - | $5.59/user≈ $5.59 | Daily Review, browsing/search and highlight sync; excludes tags, notes, exports and Reader. |
| readwise full | $12.99/user≈ $12.99 | $9.99/user≈ $9.99 | Readwise Lite plus tags, notes, exports and the full Reader app. |
Free tierno free tier; 30-day trial
Billing termsmonthly + annual; the public page exposes only the annual Lite rate
Additional costsstudents and academics can receive 50% off; continuous subscribers may retain a legacy locked price
verified 2026-08-13 · source ↗
Is it cheaper to build or buy Readwise?
Adjust the numbers: hours to build, your hourly rate, running costs and the subscription price.
Over 24 months, subscribing is cheaper.
Starting hours estimated from the analysis (one sitting). Does not price what you give up (support, integrations, security).
Can I rebuild Readwise?
Kinda. The core of Readwise is buildable in a weekend with the prompt on this page, but there are real gaps: broad source integrations, sync, daily review polish, and knowledge-tool exports, publisher bypasses. Read the honest list above before committing.
How much does Readwise cost?
Readwise costs about $9.99/mo (Readwise Full, checked 10/20/2026), which is $120 per year.
What do I lose by replacing Readwise?
Honestly: broad source integrations, sync, daily review polish, and knowledge-tool exports; publisher bypasses; cross-device mobile capture; high-quality recommendation graph; licensed full-text feeds. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Readwise?
Yes: FreshRSS (Mature open-source RSS reader with feeds, filters, and self-hosting support.). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.