Agent Sandboxesagentsandboxes.org
Head-to-head

Notte vs Steel

Answer in brief

Choose Notte for agents that need cheap browser sessions with credential vaults and synthetic identities for sign-ups and logins; choose Steel for teams that want an open-source browser API they can run themselves or scale on a managed cloud. Notte uses Isolated browser instance isolation and is open source; Steel uses Isolated Chromium session isolation and is open source.

By the Agent Sandboxes editors · Updated

Key differences between Notte and Steel

  • Isolation: Notte uses Isolated browser instance; Steel uses Isolated Chromium session.
  • Licence: Notte is SSPL-1.0; Steel is Apache-2.0.
  • Session length: 15 min to 5 h by plan (Notte) versus 15 min / 1 h / 24 h (Steel).
  • SDKs and interfaces: Only Steel lists Go and Rust.

What they have in common

  • Both are hosted platforms.
  • Both are open source.
  • Both list Python, TypeScript, CLI, REST API and MCP server.

Notte vs Steel at a glance

AttributeNotteSteel
What it isCloud browser sessions at $0.01 per hour with stealth, proxies, profiles, secret vaults and personas, a hosted MCP server and serverless browser functions; SSPL-licensed core.Open-source browser API for agents (Apache-2.0, self-hostable with Docker) with a managed Steel Cloud adding stealth, captcha solving, profiles and a hosted MCP server.
TypeHosted platformHosted platform
IsolationSessions are described as isolated browser instances running in the cloud; the container or VM boundary is not namedEach session launches its own isolated Chromium in the cloud; the container or VM boundary is not named. Self-hosted Steel Browser runs as a Docker container
Open sourceYes (SSPL-1.0)Yes (Apache-2.0)
Self-host / BYOCNot documented / Not documentedYes / Not documented
SDKsPython, JavaScript/TypeScript, CLI, REST API, MCP serverPython, JavaScript/TypeScript, Go, Rust, CLI, REST API, MCP server
Cold start (vendor claim)Not documentedNot documented
Max sessionmax_duration_minutes defaults to 15 (API maximum 1,440) with an idle timeout of 3 minutes (max 30); plan caps are 15 minutes (Free), 120 minutes (Developer), 300 minutes (Startup), custom (Enterprise)Sessions last 5 minutes by default (configurable timeout, optional inactivityTimeout); maximum 15 minutes on Launch, 1 hour on Scale, up to 24 hours on Enterprise
PersistenceProfiles snapshot cookies, local storage and session storage (not cache, history or extensions) and reload with persist true/false; vaults hold credentials that are never forwarded to LLMs; personas provide email, phone and 2FA identitiesEach session keeps its own cookies and storage; Profiles snapshot the browser user data directory (cookies, auth, extensions, settings) for reuse via profileId, up to 300 MB, deleted after 30 days unused
Snapshots / pauseNot documented / Not documentedNot documented / Not documented
GPUNot documentedNo — not offered
NetworkingResidential proxies at $10/GB, bring your own at $0.20/GB on Startup; captcha solving and anti-detection; secret proxies keep real credential values away from the browserResidential and datacenter proxies with country-to-city targeting or bring your own; dedicated IPs ($5/IP/month on Scale); captcha solving; stealth fingerprinting and an Enterprise-only Stealth Browser Chromium fork
PricingBrowser sessions $0.01 per hour; browser functions $0.05 per hour; residential proxy $10/GB; LLM tokens at cost. Free $0: $10 one-time credits, 5 concurrent, 15-minute sessions. Developer $20/month: $20 credits, 25 concurrent, 120-minute sessions. Startup $100/month: $100 credits, 100 concurrent, 300-minute sessions, BYO keys and proxy. Enterprise: custom, SSO, SLAs, HIPAA, on-premiseLaunch $0 + usage: $0.10 per browser hour, 10 concurrent sessions, proxy $10/GB, captcha $3 per 1k. Scale $250/month + usage: $100 credits/month, $0.08 per browser hour, 100 concurrent, proxy $6/GB, captcha $1 per 1k. Enterprise: custom, 1,000+ concurrent. Billed per minute, rounded up
Free tierFree plan: $10 credits granted once with no expiry, 5 concurrent browsers, 15-minute sessions, 5 vaults and 5 personas$30 one-time credits on the Launch plan (no monthly fee, no card required); Steel Browser is free to self-host
ComplianceSOC 2 Type II; HIPAA and on-premise deployment on EnterpriseHIPAA-ready BAA listed on the pricing page for Scale and Enterprise; a trust centre is published behind an access request
RegionsNot documentedNot documented
Company headquartersSan Francisco, California, United StatesNot documented
Good fit forAgents that need cheap browser sessions with credential vaults and synthetic identities for sign-ups and loginsTeams that want an open-source browser API they can run themselves or scale on a managed cloud

Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose Notte

  • You want the lowest listed browser-hour price with a no-expiry free credit
  • You need vaults and personas for sign-ups, logins and 2FA
  • You want a hosted MCP server with profiles and auth tools
  • You want to schedule automations as serverless browser functions

