Agent Sandboxesagentsandboxes.org
Head-to-head

Browser Use Cloud vs Notte

Answer in brief

Choose Browser Use Cloud for cheap stealth browser hours for agents built on the Browser Use library or any CDP client; choose Notte for agents that need cheap browser sessions with credential vaults and synthetic identities for sign-ups and logins. Browser Use Cloud uses Isolated browser per run isolation; Notte uses Isolated browser instance isolation and is open source.

By the Agent Sandboxes editors · Updated

Key differences between Browser Use Cloud and Notte

  • Isolation: Browser Use Cloud uses Isolated browser per run; Notte uses Isolated browser instance.
  • Open source: Notte is open source (SSPL-1.0); Browser Use Cloud is not.
  • Session length: 1 h default, 4 h max (Browser Use Cloud) versus 15 min to 5 h by plan (Notte).
  • SDKs and interfaces: Only Notte lists CLI and MCP server.

What they have in common

  • Both companies are based in the United States.
  • Both are hosted platforms.
  • Both list Python, TypeScript and REST API.

Browser Use Cloud vs Notte at a glance

AttributeBrowser Use CloudNotte
What it isStealth cloud Chromium at $0.06 per browser hour from the makers of the MIT-licensed Browser Use agent library, with profiles, live view, an EU deployment and a hosted agent API.Cloud 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.
TypeHosted platformHosted platform
IsolationEvery run gets its own isolated session (a browser, a proxy exit and a model context); the container or VM boundary is not namedSessions are described as isolated browser instances running in the cloud; the container or VM boundary is not named
Open sourceNoYes (SSPL-1.0)
Self-host / BYOCNot documented / Not documentedNot documented / Not documented
SDKsPython, JavaScript/TypeScript, REST APIPython, JavaScript/TypeScript, CLI, REST API, MCP server
Cold start (vendor claim)Not documentedNot documented
Max sessionStandalone browser sessions default to 60 minutes with a maximum of 240 minutes; V4 agent browsers stop about 2 minutes after the last run (keepAlive 120 to 14,400 seconds) with a hard cap of 4 hoursmax_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)
PersistenceProfiles persist cookies, local storage and login state across browsers via profileId; local logins can be synced into a cloud profile; recording is off by defaultProfiles 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 identities
Snapshots / pauseNot documented / Not documentedNot documented / Not documented
GPUNot documentedNot documented
NetworkingManaged home-IP proxies ($5/GB) with country selection, or your own proxy or direct connection ($0.20/GB); captcha solving included; network policies allow or block domainsResidential 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 browser
PricingPay as you go, $0/month: browsers $0.06 per browser hour billed by the minute (1-minute minimum); home-IP proxy $5/GB; own proxy or direct $0.20/GB; bu-ultrafast agent $0.006 per median task. Concurrency unlocks by lifetime spend: 10 at $0, 50 at $100, 250 at $1,000, 500 at $5,000, 1,000 at $25,000. Enterprise: customBrowser 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
Free tier$1 sign-up credit, one per person, never expires; credits top up from $5Free plan: $10 credits granted once with no expiry, 5 concurrent browsers, 15-minute sessions, 5 vaults and 5 personas
ComplianceSOC 2 Type II (audit period 17 July to 17 October 2025); HIPAA on enterprise plans (not on the EU deployment); signed DPA; zero data retention projectsSOC 2 Type II; HIPAA and on-premise deployment on Enterprise
RegionsUS by default; EU deployment in Frankfurt (AWS) with its own API base URL and keysNot documented
Company headquartersSan Francisco, California, United StatesSan Francisco, California, United States
Good fit forCheap stealth browser hours for agents built on the Browser Use library or any CDP clientAgents that need cheap browser sessions with credential vaults and synthetic identities for sign-ups and logins

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 Browser Use Cloud

  • You want browser hours billed by the minute at a listed $0.06 per hour
  • You already use the Browser Use library and want its default cloud browser
  • You need EU-resident browser runs
  • You want captcha solving and residential proxies without a monthly fee

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

Trade-offs to check first

  • Browser Use Cloud: Isolation boundary is not documented
  • Browser Use Cloud: Sessions cap at 4 hours
  • Notte: Isolation boundary and regions are not documented
  • Notte: Free and Developer sessions cap at 15 and 120 minutes

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

More comparisons

Frequently asked questions

Is Browser Use Cloud or Notte better for AI agents?
Neither is better for every workload. Browser Use Cloud suits cheap stealth browser hours for agents built on the Browser Use library or any CDP client. Notte suits agents that need cheap browser sessions with credential vaults and synthetic identities for sign-ups and logins.
What is the difference between Browser Use Cloud and Notte?
Browser Use Cloud uses Isolated browser per run; Notte uses Isolated browser instance. Notte is open source (SSPL-1.0); Browser Use Cloud is not. Session length: 1 h default, 4 h max (Browser Use Cloud) versus 15 min to 5 h by plan (Notte). Only Notte lists CLI and MCP server.
Which is open source, Browser Use Cloud or Notte?
Browser Use Cloud is not open source; Notte is open source (SSPL-1.0).
How do Browser Use Cloud and Notte isolate code?
Browser Use Cloud: Every run gets its own isolated session (a browser, a proxy exit and a model context); the container or VM boundary is not named. Notte: Sessions are described as isolated browser instances running in the cloud; the container or VM boundary is not named.
How does Browser Use Cloud pricing compare with Notte?
Browser Use Cloud: Pay as you go, $0/month: browsers $0.06 per browser hour billed by the minute (1-minute minimum); home-IP proxy $5/GB; own proxy or direct $0.20/GB; bu-ultrafast agent $0.006 per median task. Concurrency unlocks by lifetime spend: 10 at $0, 50 at $100, 250 at $1,000, 500 at $5,000, 1,000 at $25,000. Enterprise: custom. 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. Rates change, so check the Browser Use Cloud and Notte pricing pages before deciding.
How long can sessions run on Browser Use Cloud and Notte?
Browser Use Cloud: Standalone browser sessions default to 60 minutes with a maximum of 240 minutes; V4 agent browsers stop about 2 minutes after the last run (keepAlive 120 to 14,400 seconds) with a hard cap of 4 hours. 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).

Sources

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

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). Browser Use Cloud vs Notte. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/browser-use-cloud-vs-notte/