Browserbase review

Browserbase is hosted cloud infrastructure for software agents that browse and interact with websites. It sits between an agent or application and the browser: your code starts a cloud browser, then directs it to navigate pages, fill forms, and take actions. Browserbase also offers Search and Fetch APIs for finding sites and converting URLs into HTML, JSON, or markdown.

The platform is broader than a remote browser endpoint. Its listed components include Agent API, Identity, Functions, Sandboxes, runtime, and observability features such as logs, live view, and session replay. That puts it in the infrastructure layer of an agent stack, alongside the model and the application logic that decides what to do next. It is not a self-hosted browser library or a standalone desktop app. The homepage says one API key gives agents access to the platform, and describes its infrastructure as SOC 2 Type II compliant.

The integration surface is API-key-driven. Browserbase lists Browser APIs, Search API, Fetch API, and Agent API, with a homepage example calling bb.fetchAPI.create({ url: “...” }). Search finds relevant websites from a query; Fetch converts a URL into HTML, JSON, or markdown. Browser APIs provide sessions for interactive tasks, while the platform also lists Identity, Observability, Functions, and Sandboxes.

The homepage links to Docs and presents Stagehand and Templates, but does not name programming languages, SDK packages, a CLI, or protocol details. Confirm SDK support, supported languages, API authentication details, and browser-control compatibility in the vendor’s docs before choosing an implementation. The described workflow is to create a browser session, connect a model, and execute a task. Logs, live view, and session replay give teams ways to inspect agent activity; the docs should clarify how those outputs are accessed and retained.

Browserbase lists four tiers, but does not publish monthly or annual base-plan prices or annual billing terms. Start for Free includes 3 concurrent browsers, 1 browser hour, 3 agent runs, 1,000 Search calls, 1,000 Fetch calls, and $5 in model tokens. Get Developer includes 25 concurrent browsers, 100 browser hours, 15 agent runs, 1,000 each of Search and Fetch calls, and 1 GB of proxies. Get Startup includes 100 concurrent browsers, 500 browser hours, 50 agent runs, 1,000 Search calls, 10,000 Fetch calls, and 5 GB of proxies.

Usage beyond included amounts is billed at plan rates. The listed browser-hour overage is $0.12/hour for Developer and $0.10/hour for Startup. Search is $5 per 1,000 calls by default, with listed options from $1 to $12. Fetch defaults to $1 per 1,000 on Developer and $0.50 on Startup; proxy or Extract use can raise Fetch rates. Proxy overages are $12/GB on Developer and $10/GB on Startup. Contact Sales covers 250+ concurrent browsers and custom usage.

Browserbase is sold as hosted cloud infrastructure. The vendor’s homepage and pricing details do not publish a software license, source-code availability, or a self-hosting option. Teams that need to run browser infrastructure in their own environment should ask Browserbase directly whether a self-hosted deployment is available and what it would include.

The vendor also does not publish data-export details in the information available here. Before committing, ask how to retrieve session logs, replay data, and any stored outputs, and whether those can be exported in formats your team can use. Migration effort depends on how much application logic relies on Browserbase-specific APIs, identity features, or runtime tools. Browser automation built around the platform’s APIs may need adaptation to another provider or to a browser stack your team operates itself.

The listed concurrency ranges from 3 browsers on Start for Free to 100 on Startup and 250+ on Contact Sales. Browser-hour allowances and Search, Fetch, and proxy quotas also vary by plan, so model expected concurrency and overages against your workload. The homepage says Browserbase runs 35 million-plus browser sessions a month and describes its infrastructure as SOC 2 Type II compliant; ask the vendor for the compliance documentation and operational details your review requires.

Reddit reports are mixed. One user said session startup was noticeably faster than a self-managed Docker setup, and another reported that stealth worked for most targets. Other commenters described a one-minute minimum billing interval and idle time adding to costs; one reported a site that still blocked sessions about 20% of the time. These are user reports, not published service guarantees. Test your target sites, authentication flows, and recovery behavior, and confirm session billing and reliability expectations with Browserbase before relying on it for critical workflows.