Fixing the Code Doesn't Evict a Broken Page From the Edge Cache
I shipped a fix and the broken page kept serving. The problem was not the code but the edge cache, which had stored a broken HTML response because the store decision looked only at the status code. Here is the integrity guard I now run before every cache write, and the thresholds I had to tune in production.
The Connection That Dies Mid-Thought Is Being Killed by Your Relay, Not the Upstream
Put a proxy or Worker in front of Claude Code and long thinking pauses start dying. The cause is neither the model nor the upstream — it is your relay holding the byte stream. Six relay behaviors compared side by side, plus how to verify yours before it ships.
Claude × Stripe Meter Events — Building a Usage-Based SaaS
A production-ready architecture and full implementation for billing Claude API token consumption through Stripe Meter Events — covering idempotency, usage caps, and a hybrid base + overage pricing model.
Reading the Claude apps gateway Announcement, I Rebuilt My Indie-Scale Control Plane
The self-hosted Claude apps gateway is a control-plane/data-plane separation you can scale down. Per-app cost attribution, model allowlists, and fail-closed spend caps, implemented as a small Cloudflare Workers proxy.
Putting Cloudflare AI Gateway in Front of Claude Made the Numbers I Needed Disappear — Field Notes on Instrumentation
After putting Cloudflare AI Gateway in front of Claude API, here is where I actually got stung — cost attribution, semantic-cache false hits, fallback quietly lowering quality, and budgets that don't really stop anything — with the code I used to fix each.
It Says '500' in the Browser but curl Returns 200 — When a Next.js Error Boundary Misreads a ChunkLoadError
A production Next.js article page shows '500 Internal Server Error' in the browser, yet curl returns 200. The culprit was not the server but a ChunkLoadError surfacing through error.tsx. Here is the diagnosis and a fix with built-in auto-reload.
The Morning I Hit Cloudflare Workers' 62 MiB Limit, and the Content Split Architecture I Rebuilt for 5,000 Articles
One morning, an indie developer running 4 AI tech blogs on Cloudflare Workers + Next.js woke up to a deployment that had stopped because articles.json grew large enough to push the Worker bundle past the 62 MiB limit. This is the concrete implementation walkthrough of splitting metadata from HTML, with the build-time and bundle-size numbers observed across the first month.
Building Stateful AI Agents with Cloudflare Durable Objects and Claude API — Session Management, Context Persistence, and Scale-Out Design
A complete production guide for building stateful AI agents using Cloudflare Durable Objects and Claude API. Covers session management, context persistence, compaction strategies, and scale-out design with fully working code examples.
Building a Subscription SaaS with Claude API and Stripe — A Complete 2026 Implementation Guide
An end-to-end implementation guide for shipping a subscription SaaS built on Claude API, Stripe, and Cloudflare Workers — covering checkout, webhooks, KV-backed access control, usage limits, and the production edge cases that always bite.
Running Next.js on Cloudflare Workers in Production with Claude Code — Every Build Crisis, Cache Bug, and Automation Pattern We Solved
Running Next.js on Cloudflare Workers is not the same as Vercel. The 62 MiB bundle limit, ASSETS binding quirks, and edge cache personalization conflicts are real production hazards. Here's how Claude Code helped us solve each one.
Building a Stripe Subscription SaaS with Claude Code: Webhooks, Auth, and Production Pitfalls
Shipping a Stripe subscription SaaS with Claude Code on Cloudflare Workers: Webhook verification, KV + Cookie auth, and a cookie regex that failed silently.
Claude Code × SvelteKit Full-Stack Development Guide: From Zero to Production
A complete guide to full-stack development with Claude Code and SvelteKit. Covers Svelte 5 Runes, Drizzle ORM, Auth.js, and Cloudflare Workers deployment through practical, production-ready workflows.