Skip to main content

comparison / Checked 2026-11-02

Notte vs Steel

Notte and Steel compared on pricing, limits, features and measured performance, with every figure linked to the provider's documentation.

Key differences

  • Browser-hour rate on self-serve plans: Notte $0.01; Steel $0.08 (Scale) to $0.10 (Launch). The Pricing section shows each rate as published.[1][2]
  • Free tier - Notte: $10 credits granted once with no expiry; 5 concurrent browsers; 15-minute sessions; no card required. Steel: Launch plan: $0 per month plus usage, with $30 in one-time free usage credits valid for 90 days.[1][2]
  • Longest session on self-serve plans: Notte 5 hours (Startup); Steel 1 hour (Scale).[1][2]
  • Managed login: Notte Yes; Steel Beta.[3][4]
  • Self-hosting: Notte Enterprise; Steel Yes.[1][5]
  • Open source: Notte lists SSPL-1.0 (Server Side Public License v1) at github.com/nottelabs/notte (The core library (local browser sessions and scraping) only; the hosted API service (stealth sessions, functions, vaults and personas) is not open source); Steel lists Apache-2.0 at github.com/steel-dev/steel-browser.[6][7]

Sources: notte.cc [1] ↗docs.steel.dev [2] ↗docs.notte.cc [3] ↗docs.steel.dev [4] ↗docs.steel.dev [5] ↗github.com [6] ↗raw.githubusercontent.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.

ItemNotteSteel
Billing unitDollar-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[1]per browser hour, billed by the minute and rounded up[2]
Free tier$10 credits granted once with no expiry; 5 concurrent browsers; 15-minute sessions; no card required[1]Launch plan: $0 per month plus usage, with $30 in one-time free usage credits valid for 90 days[2]
Entry paid planDeveloper ($20/mo)[1]Scale ($250/mo)[2]
Browser-hour rate (self-serve plans)$0.01[1]$0.08 (Scale) to $0.10 (Launch)[2]
Rate as published (entry paid plan)$20/mo including $20 credits per month; usage then $0.01 / hour of browser sessions from credits[1]$0.08/hour[2]
Included browser hours (entry paid plan)Not publishedNot published
Proxy per GB (entry paid plan)$10[1]$6[2]
Proxy pricingBuilt-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.[3]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]
CAPTCHA pricingIncluded on Free, Developer and Startup (no per-solve charge listed); Enterprise row says Targeted[1]$3 per 1,000 solves on Launch, $1 per 1,000 solves on Scale, custom on Enterprise[2]
All plansFree $0; Developer $20/mo; Startup $100/mo; Enterprise custom[1]Launch $0; Scale $250/mo; Enterprise custom[2]

Sources: notte.cc [1] ↗docs.steel.dev [2] ↗docs.notte.cc [3] ↗

Limits

ItemNotteSteel
Max session durationPer 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.[1]15 minutes on Launch, 1 hour on Scale, up to 24 hours on Enterprise[2]
Default session timeout15 minutes (max_duration_minutes default)[3]5 minutes[2]
Idle timeoutDefault 3 minutes, configurable from 1 to 30 minutes; each operation resets it[3]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]
Max concurrencyBrowsers: 5 Free, 25 Developer, 100 Startup, Custom Enterprise. Agents and functions: 5, 25, 100, Custom.[1]10 on Launch, 100 on Scale, 1,000+ on Enterprise[4]
Highest concurrency on self-serve plans100 (Startup)[1]100 (Scale)[4]
Session creation rate limitRate 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.[5]Not published
RegionsNot publishedus-east[6]
Data retention (entry paid plan)Not published14 days[4]

Sources: notte.cc [1] ↗docs.steel.dev [2] ↗docs.notte.cc [3] ↗docs.steel.dev [4] ↗docs.notte.cc [5] ↗docs.steel.dev [6] ↗

Features