Reasons to choose Steel

  • You want an Apache-2.0 browser server you can self-host with Docker
  • You need a managed cloud with the same API when concurrency grows
  • You want SDKs beyond Node and Python (Go and Rust)
  • You are connecting an MCP client and want a hosted server with profiles and saved logins

Trade-offs to check first

  • Notte: Isolation boundary and regions are not documented
  • Notte: Free and Developer sessions cap at 15 and 120 minutes
  • Steel: Launch plan sessions are capped at 15 minutes; 24-hour sessions need Enterprise
  • Steel: The isolation boundary is not documented; cloud browsers run in a single region (us-east)

Both are worth piloting with your own image and region. See the full Notte profile and Steel profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Notte or Steel better for AI agents?
Neither is better for every workload. Notte suits agents that need cheap browser sessions with credential vaults and synthetic identities for sign-ups and logins. Steel suits teams that want an open-source browser API they can run themselves or scale on a managed cloud.
What is the difference between Notte and Steel?
Notte uses Isolated browser instance; Steel uses Isolated Chromium session. Notte is licensed SSPL-1.0; Steel is licensed Apache-2.0. Session length: 15 min to 5 h by plan (Notte) versus 15 min / 1 h / 24 h (Steel). Only Steel lists Go and Rust.
Which is open source, Notte or Steel?
Both are open source (Notte: SSPL-1.0; Steel: Apache-2.0).
How do Notte and Steel isolate code?
Notte: Sessions are described as isolated browser instances running in the cloud; the container or VM boundary is not named. Steel: Each session launches its own isolated Chromium in the cloud; the container or VM boundary is not named. Self-hosted Steel Browser runs as a Docker container.
How does Notte pricing compare with Steel?
Notte: Browser sessions $0.01 per hour; browser functions $0.05 per hour; residential proxy $10/GB; LLM tokens at cost. Free $0: $10 one-time credits, 5 concurrent, 15-minute sessions. Developer $20/month: $20 credits, 25 concurrent, 120-minute sessions. Startup $100/month: $100 credits, 100 concurrent, 300-minute sessions, BYO keys and proxy. Enterprise: custom, SSO, SLAs, HIPAA, on-premise. Steel: Launch $0 + usage: $0.10 per browser hour, 10 concurrent sessions, proxy $10/GB, captcha $3 per 1k. Scale $250/month + usage: $100 credits/month, $0.08 per browser hour, 100 concurrent, proxy $6/GB, captcha $1 per 1k. Enterprise: custom, 1,000+ concurrent. Billed per minute, rounded up. Rates change, so check the Notte and Steel pricing pages before deciding.
Can you self-host Notte or Steel?
Notte: not documented. Steel: yes.
How long can sessions run on Notte and Steel?
Notte: max_duration_minutes defaults to 15 (API maximum 1,440) with an idle timeout of 3 minutes (max 30); plan caps are 15 minutes (Free), 120 minutes (Developer), 300 minutes (Startup), custom (Enterprise). Steel: Sessions last 5 minutes by default (configurable timeout, optional inactivityTimeout); maximum 15 minutes on Launch, 1 hour on Scale, up to 24 hours on Enterprise.

Sources

  1. notte.cc
  2. notte.cc/pricing
  3. github.com/nottelabs/notte
  4. docs.notte.cc/concepts/sessions.md
  5. steel.dev
  6. steel.dev/pricing
  7. steel.dev/faq
  8. github.com/steel-dev/steel-browser

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

Agent Sandboxes. (2026). Notte vs Steel. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/notte-vs-steel/