Browserbase & Stagehand review: the short version
Browserbase & Stagehand is a managed platform from Browserbase, and in our 2026 assessment it scores 8.3/10 overall. It is at its best for ai browser agents and teams that refuse to run a browser fleet, it starts at free tier · from $39 / mo, and it expects the platform's managed pool, or your own gateway when volume justifies it behind it. Billed by browser-hours and concurrent sessions; proxy bandwidth is metered separately.
The rest of this review covers how it actually works, what it costs at realistic volumes, which proxy type to pair it with, how it behaves against anti-bot systems, where it breaks, and which alternatives make more sense for adjacent workloads. Every figure below reflects list pricing and hands-on testing rather than vendor marketing copy.
- +Connect existing Playwright code over CDP
- +Live view and session replay for debugging
- +Stagehand act/extract/observe primitives
- +Captcha solving and stealth mode built in
What Browserbase & Stagehand is and how it works
## Browserbase & Stagehand review: the short version
Browserbase & Stagehand is a managed platform from Browserbase, and in our 2026 assessment it scores 8.3/10 overall. It is at its best for ai browser agents and teams that refuse to run a browser fleet, it starts at free tier · from $39 / mo, and it expects the platform's managed pool, or your own gateway when volume justifies it behind it. Billed by browser-hours and concurrent sessions; proxy bandwidth is metered separately.
The rest of this review covers how it actually works, what it costs at realistic volumes, which proxy type to pair it with, how it behaves against anti-bot systems, where it breaks, and which alternatives make more sense for adjacent workloads. Every figure below reflects list pricing and hands-on testing rather than vendor marketing copy.
- Connect existing Playwright code over CDP
- Live view and session replay for debugging
- Stagehand act/extract/observe primitives
- Captcha solving and stealth mode built in
## What Browserbase & Stagehand is and how it works
Browserbase sells the unglamorous half of browser automation: keeping thousands of Chromium instances alive, patched, isolated and observable. You connect Playwright or Puppeteer to a remote CDP endpoint and everything else — scaling, session recycling, stealth patching, proxy attachment, video replay — happens on their side.
Stagehand is the layer that makes it interesting for scraping. Rather than page.click('.btn-primary'), you call act('click the accept cookies button') and extract() with a schema, and an LLM resolves the intent against the live DOM. Selector churn, which is the number one maintenance cost in any long-lived scraper, largely disappears; token cost and latency take its place.
Cost discipline decides whether this works for you. Browser-hours plus roughly $10 per GB of managed residential bandwidth is a premium over self-hosting, so the right jobs are high-value and stateful — agent workflows, authenticated portals, checkout flows — while bulk HTML retrieval stays on an HTTP crawler with your own proxy contract.
## Browserbase & Stagehand scorecard and measured performance
Scores below are relative to the other tools in this directory, not to software in general — a 6 for scale still means a tool that handles more traffic than most projects will ever generate. The performance figures come from crawling a mixed basket of static HTML, JavaScript-rendered commerce and lightly protected listing pages from three regions.
Read them alongside your own target list. The tool almost never determines success rate on its own; the combination of exit IP quality, request fingerprint and request pacing does, which is why two teams running the same framework routinely report success rates thirty points apart.
## Throughput, rendering and resource profile
Throughput numbers only mean something with the cost attached. Browserbase & Stagehand delivers Concurrency-limited by plan, and can render JavaScript, which is convenient and roughly five to twenty times more expensive per page than a plain fetch.
Use these figures to size infrastructure before committing to a plan or a proxy contract. Work backwards from records per day, apply a realistic success rate, add a retry factor of 1.2–1.6, and only then choose concurrency.
## Browserbase & Stagehand pricing and real cost per thousand pages
Billed by browser-hours and concurrent sessions; proxy bandwidth is metered separately.
Platform billing mixes compute units, proxy bandwidth and storage into one balance, which makes forecasting the real risk. Instrument cost per thousand records from week one, set hard memory and concurrency caps on every job, and prefer HTTP-based runs over browser runs wherever the data allows — the difference between those two modes is often ten times the unit cost.
A useful discipline: express every option as cost per thousand usable records, not cost per month. A plan that looks cheap and delivers a 60% success rate is more expensive than a premium option at 95%, because the failures consume bandwidth, retries, engineering attention and calendar time.
## Best proxies for scraping with Browserbase & Stagehand
Managed platforms bundle proxies with compute, which is convenient and rarely the cheapest per gigabyte. Every serious platform allows bring-your-own proxy URLs, and once monthly bandwidth passes a few hundred gigabytes a direct contract with a residential provider will usually beat the bundled rate by a wide margin. Run the bundled pool during development, then price a switch before you scale.
With Browserbase & Stagehand specifically, identity attaches through built-in residential proxies per session, or bring your own. Get that wiring right before tuning anything else — a rotation bug that reuses one exit across a thousand requests will look exactly like a bad proxy provider.
## How Browserbase & Stagehand handles anti-bot systems
The upside of a platform is that challenge handling is somebody else's job: pools are rotated, fingerprints maintained, and popular targets covered by scrapers the vendor patches. The downside is opacity. When a run starts failing you cannot inspect the exit IP or the TLS handshake, so keep a small self-hosted fallback path for critical feeds rather than depending on a single vendor's roadmap.
Practically, treat detection as a budget rather than a binary. Measure success rate per domain daily, escalate a domain one tier at a time — better headers, then better IPs, then a browser, then an unlocker — and stop at the first tier that clears your threshold. Escalating everything to the most expensive tier is the most common and most costly mistake in scraping operations.
## Scaling Browserbase & Stagehand in production
Scale on a platform means concurrency tiers and queue discipline, not servers. Use asynchronous batch submission instead of long-held synchronous requests, schedule heavy jobs off-peak, deduplicate URLs before submission, and export to your own warehouse continuously so a plan change or vendor incident never strands your dataset.
- Track success rate, cost per thousand records and bytes per page as your three primary metrics
- Retire proxy sessions automatically on repeated failures instead of retrying blindly
- Deduplicate URLs before dispatch — duplicates cost bandwidth, credits and rate-limit headroom
- Validate content, not just HTTP status: a 200 that returns a consent wall is a failed fetch
- Keep a second fetching path warm so a vendor incident degrades throughput instead of stopping it
## Browserbase & Stagehand pros and cons
No scraping tool is universally correct; each one trades cost, control and maintenance in a different ratio. Browserbase & Stagehand makes the following trade explicitly.
## Who should use Browserbase & Stagehand — and who should not
Choose Browserbase & Stagehand when your workload looks like ai browser agents and teams that refuse to run a browser fleet and your team is comfortable with Cloud · Playwright/Puppeteer CDP · Stagehand SDK. It fits organisations that have already decided whether they are buying outcomes or building capability, because it sits clearly on one side of that line: you buy an outcome and trade unit cost for removed maintenance.
Look elsewhere if your targets are unprotected static pages — a self-hosted crawler on datacenter proxies will do the same job for a fraction of the price.
## Compliance and responsible collection
Collecting publicly accessible data is broadly lawful in most jurisdictions, but the surrounding obligations are real: respect robots.txt where it expresses the publisher's intent, avoid authentication walls you have not been granted access to, never collect personal data without a lawful basis under GDPR or equivalent, and keep request rates low enough that you never degrade the target's service.
Reputable proxy providers enforce KYC precisely because misuse of their networks is their liability as well as yours. Document what you collect, why, how long you retain it and who can access it. For AI training corpora, record licensing and provenance per source — that record is increasingly the first thing an auditor or enterprise customer asks to see.
Browserbase & Stagehand scorecard and measured performance
Scores below are relative to the other tools in this directory, not to software in general — a 6 for scale still means a tool that handles more traffic than most projects will ever generate. The performance figures come from crawling a mixed basket of static HTML, JavaScript-rendered commerce and lightly protected listing pages from three regions.
Read them alongside your own target list. The tool almost never determines success rate on its own; the combination of exit IP quality, request fingerprint and request pacing does, which is why two teams running the same framework routinely report success rates thirty points apart.
| Criterion | Score | Assessment |
|---|---|---|
| Ease of adoption | 10/10 | Productive on day one |
| Scale ceiling | 8/10 | Fine into the low millions |
| Anti-bot resilience | 8/10 | Good with the right proxies |
| Documentation | 8/10 | Adequate; community fills the gaps |
| Value for money | 6/10 | Premium pricing — justify it with volume |
Throughput, rendering and resource profile
Throughput numbers only mean something with the cost attached. Browserbase & Stagehand delivers Concurrency-limited by plan, and can render JavaScript, which is convenient and roughly five to twenty times more expensive per page than a plain fetch.
Use these figures to size infrastructure before committing to a plan or a proxy contract. Work backwards from records per day, apply a realistic success rate, add a retry factor of 1.2–1.6, and only then choose concurrency.
| Metric | Observed | Notes |
|---|---|---|
| Throughput | Concurrency-limited by plan | Per worker or per plan tier, on a stable target |
| JavaScript rendering | Full, managed Chromium | Rendering multiplies cost 5–20× versus plain HTTP |
| Memory footprint | None (remote) | Sizing input for container limits |
| Success profile | Strong with stealth mode and residential exits | Depends far more on proxy quality than on the tool |
| Proxy support | Built-in residential proxies per session, or bring your own | How identity is attached to a request |
Browserbase & Stagehand pricing and real cost per thousand pages
Billed by browser-hours and concurrent sessions; proxy bandwidth is metered separately.
Platform billing mixes compute units, proxy bandwidth and storage into one balance, which makes forecasting the real risk. Instrument cost per thousand records from week one, set hard memory and concurrency caps on every job, and prefer HTTP-based runs over browser runs wherever the data allows — the difference between those two modes is often ten times the unit cost.
A useful discipline: express every option as cost per thousand usable records, not cost per month. A plan that looks cheap and delivers a 60% success rate is more expensive than a premium option at 95%, because the failures consume bandwidth, retries, engineering attention and calendar time.
| Plan | Price | What you get |
|---|---|---|
| Free | $0 | 1 concurrent browser, 60 session minutes |
| Developer | $39 / mo | 3 concurrent browsers, 200 hours, proxies |
| Startup | $99+ / mo | Higher concurrency, extended session length |
| Proxy bandwidth | ≈ $10 / GB | Managed residential exits inside sessions |
Best proxies for scraping with Browserbase & Stagehand
Managed platforms bundle proxies with compute, which is convenient and rarely the cheapest per gigabyte. Every serious platform allows bring-your-own proxy URLs, and once monthly bandwidth passes a few hundred gigabytes a direct contract with a residential provider will usually beat the bundled rate by a wide margin. Run the bundled pool during development, then price a switch before you scale.
With Browserbase & Stagehand specifically, identity attaches through built-in residential proxies per session, or bring your own. Get that wiring right before tuning anything else — a rotation bug that reuses one exit across a thousand requests will look exactly like a bad proxy provider.
| Target profile | Proxy type | Typical price | Why |
|---|---|---|---|
| Internal APIs, open data, docs sites | Datacenter | $0.30 – $2.00 / IP / mo | No consumer-IP requirement; cheapest possible bandwidth |
| Mid-tier commerce, listings, forums | Rotating residential | $1.00 – $8.00 / GB | Real ISP-assigned IPs clear reputation checks |
| Logged-in accounts, dashboards | ISP / static residential | $1.50 – $6.00 / IP / mo | One stable identity per account, held for months |
| App-only endpoints, hardest anti-bot | Mobile (4G/5G) | $4.00 – $20.00 / GB | Carrier CGNAT makes per-IP blocking costly for the target |
| Everything already blocked | Unlocker API | $0.50 – $3.00 / 1k requests | Challenge solving handled provider-side, billed per success |
Connect Playwright to a managed session (Node)
import { chromium } from "playwright-core";
import Browserbase from "@browserbasehq/sdk";
const bb = new Browserbase({ apiKey: process.env.BROWSERBASE_API_KEY });
const session = await bb.sessions.create({
projectId: process.env.BROWSERBASE_PROJECT_ID,
proxies: [{ type: "browserbase", geolocation: { country: "US", state: "NY" } }],
browserSettings: { solveCaptchas: true },
});
const browser = await chromium.connectOverCDP(session.connectUrl);
const page = browser.contexts()[0].pages()[0];
await page.goto("https://example.com", { waitUntil: "domcontentloaded" });
console.log(await page.title());
await browser.close();How Browserbase & Stagehand handles anti-bot systems
The upside of a platform is that challenge handling is somebody else's job: pools are rotated, fingerprints maintained, and popular targets covered by scrapers the vendor patches. The downside is opacity. When a run starts failing you cannot inspect the exit IP or the TLS handshake, so keep a small self-hosted fallback path for critical feeds rather than depending on a single vendor's roadmap.
Practically, treat detection as a budget rather than a binary. Measure success rate per domain daily, escalate a domain one tier at a time — better headers, then better IPs, then a browser, then an unlocker — and stop at the first tier that clears your threshold. Escalating everything to the most expensive tier is the most common and most costly mistake in scraping operations.
Scaling Browserbase & Stagehand in production
Scale on a platform means concurrency tiers and queue discipline, not servers. Use asynchronous batch submission instead of long-held synchronous requests, schedule heavy jobs off-peak, deduplicate URLs before submission, and export to your own warehouse continuously so a plan change or vendor incident never strands your dataset.
- +Track success rate, cost per thousand records and bytes per page as your three primary metrics
- +Retire proxy sessions automatically on repeated failures instead of retrying blindly
- +Deduplicate URLs before dispatch — duplicates cost bandwidth, credits and rate-limit headroom
- +Validate content, not just HTTP status: a 200 that returns a consent wall is a failed fetch
- +Keep a second fetching path warm so a vendor incident degrades throughput instead of stopping it
Browserbase & Stagehand pros and cons
No scraping tool is universally correct; each one trades cost, control and maintenance in a different ratio. Browserbase & Stagehand makes the following trade explicitly.
| Strengths | Weaknesses |
|---|---|
| Removes the entire browser-fleet operations burden | Per-hour pricing gets expensive on long crawls |
| Session replay makes agent debugging tractable | Managed proxy bandwidth at ~$10/GB is above market |
| Stagehand's act() survives DOM changes that break selectors | Another vendor in the critical path |
| Existing Playwright scripts connect with a one-line change | Not the cheapest way to fetch simple HTML |
Who should use Browserbase & Stagehand — and who should not
Choose Browserbase & Stagehand when your workload looks like ai browser agents and teams that refuse to run a browser fleet and your team is comfortable with Cloud · Playwright/Puppeteer CDP · Stagehand SDK. It fits organisations that have already decided whether they are buying outcomes or building capability, because it sits clearly on one side of that line: you buy an outcome and trade unit cost for removed maintenance.
Look elsewhere if your targets are unprotected static pages — a self-hosted crawler on datacenter proxies will do the same job for a fraction of the price.
Compliance and responsible collection
Collecting publicly accessible data is broadly lawful in most jurisdictions, but the surrounding obligations are real: respect robots.txt where it expresses the publisher's intent, avoid authentication walls you have not been granted access to, never collect personal data without a lawful basis under GDPR or equivalent, and keep request rates low enough that you never degrade the target's service.
Reputable proxy providers enforce KYC precisely because misuse of their networks is their liability as well as yours. Document what you collect, why, how long you retain it and who can access it. For AI training corpora, record licensing and provenance per source — that record is increasingly the first thing an auditor or enterprise customer asks to see.
Browserbase & Stagehand FAQs
Does Browserbase include proxies?+
Yes, managed residential exits with country and state targeting, billed per GB; you can also attach your own gateway.
What is Stagehand?+
An open-source SDK on top of Playwright that adds act(), extract() and observe() — natural-language actions resolved by an LLM against the live page.
Is it cheaper than self-hosting browsers?+
Below a few hundred browser-hours a month, usually. Above that, your own container fleet plus a direct proxy contract wins.
Keywords covered
ai scraping proxy · headless browser proxy · best proxies for scraping · scraping proxy network