FeatureGroupNotteSteel
Connect over CDPConnectYes[1]Yes[2]
PlaywrightConnectYes[1]Yes[3]
PuppeteerConnectYes[4]Yes[5]
SeleniumConnectYes[6]Yes[7]
Persistent profilesLogin and stateYes[8]Yes[9]
Credential vaultLogin and stateYes[10]Beta[11]
Managed loginLogin and stateYes[12]Beta[11]
TOTP and 2FA handlingLogin and stateYes[13]Beta[11]
CAPTCHA solvingAnti-bot and networkYes[14]Yes[15]
Stealth and fingerprintingAnti-bot and networkYes[16]Yes[17]
Managed proxiesAnti-bot and networkYes[18]Yes[19]
Proxy geo-targetingAnti-bot and networkYes[18]Yes[19]
Bring your own proxyAnti-bot and networkYes[18]Yes[19]
Live viewObserve and controlYes[20]Yes[21]
Embeddable live viewObserve and controlYes[22]Yes[21]
Human takeoverObserve and controlYes[22]Yes[23]
Session recordingObserve and controlYes[24]Yes[25]
Network logsObserve and controlYes[26]Yes[27]
File downloadsFiles and extensionsYes[28]Yes[29]
File uploadsFiles and extensionsYes[28]Yes[29]
Browser extensionsFiles and extensionsNo[30]Beta[31]
Serverless functionsRun code and agentsYes[32]Unknown
SchedulingRun code and agentsYes[33]Unknown
WebhooksRun code and agentsYes[34]Unknown
MCP serverRun code and agentsYes[35]Yes[36]
Hosted agent APIRun code and agentsYes[37]Unknown
Scrape and fetch APIRun code and agentsYes[38]Yes[39]
Self-hostingDeploymentEnterprise[37]Yes[40]
Region selectionDeploymentUnknownUnknown
Sources (40)

docs.notte.cc [1] ↗steel.dev [2] ↗docs.steel.dev [3] ↗docs.notte.cc [4] ↗docs.steel.dev [5] ↗docs.notte.cc [6] ↗docs.steel.dev [7] ↗docs.notte.cc [8] ↗docs.steel.dev [9] ↗docs.notte.cc [10] ↗docs.steel.dev [11] ↗docs.notte.cc [12] ↗docs.notte.cc [13] ↗docs.notte.cc [14] ↗docs.steel.dev [15] ↗docs.notte.cc [16] ↗docs.steel.dev [17] ↗docs.notte.cc [18] ↗docs.steel.dev [19] ↗docs.notte.cc [20] ↗docs.steel.dev [21] ↗docs.notte.cc [22] ↗docs.steel.dev [23] ↗docs.notte.cc [24] ↗docs.steel.dev [25] ↗docs.notte.cc [26] ↗docs.steel.dev [27] ↗docs.notte.cc [28] ↗docs.steel.dev [29] ↗docs.notte.cc [30] ↗docs.steel.dev [31] ↗docs.notte.cc [32] ↗docs.notte.cc [33] ↗docs.notte.cc [34] ↗docs.notte.cc [35] ↗raw.githubusercontent.com [36] ↗notte.cc [37] ↗docs.notte.cc [38] ↗docs.steel.dev [39] ↗docs.steel.dev [40] ↗

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.

ProviderLifecycle medianP95Success rateActions/sTest setupRun date
Notte317 ms[1]442 ms[1]100% of 100 runs[1]2.65[2]runner us-west-1 -> browsers us-west-22026-11-02 (lifecycle), 2026-11-01 (throughput)
Steel1192 ms[1]2111 ms[1]97% of 100 runs[1]3.35[2]runner us-east-1 -> browsers us-east-12026-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 Notte

SDK languages: python, typescript. The snippet below is the official python quickstart from docs.notte.cc, trimmed.

  • python: notte-sdk[2]
  • typescript: notte-sdk[3]
  • python: notte (open-source core: local sessions and scraping)[4]
python From Notte docs
import os

from notte_sdk import NotteClient
from playwright.sync_api import sync_playwright

client = NotteClient()

with client.Session(idle_timeout_minutes=2) as session:
    cdp_url = session.cdp_url()

    with sync_playwright() as p:
        browser = p.chromium.connect_over_cdp(cdp_url)
        try:
            page = browser.contexts[0].pages[0]
            page.goto("https://www.google.com")
            page.screenshot(path=os.environ.get("NOTTE_SCREENSHOT_PATH", "screenshot.png"))
        finally:
            browser.close()

Sources: docs.notte.cc [1] ↗pypi.org [2] ↗npmjs.com [3] ↗pypi.org [4] ↗

Get started with Steel

SDK languages: python, typescript, go, rust. The snippet below is the official python quickstart from github.com, trimmed.

  • python: steel-sdk[2]
  • typescript: steel-sdk[3]
  • go: github.com/steel-dev/steel-go[4]
  • rust: steel-rs[5]
python From Steel docs
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] ↗

Keep comparing

Put the workflow to the test.

Try Notte Read the quickstart ↗