One hour every morning. Thirty tabs. That was the price of staying current on Claude and the wider Anthropic ecosystem. Reddit, X lists, GitHub releases, Hacker News, half a dozen Substacks, the Anthropic blog itself. Something always slipped through.
So I stopped reading and started building.
claude.mazzotta.dev is a one-page, AI-curated daily briefing. Fifteen sources collapse into about five minutes of reading. New issue every morning at 06:00 CET. Free. No signup. RSS works too.
This post is the long-form version of why it exists, how it is built, and what I learned shipping a Claude-on-Claude pipeline as a free product.
The problem with how I was working
The Anthropic ecosystem moves fast. In any given week:
- Anthropic ships a model upgrade or new API surface
- The Claude Agent SDK gets a new release
- Someone reverse-engineers a clever pattern on r/ClaudeAI
- A new MCP server hits the directory
- A safety paper drops that changes how you should evaluate your prompts
- A trending repo on GitHub turns into a tool you actually need
If you build with Claude, missing any of those costs time. If you do not check daily, you fall behind in a week.
My old workflow was thirty tabs and decision fatigue. Should I read the safety paper or the engineering blog post? Should I open the trending repo or the discussion thread? Most days I gave up halfway and lost an hour to context-switching with no real output.
Newsletters were the obvious answer. I tried subscribing to four. They were either too broad (everything AI, no signal) or too narrow (only Anthropic press releases). None ranked items. None summarised consistently. None worked offline as a URL I could bookmark and trust.
What Claude Daily actually does
One page. Six sections. Always at the same URL.
- Releases. What Anthropic shipped today plus any first-party SDK updates.
- Tools. New MCP servers, libraries, debugging packages worth opening.
- Tips. Practitioner patterns surfacing on r/ClaudeAI, Hacker News, X.
- Reading. Long-form posts, safety research, engineering essays.
- Discussions. What the community is arguing about right now.
- Always at hand. Permanent reference links: Anthropic docs, Claude Code CLI, MCP spec, model lineup.
Above the fold: a single editor's note, written daily, that names the one thing you should not miss. A TL;DR sidebar for the meeting-in-five-minutes case.
That is the entire product. No personalisation. No login. No "subscribe to read more".
The pipeline is itself a Claude application
This is the part that makes it work as a free product. Reading every source manually is unaffordable. Reading every source with AI is not.
SOURCES (15 feeds, polled every 30 min)
↓
INGESTION /api/cron/ingest
→ dedup by canonical-url + normalised-title sha256
→ INSERT raw_items
↓
ENRICHMENT /api/cron/enrich (hourly)
→ Haiku 4.5: classify (category, importance, tags)
→ Sonnet 4.6: summarise EN + DE if importance ≥ 5
→ INSERT enriched_items
↓
CURATION /api/cron/curate (04:30 UTC daily)
→ Sonnet 4.6: pick top items per section
→ Opus 4.7: write headline + editor note + TL;DR
→ UPSERT daily_briefings + revalidatePath
↓
RENDER /, /[date], /archive, /api/og/*, /feed.xml
↓
DIGEST /api/cron/digest (05:30 UTC, Resend)
WEEKLY /api/cron/weekly (Sun 07:00 UTC, Resend)
The model selection is the boring win. Haiku is fast and cheap so it handles the high-volume classification step. Sonnet is the workhorse: every important item gets a bilingual EN + DE summary, no exceptions. Opus only runs once per day for the editorial layer where quality compounds.
Cost shape, roughly:
| Step | Model | Items per day | Notes |
|---|---|---|---|
| Classify | Haiku 4.5 | 400 to 800 | Most items never get summarised |
| Summarise | Sonnet 4.6 | 60 to 100 | Only importance ≥ 5 |
| Curate | Opus 4.7 | 6 to 8 sections | Once per day |
| Editor note | Opus 4.7 | 1 paragraph | Once per day |
Across a typical day this lands well under the cost of a single cup of coffee. The free product is genuinely free.
The stack
Next.js 15 App Router. TypeScript strict. Tailwind v4 with shadcn primitives. Postgres on Supabase with Drizzle for the ORM. The Anthropic SDK directly, no abstraction layer. Resend for the digest. Vercel for hosting and cron. Plausible for privacy-first analytics.
Two design rules:
- One database, one process. No queues, no Redis, no scheduler. Vercel Cron is the only scheduler. Postgres is the only state.
- No build-time content. Every briefing is a row in
daily_briefings. The home page is server-rendered from that row with on-demand revalidation. Adding a new day is anUPSERT, not a deploy.
Both rules collapse the operational footprint to almost zero. I deploy it like a marketing site and it runs like a daily product.
Why a website instead of a newsletter
Newsletters demand three things from the reader:
- An email address
- A confirmation click
- Inbox real-estate
I just want to open a URL, read, close it. The product is the URL. The newsletter is a courtesy for inbox-natives. RSS is for the rest.
This also means the briefing is fully indexable. Google sees it. Claude.ai's web crawler sees it. Perplexity sees it. A newsletter behind a signup wall is invisible to all three.
What it costs to run
Hosting is free on Vercel's hobby tier. Database is free on Supabase's hobby tier. Resend's free tier covers thousands of digest sends. Anthropic API calls are the only real cost and they sit under coffee money per day.
The whole thing is so cheap that I genuinely worry less about cost than about people not finding it. Distribution is now the harder problem.
What I learned
A few things I would underline for anyone building a similar AI-on-AI pipeline.
Score everything. Importance scoring before summarising is the cost lever. Without it, you summarise noise.
Localise during enrichment, not at render. EN and DE summaries are written once per item, stored, served. Translating at render time would be slow, expensive, and inconsistent.
Use Opus sparingly. One Opus call per day is the right number for an editorial product. Anything that feels like Opus-tier judgement should be batched into that one call.
Cron is not a queue. Vercel Cron fires once. If you need retries you build them. I lean on idempotent upserts plus an admin route that lets me re-run any stage by date.
The free product is a funnel, not a charity. Claude Daily exists partly because I want to help people, mostly because it puts my name in front of the exact people who hire Wealthior Labs. The economics work because the funnel works.
Try it
If you build with Claude, give it five minutes tomorrow morning. If it does not save you an hour, close the tab. No subscribe button. No follow-up email. That is the deal.
If you want me to build something like this for your team or your product, Wealthior Labs ships fixed-price AI engagements. The pipeline above took two Sprint packages plus retainer time. The cost model lives in the AI Engineer page.
Either way: stop reading r/ClaudeAI at 6am. Read it at 06:00 CET, condensed.