Cloudflare Rebuilds Browser Run on Containers for 4x Better Performance and Scale
Key Takeaways
- ▸Browser Run now supports 4x higher concurrent browser limits (120 vs. 30) and 60 spawns per minute with 50%+ faster response times
- ▸Migration to Cloudflare Containers required zero changes from existing customers; improvements deployed immediately with no redeployments needed
- ▸Browser Run is increasingly critical infrastructure for AI agents, enabling programmatic web interaction at scale on a global network
Summary
Cloudflare has announced a major upgrade to its Browser Run service, migrating from shared infrastructure with Browser Isolation to dedicated Cloudflare Containers. The move enables significant performance improvements and higher usage limits without requiring any changes from existing customers.
The improvements are substantial: Browser Run now supports spinning up 60 browsers per minute, running up to 120 concurrent browsers (4x the previous limit), and Quick Action response times have dropped by more than 50%. All improvements are live immediately, and customers don't need to redeploy workers or change any code.
Browser Run is used for web application end-to-end testing, security investigations, PDF rendering, and increasingly as critical infrastructure for AI agents to interact with the web. The migration to Containers allows Cloudflare to optimize for Browser Run's unique usage pattern of short, spiky bursts rather than the long, steady sessions typical of Browser Isolation users.
The technical migration involved a phased rollout starting with Quick Actions endpoints and progressing through different customer tiers. This approach, combined with Browser Run serving as "Customer Zero" for Cloudflare's Containers platform, provided valuable feedback that improved the product for external customers.
