Browser Use just teased its next infrastructure product: browser-wall, a cloud browser hub that lets a single agent control multiple browsers in parallel through one unified connection point. The demo shows an agent driving four browsers simultaneously, each loaded with separate profiles and proxies. It is not fully launched yet, but a waitlist is live.

The problem it is solving

Running browser agents at scale today is a mess of infrastructure. Running headless browsers locally often leads to crashes from memory leaks, heavy server resource usage, broken setups after browser updates, and detection by anti-bot systems. The standard workaround is to spin up a separate cloud browser session per task, but that means managing a fleet of individual CDP connections, each with its own lifecycle, proxy, and auth state.

Browser-wall collapses that complexity. Instead of your agent juggling N separate WebSocket connections, it exposes one CDP URL that acts as a router to all active cloud browsers underneath. Think of it as a load balancer, but for browser sessions.

What browser-wall actually does

Based on the announcement, browser-wall is built around three core capabilities:

• One CDP URL to rule them all. Cloud browser APIs are services that provide remote browser instances accessible via Chrome DevTools Protocol (CDP) or WebSocket connections. Browser-wall wraps multiple of those instances behind a single endpoint, so your agent code does not change as you scale from one browser to ten.
• Sub-second cold starts. The demo shows four browsers spinning up nearly instantly. Browser Use's new infrastructure claims sub-second cold starts and describes itself as 3x cheaper at $0.02/hr.
• Profiles and proxies pre-loaded. Each browser in the wall comes with its own identity. Browser Use already offers anti-detect, CAPTCHA solving, and 195+ country proxies, and browser-wall appears to bundle those capabilities per-session automatically.