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: Steel $0.08 (Scale) to $0.10 (Launch); Browser Use Cloud $0.02. The Pricing section shows each rate as published.[1][2]
- Free tier - Steel: Launch plan: $0 per month plus usage, with $30 in one-time free usage credits valid for 90 days. 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.[1][3]
- Highest concurrency on self-serve plans: Steel 100 (Scale); Browser Use Cloud 1000 (Pay as you go, Tier 4 ($25,000 total paid)).[1][3]
- Longest session on self-serve plans: Steel 1 hour (Scale); Browser Use Cloud 4 hours (Free (Tier 0)).[1][3]
- Regions: Steel lists 1 region; Browser Use Cloud lists 2 regions (selectable).[4][5]
- Self-hosting: Steel Yes; Browser Use Cloud Enterprise.[6][7]
- Open source: Steel lists Apache-2.0 at github.com/steel-dev/steel-browser; Browser Use Cloud lists MIT at github.com/browser-use/browser-use.[8][9]
Sources: docs.steel.dev [1] ↗docs.browser-use.com [2] ↗browser-use.com [3] ↗docs.steel.dev [4] ↗docs.browser-use.com [5] ↗docs.steel.dev [6] ↗browser-use.com [7] ↗raw.githubusercontent.com [8] ↗raw.githubusercontent.com [9] ↗
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 | Steel | Browser Use Cloud | Notte (publisher) |
|---|---|---|---|
| Billing unit | per browser hour, billed by the minute and rounded up[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 | Launch plan: $0 per month plus usage, with $30 in one-time free usage credits valid for 90 days[1] | $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 | Scale ($250/mo)[1] | Pay as you go, Tier 1 ($100 total paid)[4] | Developer ($20/mo)[3] |
| Browser-hour rate (self-serve plans) | $0.08 (Scale) to $0.10 (Launch)[1] | $0.02[4][2] | $0.01[3] |
| Rate as published (entry paid plan) | $0.08/hour[1] | $0.02/browser-hour plus traffic; no subscription[4] | $20/mo including $20 credits per month; usage then $0.01 / hour of browser sessions from credits[3] |
| Included browser hours (entry paid plan) | Not published | Not published | Not published |
| Proxy per GB (entry paid plan) | $6[1] | $5[4] | $10[3] |
| Proxy pricing | 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.[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.[5] |
| CAPTCHA pricing | $3 per 1,000 solves on Launch, $1 per 1,000 solves on Scale, custom on Enterprise[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.[6] | Included on Free, Developer and Startup (no per-solve charge listed); Enterprise row says Targeted[3] |
| All plans | Launch $0; Scale $250/mo; Enterprise custom[1] | 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[7] | Free $0; Developer $20/mo; Startup $100/mo; Enterprise custom[3] |
Sources: docs.steel.dev [1] ↗browser-use.com [2] ↗notte.cc [3] ↗docs.browser-use.com [4] ↗docs.notte.cc [5] ↗browser-use.com [6] ↗browser-use.com [7] ↗
Limits
| Item | Steel | Browser Use Cloud | Notte (publisher) |
|---|---|---|---|
| Max session duration | 15 minutes on Launch, 1 hour on Scale, up to 24 hours on Enterprise[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 | 5 minutes[1] | 60 minutes (standalone browser timeout parameter, range 1-240 minutes)[4] | 15 minutes (max_duration_minutes default)[5] |
| Idle timeout | 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.[1] | 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.[6] | Default 3 minutes, configurable from 1 to 30 minutes; each operation resets it[5] |
| Max concurrency | 10 on Launch, 100 on Scale, 1,000+ on Enterprise[7] | 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.[8] | Browsers: 5 Free, 25 Developer, 100 Startup, Custom Enterprise. Agents and functions: 5, 25, 100, Custom.[3] |
| Highest concurrency on self-serve plans | 100 (Scale)[7] | 1000 (Pay as you go, Tier 4 ($25,000 total paid))[8] | 100 (Startup)[3] |
| Session creation rate limit | Not published | 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.[6] | 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-east[10] | US (default, api.browser-use.com), EU (Frankfurt, Germany; api.eu.browser-use.com) (selectable)[11] | Not published |
| Data retention (entry paid plan) | 14 days[7] | Not published | Not published |
Sources: docs.steel.dev [1] ↗docs.browser-use.com [2] ↗notte.cc [3] ↗docs.browser-use.com [4] ↗docs.notte.cc [5] ↗docs.browser-use.com [6] ↗docs.steel.dev [7] ↗browser-use.com [8] ↗docs.notte.cc [9] ↗docs.steel.dev [10] ↗docs.browser-use.com [11] ↗
Features
| Feature | Group | Steel | 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 | Beta[13] | Yes[14] | Yes[15] |
| Managed login | Login and state | Beta[13] | Unknown | Yes[16] |
| TOTP and 2FA handling | Login and state | Beta[13] | Yes[17] | Yes[18] |
| CAPTCHA solving | Anti-bot and network | Yes[19] | Yes[20] | Yes[21] |
| Stealth and fingerprinting | Anti-bot and network | Yes[22] | 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[23] | 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[31] | Yes[32] |
| Human takeover | Observe and control | Yes[33] | Yes[34] | Yes[32] |
| Session recording | Observe and control | Yes[35] | Yes[31] | Yes[36] |
| Network logs | Observe and control | Yes[37] | Unknown | Yes[38] |
| File downloads | Files and extensions | Yes[39] | Yes[8] | Yes[40] |
| File uploads | Files and extensions | Yes[39] | Yes[41] | Yes[40] |
| Browser extensions | Files and extensions | Beta[42] | Yes[43] | No[44] |
| Serverless functions | Run code and agents | Unknown | Unknown | Yes[45] |
| Scheduling | Run code and agents | Unknown | Yes[46] | Yes[47] |
| Webhooks | Run code and agents | Unknown | Yes[48] | Yes[49] |
| MCP server | Run code and agents | Yes[50] | Yes[51] | Yes[52] |
| Hosted agent API | Run code and agents | Unknown | Yes[53] | Yes[54] |
| Scrape and fetch API | Run code and agents | Yes[55] | Unknown | Yes[56] |
| Self-hosting | Deployment | Yes[57] | Enterprise[58] | Enterprise[54] |
| Region selection | Deployment | Unknown | Yes[59] | Unknown |
Sources (59)
steel.dev [1] ↗browser-use.com [2] ↗docs.notte.cc [3] ↗docs.steel.dev [4] ↗docs.steel.dev [5] ↗docs.notte.cc [6] ↗docs.steel.dev [7] ↗docs.browser-use.com [8] ↗docs.notte.cc [9] ↗docs.steel.dev [10] ↗docs.browser-use.com [11] ↗docs.notte.cc [12] ↗docs.steel.dev [13] ↗docs.browser-use.com [14] ↗docs.notte.cc [15] ↗docs.notte.cc [16] ↗docs.browser-use.com [17] ↗docs.notte.cc [18] ↗docs.steel.dev [19] ↗docs.browser-use.com [20] ↗docs.notte.cc [21] ↗docs.steel.dev [22] ↗docs.browser-use.com [23] ↗docs.notte.cc [24] ↗docs.steel.dev [25] ↗docs.browser-use.com [26] ↗docs.notte.cc [27] ↗docs.steel.dev [28] ↗browser-use.com [29] ↗docs.notte.cc [30] ↗docs.browser-use.com [31] ↗docs.notte.cc [32] ↗docs.steel.dev [33] ↗docs.browser-use.com [34] ↗docs.steel.dev [35] ↗docs.notte.cc [36] ↗docs.steel.dev [37] ↗docs.notte.cc [38] ↗docs.steel.dev [39] ↗docs.notte.cc [40] ↗docs.browser-use.com [41] ↗docs.steel.dev [42] ↗docs.browser-use.com [43] ↗docs.notte.cc [44] ↗docs.notte.cc [45] ↗browser-use.com [46] ↗docs.notte.cc [47] ↗docs.browser-use.com [48] ↗docs.notte.cc [49] ↗raw.githubusercontent.com [50] ↗docs.browser-use.com [51] ↗docs.notte.cc [52] ↗docs.browser-use.com [53] ↗notte.cc [54] ↗docs.steel.dev [55] ↗docs.notte.cc [56] ↗docs.steel.dev [57] ↗browser-use.com [58] ↗docs.browser-use.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.
| Provider | Lifecycle median | P95 | Success rate | Actions/s | Test setup | Run date |
|---|---|---|---|---|---|---|
| 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) |
| 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 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] ↗
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] ↗