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); Steel $0.08 (Scale) to $0.10 (Launch). 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. Steel: Launch plan: $0 per month plus usage, with $30 in one-time free usage credits valid for 90 days.[3][2]
- Longest session on self-serve plans: Browserbase 6 hours (Developer); Steel 1 hour (Scale).[1][2]
- Regions: Browserbase lists 4 regions (selectable); Steel lists 1 region.[4][5]
- Self-hosting: Browserbase No; Steel Yes.[3][6]
- Open source: Browserbase lists MIT at github.com/browserbase/stagehand (Stagehand automation framework, SDKs and MCP server only; the hosted browser infrastructure is closed source); Steel lists Apache-2.0 at github.com/steel-dev/steel-browser.[7][8]
Sources: docs.browserbase.com [1] ↗docs.steel.dev [2] ↗browserbase.com [3] ↗docs.browserbase.com [4] ↗docs.steel.dev [5] ↗docs.steel.dev [6] ↗github.com [7] ↗raw.githubusercontent.com [8] ↗
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 | Steel | 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] | per browser hour, billed by the minute and rounded up[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] | Launch plan: $0 per month plus usage, with $30 in one-time free usage credits valid for 90 days[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] | Scale ($250/mo)[2] | Developer ($20/mo)[3] |
| Browser-hour rate (self-serve plans) | $0.10 (Startup) to $0.12 (Developer)[1] | $0.08 (Scale) to $0.10 (Launch)[2] | $0.01[3] |
| Rate as published (entry paid plan) | then $0.12/browser hr[1] | $0.08/hour[2] | $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] | $6[2] | $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] | Steel-managed residential proxies: $10 per GB on Launch, $6 per GB on Scale, custom on Enterprise. On Launch, Steel-provided proxies require a $10 paid-balance deposit.[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.[5] |
| CAPTCHA pricing | No separate meter listed. Auto captcha solving is included on Developer, Startup and Scale plans and listed as No on Free.[1] | $3 per 1,000 solves on Launch, $1 per 1,000 solves on Scale, custom on Enterprise[2] | 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] | Launch $0; Scale $250/mo; Enterprise custom[2] | Free $0; Developer $20/mo; Startup $100/mo; Enterprise custom[3] |
Sources: docs.browserbase.com [1] ↗docs.steel.dev [2] ↗notte.cc [3] ↗browserbase.com [4] ↗docs.notte.cc [5] ↗
Limits
| Item | Browserbase | Steel | Notte (publisher) |
|---|---|---|---|
| Max session duration | 6 hours[1] | 15 minutes on Launch, 1 hour on Scale, up to 24 hours on Enterprise[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 | 5 minutes[2] | 15 minutes (max_duration_minutes default)[4] |
| 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.[5] | Optional inactivityTimeout (milliseconds): releases the session early once it sees no CDP command or remote input for that long. Off by default; it has no effect if it is greater than or equal to timeout.[2] | Default 3 minutes, configurable from 1 to 30 minutes; each operation resets it[4] |
| Max concurrency | Per plan: Free 3, Developer 25, Startup 100, Scale 250+. Assigned at the organization level and split across projects.[6] | 10 on Launch, 100 on Scale, 1,000+ on Enterprise[7] | 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)[8] | 100 (Scale)[7] | 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.[6] | Not published | 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.[9] |
| Regions | us-west-2, us-east-1, eu-central-1, ap-southeast-1 (selectable)[10] | us-east[11] | Not published |
| Data retention (entry paid plan) | Not published | 14 days[7] | Not published |
Sources: docs.browserbase.com [1] ↗docs.steel.dev [2] ↗notte.cc [3] ↗docs.notte.cc [4] ↗docs.browserbase.com [5] ↗docs.browserbase.com [6] ↗docs.steel.dev [7] ↗docs.browserbase.com [8] ↗docs.notte.cc [9] ↗docs.browserbase.com [10] ↗docs.steel.dev [11] ↗
Features
| Feature | Group | Browserbase | Steel | Notte (publisher) |
|---|---|---|---|---|
| Connect over CDP | Connect | Yes[1] | Yes[2] | Yes[3] |
| Playwright | Connect | Yes[4] | Yes[5] | Yes[3] |
| Puppeteer | Connect | Yes[6] | Yes[7] | Yes[8] |
| Selenium | Connect | Yes[9] | Yes[10] | Yes[11] |
| Persistent profiles | Login and state | Yes[12] | Yes[13] | Yes[14] |
| Credential vault | Login and state | Yes[15] | Beta[16] | Yes[17] |
| Managed login | Login and state | Unknown | Beta[16] | Yes[18] |
| TOTP and 2FA handling | Login and state | Unknown | Beta[16] | Yes[19] |
| CAPTCHA solving | Anti-bot and network | Yes[20] | Yes[21] | Yes[22] |
| Stealth and fingerprinting | Anti-bot and network | Yes[4] | Yes[23] | Yes[24] |
| Managed proxies | Anti-bot and network | Yes[25] | Yes[26] | Yes[27] |
| Proxy geo-targeting | Anti-bot and network | Yes[25] | Yes[26] | Yes[27] |
| Bring your own proxy | Anti-bot and network | Yes[25] | Yes[26] | Yes[27] |
| Live view | Observe and control | Yes[28] | Yes[29] | Yes[30] |
| Embeddable live view | Observe and control | Yes[28] | Yes[29] | Yes[31] |
| Human takeover | Observe and control | Yes[28] | Yes[32] | Yes[31] |
| Session recording | Observe and control | Yes[33] | Yes[34] | Yes[35] |
| Network logs | Observe and control | Yes[33] | Yes[36] | Yes[37] |
| File downloads | Files and extensions | Yes[38] | Yes[39] | Yes[40] |
| File uploads | Files and extensions | Yes[41] | Yes[39] | Yes[40] |
| Browser extensions | Files and extensions | Yes[42] | Beta[43] | No[44] |
| Serverless functions | Run code and agents | Yes[45] | Unknown | Yes[46] |
| Scheduling | Run code and agents | Unknown | Unknown | Yes[47] |
| Webhooks | Run code and agents | Yes[48] | Unknown | Yes[49] |
| MCP server | Run code and agents | Yes[50] | Yes[51] | Yes[52] |
| Hosted agent API | Run code and agents | Yes[53] | Unknown | Yes[54] |
| Scrape and fetch API | Run code and agents | Yes[55] | Yes[56] | Yes[57] |
| Self-hosting | Deployment | No[4] | Yes[58] | Enterprise[54] |
| Region selection | Deployment | Yes[59] | Unknown | Unknown |
Sources (59)
docs.browserbase.com [1] ↗steel.dev [2] ↗docs.notte.cc [3] ↗browserbase.com [4] ↗docs.steel.dev [5] ↗docs.browserbase.com [6] ↗docs.steel.dev [7] ↗docs.notte.cc [8] ↗docs.browserbase.com [9] ↗docs.steel.dev [10] ↗docs.notte.cc [11] ↗docs.browserbase.com [12] ↗docs.steel.dev [13] ↗docs.notte.cc [14] ↗docs.browserbase.com [15] ↗docs.steel.dev [16] ↗docs.notte.cc [17] ↗docs.notte.cc [18] ↗docs.notte.cc [19] ↗docs.browserbase.com [20] ↗docs.steel.dev [21] ↗docs.notte.cc [22] ↗docs.steel.dev [23] ↗docs.notte.cc [24] ↗docs.browserbase.com [25] ↗docs.steel.dev [26] ↗docs.notte.cc [27] ↗docs.browserbase.com [28] ↗docs.steel.dev [29] ↗docs.notte.cc [30] ↗docs.notte.cc [31] ↗docs.steel.dev [32] ↗docs.browserbase.com [33] ↗docs.steel.dev [34] ↗docs.notte.cc [35] ↗docs.steel.dev [36] ↗docs.notte.cc [37] ↗docs.browserbase.com [38] ↗docs.steel.dev [39] ↗docs.notte.cc [40] ↗docs.browserbase.com [41] ↗docs.browserbase.com [42] ↗docs.steel.dev [43] ↗docs.notte.cc [44] ↗docs.browserbase.com [45] ↗docs.notte.cc [46] ↗docs.notte.cc [47] ↗docs.browserbase.com [48] ↗docs.notte.cc [49] ↗docs.browserbase.com [50] ↗raw.githubusercontent.com [51] ↗docs.notte.cc [52] ↗docs.browserbase.com [53] ↗notte.cc [54] ↗docs.browserbase.com [55] ↗docs.steel.dev [56] ↗docs.notte.cc [57] ↗docs.steel.dev [58] ↗docs.browserbase.com [59] ↗
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) |
| Steel | 1192 ms[1] | 2111 ms[1] | 97% of 100 runs[1] | 3.35[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 Steel
SDK languages: python, typescript, go, rust. The snippet below is the official python quickstart from github.com, trimmed.
import os
from playwright.sync_api import sync_playwright
from steel import Steel
STEEL_API_KEY = os.getenv('STEEL_API_KEY')
client = Steel(steel_api_key=STEEL_API_KEY)
session = None
try:
session = client.sessions.create()
playwright = sync_playwright().start()
browser = playwright.chromium.connect_over_cdp(
f"{session.websocket_url}&apiKey={STEEL_API_KEY}"
)
currentContext = browser.contexts[0]
page = currentContext.new_page()
page.goto("https://news.ycombinator.com", wait_until="networkidle")
finally:
if session:
client.sessions.release(session.id)
Sources: github.com [1] ↗pypi.org [2] ↗npmjs.com [3] ↗github.com [4] ↗github.com [5] ↗