10 Ways Browser Run Just Got Faster and More Scalable on Cloudflare Containers

If you're a developer using Browser Run, get ready for a major upgrade. We've rebuilt the platform on Cloudflare's Containers, and the results are impressive: you can now spin up 60 browsers per minute, run up to 120 concurrently (four times the previous limit), and enjoy Quick Action response times that have dropped by more than 50%. All of this happens automatically—no changes needed on your end. In this article, we'll walk through the ten key things you need to know about this transformation, from the old infrastructure challenges to the cutting-edge solution that powers it all. Let's dive in.

1. What Exactly Is Browser Run?

Browser Run is a developer tool that lets you programmatically control and interact with headless browser instances running on Cloudflare's global network. Think of it as a remote browser you can command via code—perfect for end-to-end testing of web apps, investigating suspicious URLs securely, rendering PDFs, capturing screenshots, or extracting content. Recently, it's also become essential for AI agents that need to interact with web pages autonomously. With this upgrade, Browser Run aims to be the go-to platform for securely using automated browsers at massive scale.

10 Ways Browser Run Just Got Faster and More Scalable on Cloudflare Containers — Source: blog.cloudflare.com

2. Key Use Cases: From Testing to AI

Developers rely on Browser Run for a variety of tasks. End-to-end testing ensures your web application works across different scenarios without manual effort. Security teams use it to safely examine suspicious links in isolated browser instances. Content extraction and PDF generation are common quick actions. But the emerging killer app is AI: agents that browse the web to gather data, fill forms, or perform transactions. Browser Run provides a reliable, scalable environment for these AI-driven interactions, all while maintaining security and privacy.

3. The Old Infrastructure: Sharing a Bunk Bed

Before moving to Cloudflare Containers, Browser Run shared infrastructure with Browser Isolation (BISO). While technically similar, this marriage created problems. BISO's larger container images slowed startup times and delayed development. Worse, BISO browsers weren't optimally distributed globally, hurting resiliency and latency. BISO users typically had long, steady sessions, while Browser Run experienced short, spiky usage. This mismatch caused scaling bottlenecks and availability delays. It was clear a change was needed.

4. Enter Cloudflare Containers: A Tailored Solution

Cloudflare's Durable Object (DO)-enabled Containers entered open beta last year, offering a perfect alternative. By moving Browser Run to its own dedicated container infrastructure, we eliminated the conflicts with BISO. Containers provide faster startup times, better global distribution, and independent scaling. This means Browser Run can now handle sudden spikes without impacting other services. The move also allowed us to optimize specifically for headless browser workloads, improving performance across the board.

5. The Migration Process: Gradual and Safe

We didn't switch overnight. Instead, we inserted a Worker in our request path to route some traffic to Container-powered browsers alongside the old BISO ones. This dual-support phase let us compare performance, catch bugs, and build confidence. We first activated Containers for Quick Actions endpoints, then for Workers browser binding on free accounts, followed by pay-as-you-go users, and finally contract customers. The entire transition required no action or redeployment from you—it just worked.

6. Performance Gains: 4x Higher Limits

The numbers speak for themselves. The previous limit was 15 browsers per minute and 30 concurrent. Now you can spin up 60 browsers per minute and run 120 concurrently—a fourfold increase. This is critical for teams running large-scale testing or AI scraping operations. The underlying container architecture scales horizontally, so you get consistent performance no matter how many browsers you launch. Bottlenecks that once caused queuing are now a thing of the past.

7. Quick Action Response Times Drop Over 50%

Quick Actions—like taking a screenshot or fetching page content—are the most frequent operations. With the move to Containers, median response times have fallen by more than 50%. This means your applications feel snappier, and you can complete tasks faster. The improvement comes from reduced startup overhead and better global routing. Whether you're running a quick check or a batch of actions, the speed boost is immediately noticeable.

8. Zero Changes Required on Your End

One of our core principles is that improvements should be invisible to users. This migration is no exception. All existing Workers that use the Browser Run binding continue to work without any modifications. Your code, configurations, and API calls remain exactly the same. The performance and scalability benefits are delivered automatically. We've handled the heavy lifting so you can focus on building.

9. Faster Feature Development and Fixes

By moving to Cloudflare Containers, we've decoupled Browser Run from BISO's development cycle. This means we can ship new features, bug fixes, and performance improvements much faster. Our team now has full control over the infrastructure, allowing us to iterate rapidly. You'll see more frequent updates and enhancements as we continue to optimize the platform. This agility is a direct result of building on a modern container foundation.

10. Our Commitment: Platform First

Like many successful product platforms, we believe in eating our own dogfood. By building Browser Run on Cloudflare's containers, we not only improve our own service but also discover and fix pain points before external customers encounter them. This migration demonstrates our commitment to using Cloudflare's latest technologies to deliver the best possible experience. As containers evolve, we'll continue to adopt innovations that benefit Browser Run users. The future is brighter—and faster—than ever.

From higher limits to faster response times and a future-proof architecture, Browser Run's move to Cloudflare Containers is a win for every developer. No action required from you—just enjoy the speed and scale. Ready to give it a spin? Your next headless browser session is already faster.

Tags: