I PUT A PYTHON VOICE AGENT IN A CLOUDFLARE CONTAINER. TURN-TAKING WAS THE WHOLE FIGHT.
A production phone agent on Pipecat in a Cloudflare Container. A per-call turn-detection model, scale-to-zero, and every millisecond of latency I fought for.
// POSTS TAGGED: [CLOUDFLARE]
7 posts
BROWSER RENDERING IS THE BEST THING CLOUDFLARE SHIPPED IN 2025
I was evaluating Firecrawl. Then I found Cloudflare's Browser Rendering API. The /markdown endpoint does what I needed. One REST call. URL in, clean markdown out. Architecture, Firecrawl comparison, and the gaps I've hit in production.
MY AGENT ALREADY CONVERTS HTML TO MARKDOWN. CLOUDFLARE JUST MADE IT FREE.
Cloudflare shipped Markdown for Agents — any site on their network can now serve markdown instead of HTML through content negotiation. One header. No origin changes. Here's how it fits into an agent pipeline.
10 MILLION SUBREQUESTS. THE CAP THAT CRIPPLED WORKFLOWS IS GONE.
Cloudflare blew up the Worker subrequest limit — from 1,000 to a configurable max of 10 million. What changed, why it matters for Workflows, Durable Objects, and batch jobs.
MOLTWORKER USES A CONTAINER. I USED DURABLE OBJECTS.
Comparing Cloudflare's Moltworker container-based agent to a native Durable Objects approach — cold starts, state management, browser automation, and cost.
REMOTION ON CLOUDFLARE. NO LAMBDA. NO S3.
How I got Remotion running entirely on Cloudflare — Workers, Containers, R2, Queues — with zero AWS dependencies and zero egress fees.
BROWSER RENDERING API KILLED MY FIRECRAWL BILL
How I replaced an $83/month Firecrawl subscription with Cloudflare's Browser Rendering API for effectively $0 when scraping public technical content.