Cloudflare Unveils Major Browser Run Overhaul: 4x Concurrency, 50% Faster Response
Breaking: Cloudflare dramatically upgrades Browser Run performance and scalability
Cloudflare has announced a complete rebuild of its Browser Run service on top of the company's own Containers infrastructure, delivering immediate performance gains and higher usage limits for developers. The upgrade, now live, requires no changes from users.
Developers can now spin up 60 browsers per minute via the Workers binding and run up to 120 concurrently — quadruple the previous cap. Quick Action response times have dropped more than 50%, the company confirmed.
“These aren’t incremental tweaks; it’s a fundamental architectural shift,” said a Cloudflare engineering lead. “We moved from shared infrastructure to dedicated Containers, and the numbers speak for themselves.”
Background: Why the migration was necessary
Browser Run previously shared infrastructure with Cloudflare’s Browser Isolation (BISO) service. That arrangement, while efficient on paper, created serious bottlenecks. BISO’s larger container images slowed startup times and hindered global distribution, affecting latency and reliability.
“Browser Run’s usage pattern is spiky and short-lived, while BISO users have long, steady sessions,” explained a senior platform engineer. “The clash made scaling and availability challenging.”
Internal development of Durable Object (DO)-enabled Containers, which entered open beta last year, gave the team a chance to migrate. “We’re committed to eating our own dog food,” the engineer added. “It lets us fix pain points before our customers ever see them.”
The migration: A gradual, dual-infrastructure approach
To ensure stability, Cloudflare staged the rollout. A Worker was inserted into request paths to serve some users from the new Container-powered browsers while others remained on the old BISO infrastructure. This dual support allowed side-by-side performance comparisons and bug isolation.
“We started with Quick Actions endpoints, then moved to Workers browser bindings for free accounts, then pay-as-you-go, and finally contract customers,” the engineering lead said. “Each step validated stability before we expanded. The transition required zero action from users — no worker redeployments, no code changes.”
What This Means
For developers, the upgrade translates directly into faster, more reliable automated browser workflows. End-to-end testing, content extraction, PDF rendering, and AI agent interactions — all benefit from lower latency and higher concurrency limits.
“This makes Browser Run the go-to platform for scalable, secure automated browsers,” said a product manager. “We’ve effectively removed the scaling ceiling that held back some of our most demanding use cases.”
Cloudflare also notes that shipping fixes and new features will accelerate because the Container architecture decouples Browser Run from BISO's release cycle. “We can iterate much faster now,” the engineer concluded.
For more details, see the original blog post on Cloudflare's official announcement.
Related Articles
- 6 Key Facts About Docker Hardened Images for ClickHouse in Production
- How to Optimize Cloud Costs in the Age of AI: A Step-by-Step Guide
- The PCPJack Worm: A Credential-Stealing Malware That Exploits Cloud Environments
- Your Guide to Custom MCP Catalogs and Profiles for Enterprise AI Tooling
- How to Optimize Prompts in Amazon Bedrock: A Step-by-Step Guide
- Microsoft Scales Sovereign Private Cloud to Thousands of Nodes with Azure Local
- 10 Steps to Build Your Private AI Image Generator with Docker and Open WebUI
- 8 Key Upgrades in Browser Run's Cloudflare Containers Migration