Browser Use adds cloud profiles and geo proxies, with 484 browsers in <2s

• Browser Use added cloud profiles that keep browser state across sessions, and browser_use's profile demo frames the feature as a way for agents to stay logged in without redoing setup.
• The product docs behind browser_use's Browser Use Cloud link and Create Profile say profiles are meant to preserve login state between tasks, typically one profile per user.
• Browser Use also pushed geo-targeted proxies, and browser_use's proxy demo says cloud browsers can now launch from different countries to handle geo-restricted or anti-bot flows.
• The browser session API shown in Create Browser Session exposes a proxyCountryCode field that defaults to us, while browser_use's 484-browser demo showed 484 browsers starting in under two seconds.
• The bigger product pitch on Stealth Browsers is a hosted browser stack with a custom Chromium fork, built-in CAPTCHA solving, residential proxies, and CDP access for existing Playwright or Puppeteer code.

You can open the profile API docs, skim the stealth browser page, and even read Browser Use's own CLOUD.md, which spells out that uploaded profiles can carry cookies, local storage, saved passwords, and credentials into cloud sessions.

The new profile flow is a state-persistence feature, not just an account page. Create Profile says profiles preserve browser state between tasks and are mainly used to keep users logged in.

Browser Use's own CLOUD.md goes further: a reused profile can persist authentication cookies, local storage, saved passwords, credentials, and user preferences across sessions. The same file says users can upload a Chrome profile from their own machine, then reuse it in cloud automations.

Browser Use pitched proxies as a way to create browsers from any country and bypass geo restrictions or anti-bot checks. The official stealth browser page says residential proxies are built into the platform across 195-plus countries, alongside automatic CAPTCHA solving.

The API surface matches the pitch. Create Browser Session includes proxyCountryCode, defaults it to us, and lets users disable the proxy by setting it to null.

The headline demo was raw startup speed. Browser Use first showed 25 browsers starting in less than a second, then followed with a 484-browser run that finished in under two seconds.

The official pricing page is more conservative than the demo clips: self-serve plans list 3, 25, 200, and 500 concurrent sessions on Free, Dev, Business, and Scaleup, with browser profiles capped at 1, 5, or unlimited depending on tier. That makes the 484-browser clip look like a near-capacity demo of the top self-serve plan, not just a flashy benchmark.

Under the hood, Browser Use is packaging several pieces into one hosted browser layer: a hardened Chromium fork, CDP access, built-in residential proxy routing, and CAPTCHA solving, according to the official stealth browser page. Wes Roth's post adds the company's claim that the stack also uses a Firecracker fork and a custom Linux kernel for browser automation workloads.

That combination explains why these smaller feature drops matter. Profiles remove session-management glue, proxies remove regional routing glue, and the hosted browser layer keeps the whole thing accessible through the same remote browser interface described in the remote browser docs.