Key differences
Published by Notte, which competes with the products on this page. Every figure links to the provider's own documentation, checked on 2026-11-02.
- Browser-hour rate on self-serve plans: Browserbase $0.10 (Startup) to $0.12 (Developer); Browser Use Cloud $0.02. The Pricing section shows each rate as published.[1][2]
- Free tier - Browserbase: Free plan, $0/mo: 3 concurrent browsers, 1 browser hour, 15 minutes per session, 3 Agent runs, 1,000 Search calls and 1,000 Fetch calls included. Browser Use Cloud: $1 one-time credit for eligible Google, GitHub or Microsoft signups (does not renew) and 10 concurrent sessions, with no subscription. Free accounts are limited to cost-efficient models until a first top-up.[3][4]
- Highest concurrency on self-serve plans: Browserbase 100 (Startup); Browser Use Cloud 1000 (Pay as you go, Tier 4 ($25,000 total paid)).[1][4]
- Longest session on self-serve plans: Browserbase 6 hours (Developer); Browser Use Cloud 4 hours (Free (Tier 0)).[1][4]
- Regions: Browserbase lists 4 regions (selectable); Browser Use Cloud lists 2 regions (selectable).[5][6]
- Self-hosting: Browserbase No; Browser Use Cloud Enterprise.[3][7]
Sources: docs.browserbase.com [1] ↗docs.browser-use.com [2] ↗browserbase.com [3] ↗browser-use.com [4] ↗docs.browserbase.com [5] ↗docs.browser-use.com [6] ↗browser-use.com [7] ↗
Pricing
Entry paid plan is the cheapest listed plan with a monthly price, or the first usage-only plan; Enterprise and contact-sales plans are excluded. Browser-hour rates span the lowest to highest rate across self-serve paid plans, normalized to one browser-hour.
| Item | Browserbase | Browser Use Cloud | Notte (publisher) |
|---|---|---|---|
| Billing unit | Browser time is billed by the minute (one-minute minimum per session); proxy bandwidth by the MB (one-MB minimum per session). Plans include a monthly allocation of browser hours and proxy GB; overage is billed per browser hour and per GB.[1] | Browser time: $0.02 per browser-hour, metered by the minute. Credits for the requested timeout are reserved when the browser is created and unused reserved credits are returned after it ends. The final charge has a one-minute minimum and partial minutes round up. Network traffic is charged separately per GB, and hosted agent runs also bill model tokens.[2] | Dollar-denominated credits spent per hour of browser session ($0.01 per hour); the page says usage is rounded by a billing policy without stating the increment[3] |
| Free tier | Free plan, $0/mo: 3 concurrent browsers, 1 browser hour, 15 minutes per session, 3 Agent runs, 1,000 Search calls and 1,000 Fetch calls included.[4] | $1 one-time credit for eligible Google, GitHub or Microsoft signups (does not renew) and 10 concurrent sessions, with no subscription. Free accounts are limited to cost-efficient models until a first top-up.[2] | $10 credits granted once with no expiry; 5 concurrent browsers; 15-minute sessions; no card required[3] |
| Entry paid plan | Developer ($20/mo)[1] | Pay as you go, Tier 1 ($100 total paid)[5] | Developer ($20/mo)[3] |
| Browser-hour rate (self-serve plans) | $0.10 (Startup) to $0.12 (Developer)[1] | $0.02[5][2] | $0.01[3] |
| Rate as published (entry paid plan) | then $0.12/browser hr[1] | $0.02/browser-hour plus traffic; no subscription[5] | $20/mo including $20 credits per month; usage then $0.01 / hour of browser sessions from credits[3] |
| Included browser hours (entry paid plan) | 100 hours[1] | Not published | Not published |
| Proxy per GB (entry paid plan) | $12[1] | $5[5] | $10[3] |
| Proxy pricing | Free: 0 GB included, overage N/A. Developer: 1 GB included, then $12/GB. Startup: 5 GB included, then $10/GB. Scale: usage-based proxy with custom overage.[1] | Managed residential proxy $5/GB, charged only when the Browser Use residential proxy network is used. Direct connection or bring-your-own-proxy egress $0.20/GB.[2] | Built-in residential proxies $10 per GB. Custom proxies on the Startup plan $0.20 per GB, on top of what the proxy provider charges. Bandwidth is counted as request plus response bytes, rounded up to the next MB per session.[6] |
| CAPTCHA pricing | No separate meter listed. Auto captcha solving is included on Developer, Startup and Scale plans and listed as No on Free.[1] | No extra charge: automatic reCAPTCHA solving is included, hCaptcha also supported but newer and not guaranteed. Off in the EU deployment. No solver API key needed.[7] | Included on Free, Developer and Startup (no per-solve charge listed); Enterprise row says Targeted[3] |
| All plans | Free $0; Developer $20/mo; Startup $99/mo; Scale custom[4] | Free (Tier 0) $0; Pay as you go, Tier 1 ($100 total paid) price not published; Pay as you go, Tier 2 ($1,000 total paid) price not published; Pay as you go, Tier 3 ($5,000 total paid) price not published; Pay as you go, Tier 4 ($25,000 total paid) price not published; Enterprise custom[8] | Free $0; Developer $20/mo; Startup $100/mo; Enterprise custom[3] |
Sources: docs.browserbase.com [1] ↗browser-use.com [2] ↗notte.cc [3] ↗browserbase.com [4] ↗docs.browser-use.com [5] ↗docs.notte.cc [6] ↗browser-use.com [7] ↗browser-use.com [8] ↗
Limits
| Item | Browserbase | Browser Use Cloud | Notte (publisher) |
|---|---|---|---|
| Max session duration | 6 hours[1] | 4 hours (240 minutes) per browser session[2] | Per plan: 15 min Free, 120 min Developer, 300 min Startup, custom on Enterprise. The API parameter max_duration_minutes documents a schema maximum of 1440 minutes, which exceeds the self-serve plan limits.[3] |
| Default session timeout | Not published | 60 minutes (standalone browser timeout parameter, range 1-240 minutes)[4] | 15 minutes (max_duration_minutes default)[5] |
| Idle timeout | A CDP connection can close after 10 minutes with no data in either direction; without keepAlive the session ends when the client disconnects.[6] | V4 agent browsers stop about 2 minutes after the last run activity (cleanup runs every minute, so expect 2-3 minutes); keepAlive (integer seconds, 120-14400) can keep one open longer. No idle timeout is documented for standalone browsers, which run until stopped or until their timeout.[7] | Default 3 minutes, configurable from 1 to 30 minutes; each operation resets it[5] |
| Max concurrency | Per plan: Free 3, Developer 25, Startup 100, Scale 250+. Assigned at the organization level and split across projects.[8] | 10 concurrent sessions on a new project; 50 / 250 / 500 / 1,000 after $100 / $1,000 / $5,000 / $25,000 total paid; 1,000+ on Enterprise. Agents and browsers share one limit.[9] | Browsers: 5 Free, 25 Developer, 100 Startup, Custom Enterprise. Agents and functions: 5, 25, 100, Custom.[3] |
| Highest concurrency on self-serve plans | 100 (Startup)[10] | 1000 (Pay as you go, Tier 4 ($25,000 total paid))[9] | 100 (Startup)[3] |
| Session creation rate limit | Per plan, per any 60-second period: Free 5, Developer 25, Startup 50, Scale 150+. Requests over the limit receive a 429 error.[8] | No separate session-creation limit is documented. HTTP request budget per project: creates, lists, updates, deletes, event reads and full run reads get max(25, 2 x stored concurrency) requests/second, capped at 100; selected status reads get max(25, 2 x stored concurrency) with no cap. A Tier 0 project is on the 25 RPS floor. The project limiter counts requests in five-second windows. Separate per-IP edge ceilings apply: 1,000 requests/second for general API traffic and 2,500 requests/second for selected status reads, evaluated over 300 seconds.[7] | Rate limited per API key with a separate budget for session starts (POST /sessions/start): per minute 50 (Free), 50 (Developer), 100 (Startup); per hour 200, 200, 1,000; per day 600, 600, 10,000; Enterprise custom. Requests over the limit return 429.[11] |
| Regions | us-west-2, us-east-1, eu-central-1, ap-southeast-1 (selectable)[12] | US (default, api.browser-use.com), EU (Frankfurt, Germany; api.eu.browser-use.com) (selectable)[13] | Not published |
| Data retention (entry paid plan) | Not published | Not published | Not published |
Sources (13)
docs.browserbase.com [1] ↗docs.browser-use.com [2] ↗notte.cc [3] ↗docs.browser-use.com [4] ↗docs.notte.cc [5] ↗docs.browserbase.com [6] ↗docs.browser-use.com [7] ↗docs.browserbase.com [8] ↗browser-use.com [9] ↗docs.browserbase.com [10] ↗docs.notte.cc [11] ↗docs.browserbase.com [12] ↗docs.browser-use.com [13] ↗
Features
| Feature | Group | Browserbase | Browser Use Cloud | Notte (publisher) |
|---|---|---|---|---|
| Connect over CDP | Connect | Yes[1] | Yes[2] | Yes[3] |
| Playwright | Connect | Yes[4] | Yes[2] | Yes[3] |
| Puppeteer | Connect | Yes[5] | Yes[2] | Yes[6] |
| Selenium | Connect | Yes[7] | No[8] | Yes[9] |
| Persistent profiles | Login and state | Yes[10] | Yes[11] | Yes[12] |
| Credential vault | Login and state | Yes[13] | Yes[14] | Yes[15] |
| Managed login | Login and state | Unknown | Unknown | Yes[16] |
| TOTP and 2FA handling | Login and state | Unknown | Yes[17] | Yes[18] |
| CAPTCHA solving | Anti-bot and network | Yes[19] | Yes[20] | Yes[21] |
| Stealth and fingerprinting | Anti-bot and network | Yes[4] | Yes[22] | Yes[23] |
| Managed proxies | Anti-bot and network | Yes[24] | Yes[25] | Yes[26] |
| Proxy geo-targeting | Anti-bot and network | Yes[24] | Yes[22] | Yes[26] |
| Bring your own proxy | Anti-bot and network | Yes[24] | Yes[25] | Yes[26] |
| Live view | Observe and control | Yes[27] | Yes[28] | Yes[29] |
| Embeddable live view | Observe and control | Yes[27] | Yes[30] | Yes[31] |
| Human takeover | Observe and control | Yes[27] | Yes[32] | Yes[31] |
| Session recording | Observe and control | Yes[33] | Yes[30] | Yes[34] |
| Network logs | Observe and control | Yes[33] | Unknown | Yes[35] |
| File downloads | Files and extensions | Yes[36] | Yes[8] | Yes[37] |
| File uploads | Files and extensions | Yes[38] | Yes[39] | Yes[37] |
| Browser extensions | Files and extensions | Yes[40] | Yes[41] | No[42] |
| Serverless functions | Run code and agents | Yes[43] | Unknown | Yes[44] |
| Scheduling | Run code and agents | Unknown | Yes[45] | Yes[46] |
| Webhooks | Run code and agents | Yes[47] | Yes[48] | Yes[49] |
| MCP server | Run code and agents | Yes[50] | Yes[51] | Yes[52] |
| Hosted agent API | Run code and agents | Yes[53] | Yes[54] | Yes[55] |
| Scrape and fetch API | Run code and agents | Yes[56] | Unknown | Yes[57] |
| Self-hosting | Deployment | No[4] | Enterprise[58] | Enterprise[55] |
| Region selection | Deployment | Yes[59] | Yes[60] | Unknown |
Sources (60)
docs.browserbase.com [1] ↗browser-use.com [2] ↗docs.notte.cc [3] ↗browserbase.com [4] ↗docs.browserbase.com [5] ↗docs.notte.cc [6] ↗docs.browserbase.com [7] ↗docs.browser-use.com [8] ↗docs.notte.cc [9] ↗docs.browserbase.com [10] ↗docs.browser-use.com [11] ↗docs.notte.cc [12] ↗docs.browserbase.com [13] ↗docs.browser-use.com [14] ↗docs.notte.cc [15] ↗docs.notte.cc [16] ↗docs.browser-use.com [17] ↗docs.notte.cc [18] ↗docs.browserbase.com [19] ↗docs.browser-use.com [20] ↗docs.notte.cc [21] ↗docs.browser-use.com [22] ↗docs.notte.cc [23] ↗docs.browserbase.com [24] ↗docs.browser-use.com [25] ↗docs.notte.cc [26] ↗docs.browserbase.com [27] ↗browser-use.com [28] ↗docs.notte.cc [29] ↗docs.browser-use.com [30] ↗docs.notte.cc [31] ↗docs.browser-use.com [32] ↗docs.browserbase.com [33] ↗docs.notte.cc [34] ↗docs.notte.cc [35] ↗docs.browserbase.com [36] ↗docs.notte.cc [37] ↗docs.browserbase.com [38] ↗docs.browser-use.com [39] ↗docs.browserbase.com [40] ↗docs.browser-use.com [41] ↗docs.notte.cc [42] ↗docs.browserbase.com [43] ↗docs.notte.cc [44] ↗browser-use.com [45] ↗docs.notte.cc [46] ↗docs.browserbase.com [47] ↗docs.browser-use.com [48] ↗docs.notte.cc [49] ↗docs.browserbase.com [50] ↗docs.browser-use.com [51] ↗docs.notte.cc [52] ↗docs.browserbase.com [53] ↗docs.browser-use.com [54] ↗notte.cc [55] ↗docs.browserbase.com [56] ↗docs.notte.cc [57] ↗browser-use.com [58] ↗docs.browserbase.com [59] ↗docs.browser-use.com [60] ↗
Measured performance
BrowserArena is run by Notte, which competes with the providers it measures. Lifecycle covers creating a session, connecting, navigating and releasing it; actions per second comes from a separate throughput test. Each row is the latest run for that provider.
Measured across regions; network distance adds latency. Affected: Browserbase.
| Provider | Lifecycle median | P95 | Success rate | Actions/s | Test setup | Run date |
|---|---|---|---|---|---|---|
| Browserbase | 714 ms[1] | 772 ms[1] | 100% of 100 runs[1] | 3.39[2] | runner us-east-1 -> browsers us-west-2 | 2026-11-02 (lifecycle), 2026-11-01 (throughput) |
| Browser Use Cloud | 392 ms[1] | 488 ms[1] | 100% of 100 runs[1] | 4.04[2] | runner us-east-1 -> browsers us-east-1 | 2026-11-02 (lifecycle), 2026-11-01 (throughput) |
| Notte (for reference) | 317 ms[1] | 442 ms[1] | 100% of 100 runs[1] | 2.65[2] | runner us-west-1 -> browsers us-west-2 | 2026-11-02 (lifecycle), 2026-11-01 (throughput) |
Sources: browserarena.ai [1] ↗browserarena.ai [2] ↗browserarena.ai [3] ↗browserarena.ai [4] ↗github.com [5] ↗
Get started with Browserbase
SDK languages: typescript, python. The snippet below is the official python quickstart from docs.browserbase.com, trimmed.
- typescript: @browserbasehq/sdk[2]
- python: browserbase[3]
- typescript: @browserbasehq/sdk-functions[4]
- typescript: @browserbasehq/stagehand[5]
from playwright.sync_api import Playwright, sync_playwright
from browserbase import Browserbase
import os
bb = Browserbase(api_key=os.environ["BROWSERBASE_API_KEY"])
def run(playwright: Playwright) -> None:
session = bb.sessions.create()
print(
"Session replay URL:", f"https://browserbase.com/sessions/{session.id}"
)
chromium = playwright.chromium
browser = chromium.connect_over_cdp(session.connect_url)
context = browser.contexts[0]
page = context.pages[0]
page.goto("https://browserbase.com/")
page_title = page.title()
print(page_title)
page.close()
browser.close()
print("Done!")
if __name__ == "__main__":
with sync_playwright() as playwright:
run(playwright)
Sources: docs.browserbase.com [1] ↗npmjs.com [2] ↗pypi.org [3] ↗npmjs.com [4] ↗npmjs.com [5] ↗
Get started with Browser Use Cloud
SDK languages: python, typescript. The snippet below is the official python quickstart from docs.browser-use.com, trimmed.
- python: browser-use-sdk[2]
- typescript: browser-use-sdk[3]
- python: browser-use (open-source library, separate API)[4]
from browser_use_sdk.v4 import BrowserUse
from playwright.sync_api import sync_playwright
with BrowserUse() as client:
session = client.browsers.create(proxy_country_code="us")
try:
if not session.cdp_url:
raise RuntimeError("The browser did not return a CDP URL")
with sync_playwright() as p:
browser = p.chromium.connect_over_cdp(session.cdp_url)
context = browser.contexts[0]
page = context.pages[0] if context.pages else context.new_page()
page.goto("https://example.com")
print(page.title())
finally:
client.browsers.stop(session.id)
Sources: docs.browser-use.com [1] ↗pypi.org [2] ↗npmjs.com [3] ↗pypi.org [4] ↗