Documents and notes decision
Analog Reader
A technical user can reproduce the core weekly PDF-from-feeds workflow and delivery for themselves, but the full paid product’s polish, broad source compatibility, and managed subscription experience are costly to match.
Visit website↗$15/mo
$180/yr
Read off the official pricing page.
$50one-off30 h to build
$20/mo3 h/mo upkeep
On cash alone, building overtakes the subscription at 2 seats.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Generate a weekly newspaper PDF from user-selected sources and send it by email/Kindle.
What it still won’t have
- Polished, curated design and typography tuning done by the vendor
- Managed payment/subscription handling and churn management
- Reliability, monitoring, and support SLA
- Automatic content-source compatibility work for many newsletter formats
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 single-user weekly newspaper generator using Python (FastAPI) + SQLite + worker cron: 1) implement fetchers that accept newsletter URLs, RSS/X lists, Hacker News links and archive raw HTML; 2) extract and sanitize article body/title/images using readability-lxml or newspaper3k; 3) implement a paged newspaper layout using HTML/CSS and render to PDF with WeasyPrint; 4) schedule a weekly job to assemble top N items into an issue; 5) send the PDF by SMTP/SendGrid and also to a configured Kindle email address; 6) provide a minimal web UI to add/remove sources and preview an issue. Out of scope: multi-user billing, a polished WYSIWYG editor, distributed scaling. Include error handling, retries, logging, and unit tests for extractors and PDF generation.
How we checked
How the score was reached
- Partly verdict base52
- 2 cited sources+1
- Price verified on pricing page+3
- Evidence score56
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 · 2
Every page the run actually retrieved.
- official productAnalog Reader
- official pricingAnalog Reader Pricing
Integrity checks
What held up, and what did not.
