Browser Use review

Browser Use combines browser automation software with hosted browser infrastructure. Its web agents take a task and return JSON; its stealth browsers are designed to get past bot checks. Browser Harness is a free, open-source browser tool for Claude Code and Codex, so the product is not only a hosted agent service.

The pricing page lists pay-as-you-go access at $0 per month, with no subscription or annual billing. Usage costs extra, and credits never expire. Self-serve includes up to 1,000 browsers at once. Teams that need custom deployment or terms can ask about Enterprise, which lists custom concurrency above 1,000 and on-prem deployment. The homepage also lists US or EU cloud, with EU runs in Frankfurt, and says SOC 2 Type II and HIPAA are available on enterprise plans. For a team weighing a switch, the key distinction is between Browser Use as an open-source harness and its metered browser infrastructure.

The clearest selling point is infrastructure choice. Teams can use Browser Use’s hosted browsers, run browsers on their own network with an on-prem deployment, or use the free, open-source Browser Harness with Claude Code or Codex. The homepage lists US and EU cloud options, with EU runs in Frankfurt. Enterprise plans list SOC 2 Type II and HIPAA, which may matter when a browser agent handles sensitive workflows.

The billing model is flexible for uneven workloads: according to the pricing page, there is no subscription or annual commitment, and credits do not expire. Self-serve allows up to 1,000 browsers at once, with higher custom concurrency available through Enterprise. Listed costs include browser time at $0.02 per hour, billed by the minute with a one-minute minimum; home-IP traffic at $5/GB; and direct or customer-provided proxy traffic at $0.20/GB. BU Ultrafast is listed at $0.006 per task.

User reports are mixed, but one r/LocalLLaMA poster said the WebUI completed varied tasks, including summarizing email. That is an anecdote, not a reliability guarantee.

The pricing is flexible, but not automatically cheap. Browser time, traffic, and optional task processing are separate charges, while agent-model token rates vary. Bringing your own model key costs the provider rate plus 0.2x, according to the pricing details. The $0 monthly figure is not an all-in price: it includes a one-time $1 signup credit, and browser time has a one-minute minimum. Home-IP traffic costs more than direct or your own proxy traffic. Enterprise pricing is custom, not published.

There is also a hard self-serve concurrency ceiling: up to 1,000 browsers at once. Higher concurrency requires Enterprise, and the pricing page lists paid-spend thresholds of $100 for 50 browsers, $1,000 for 250, $5,000 for 500, and $25,000 for 1,000. Those thresholds make scaling costs worth checking before moving production workflows.

Agent reliability is the bigger question. One r/AI_Agents thread describes hallucinated clicks and incomplete sessions; a separate r/LocalLLaMA poster reports successful tasks. These are individual reports, not a controlled comparison, but they point to a risk buyers should validate against their own sites and workflows.

Browser Use has no subscription or annual billing. The self-serve plan is $0 per month, with pay-as-you-go usage charges; credits never expire. It includes up to 1,000 browsers at once, SOC 2 Type II, a signed DPA and a $1 one-time signup credit. Enterprise pricing is custom and not published, so there is no listed price for the jump beyond 1,000 concurrent browsers or for on-prem deployment.

The main costs are metered: browser time is $0.02 per hour, billed by the minute with a one-minute minimum. Home-IP traffic is $5/GB; direct traffic or your own proxy is $0.20/GB. BU Ultrafast costs $0.006 per task. Agent model rates vary by token; bringing your own key costs the provider’s rate plus 0.2x. Concurrency thresholds are tied to total paid: $100 for 50 browsers, $1,000 for 250, $5,000 for 500 and $25,000 for 1,000. Those charges make usage less predictable than a flat monthly plan.

Treat a move to Browser Use as an integration project, not a simple account swap. First, list the browser tasks you need, the JSON results each task must return and your expected concurrency. Then check whether the hosted browser, Browser Harness for Claude Code or Codex, or an enterprise on-prem deployment fits. The published product information does not specify migration tooling, export formats or data-retention terms, so confirm those before moving production workflows.

The open-source Browser Harness may give developers a route to try its Claude Code or Codex workflow without adopting the hosted service. But the published material does not establish that it replaces the hosted browser or provides a portable way to move existing agent setups. We also have no Reddit posts or comments in the published sources, so we can’t attribute reasons for leaving to Reddit users. The stated caveats point to the questions to resolve before switching: agent reliability, variable usage costs and unpublished support terms. Compare those against your current setup before committing.