10 Breakthroughs in Browser Run’s Cloudflare Container Migration

Browser Run, Cloudflare’s headless browser automation service, has undergone a major transformation. By rebuilding on Cloudflare Containers, it now delivers higher usage limits, faster performance, and better reliability—all without requiring any changes from users. Here are the ten most important things you need to know about this upgrade, from what Browser Run is to the technical migration that made it all possible.

What Exactly Is Browser Run?
4x Higher Concurrent Browser Limits
60 Browsers per Minute via Workers Binding
Quick Action Response Times Drop by Over 50%
Seamless Upgrade – No User Action Required
Faster Bug Fixes and Feature Rollouts
Why We Left the Shared Bunk Bed with Browser Isolation
The Migration Strategy: Dual Support and Gradual Rollout
Real-World Performance Data from the Transition
What’s Next for Browser Run on Cloudflare Containers

1. What Exactly Is Browser Run?

Browser Run is a developer tool that lets you programmatically control headless browsers running on Cloudflare’s global network. These automated browsers can perform end-to-end testing of web apps, safely investigate suspicious URLs, render PDF documents, capture screenshots, and extract content. More recently, Browser Run has become essential for AI agents that need to interact with the web. The service is designed to be the go-to platform for responsibly using automated browsers at massive scale, with security and reliability at its core.

10 Breakthroughs in Browser Run’s Cloudflare Container Migration — Source: blog.cloudflare.com

2. 4x Higher Concurrent Browser Limits

One of the most immediate benefits of the container migration is a dramatic increase in concurrency. Users can now run up to 120 browsers simultaneously—a four‑fold jump from the previous limit of 30. This improvement is critical for large‑scale testing, security analysis, and AI workloads that demand many parallel browser sessions. The boost came from moving off shared infrastructure onto dedicated Cloudflare Containers, which eliminated resource contention and allowed for much higher throughput.

3. 60 Browsers per Minute via Workers Binding

Developers using the Workers binding can now spin up browsers at a rate of 60 per minute. This represents a significant increase in provisioning speed, enabling rapid scaling for bursty workloads. The Workers binding is a key integration point, allowing automation scripts to create browser instances on the fly without worrying about startup delays. Combined with the higher concurrency limit, this makes Browser Run suitable for near‑real‑time applications such as dynamic content scraping and interactive AI agents.

4. Quick Action Response Times Drop by Over 50%

Quick Actions—such as taking a screenshot, extracting text, or generating a PDF—now complete more than 50% faster than before. The migration to Cloudflare Containers reduced the overhead of starting a browser instance and executing simple commands. This speedup is especially valuable for developers who rely on Browser Run for rapid feedback loops in continuous integration pipelines or for live monitoring. The improvement was measured carefully during the gradual rollout, confirming the new architecture’s efficiency.

5. Seamless Upgrade – No User Action Required

Despite the deep architectural changes, the upgrade has been completely transparent to end users. No code changes, no redeployments, and no configuration updates were necessary. The migration happened in stages, with a Worker inserted into the request path to route a portion of traffic to container‑based browsers while the old infrastructure still handled the rest. Once validated, the new system took over fully—users simply experienced faster, more reliable performance without lifting a finger.

6. Faster Bug Fixes and Feature Rollouts

With the old shared infrastructure, releasing fixes or new features was slow because changes often required coordination with the Browser Isolation team. Now that Browser Run runs on its own Cloudflare Containers, the development team can ship updates independently and more frequently. This means users benefit from shorter turnaround times for both bug fixes and new capabilities. The team is already taking advantage of this agility to iterate quickly based on user feedback.

7. Why We Left the Shared Bunk Bed with Browser Isolation

Previously, Browser Run shared infrastructure with Browser Isolation (BISO). While the two products had technical similarities, the arrangement caused several problems. BISO’s larger container images led to slower startup times for Browser Run. More critically, BISO browsers weren’t distributed globally in a way that optimized latency and resiliency for Browser Run’s workload. Additionally, BISO users tend to hold long, steady sessions, whereas Browser Run users create short, spiky bursts—a mismatch that caused scaling bottlenecks and availability delays. Moving to dedicated Containers solved all these issues.

8. The Migration Strategy: Dual Support and Gradual Rollout

The migration was carefully planned to minimize risk. A Worker was placed in the request path to serve a mix of container‑powered browsers and the old BISO‑backed browsers to a subset of users. This dual‑support phase allowed the team to compare performance side by side, isolate bugs, and validate benefits. They first enabled Containers for Quick Actions, then for Workers binding connections from free accounts, followed by pay‑as‑you‑go accounts. Finally, contract customers were migrated. This step‑by‑step approach ensured stability at every stage and gave the team confidence in the new architecture.

9. Real‑World Performance Data from the Transition

Throughout the migration, the team collected detailed metrics. The 50% reduction in Quick Action response times was backed by production data. Concurrent browser limits increased from 30 to 120, and browser spin‑up rates hit 60 per minute. The new system also showed better global distribution—containers are now deployed closer to users, reducing latency. These numbers validated the decision to rebuild on Cloudflare Containers and demonstrated that the platform could handle peak loads without the previous throttling issues.

10. What’s Next for Browser Run on Cloudflare Containers

With the migration complete, the Browser Run team is now focused on leveraging the new platform’s flexibility. Expect even more integrations with Cloudflare’s ecosystem, including deeper Durable Object support for stateful browser interactions and improved AI agent compatibility. The team is also exploring ways to offer custom container images for specialized use cases. By building on their own platform, they can continue to refine performance, security, and scalability—benefits that will eventually flow to external customers as well.

In summary, Browser Run’s move to Cloudflare Containers has unlocked significant improvements in speed, scale, and agility—all delivered seamlessly. For developers, this means more powerful headless browser automation without the headaches of infrastructure management. Whether you’re testing web apps, analyzing security threats, or building AI agents, Browser Run now offers a faster, more scalable foundation to build on.