Agent Sandboxesagentsandboxes.org
Head-to-head

Hyperbrowser vs Notte

Answer in brief

Choose Hyperbrowser for agents that need cheap browser hours with a built-in path to run computer-use models as one-shot tasks; choose Notte for agents that need cheap browser sessions with credential vaults and synthetic identities for sign-ups and logins. Hyperbrowser uses Isolated browser instance isolation; Notte uses Isolated browser instance isolation and is open source.

By the Agent Sandboxes editors · Updated

Key differences between Hyperbrowser and Notte

  • Open source: Notte is open source (SSPL-1.0); Hyperbrowser is not.
  • Session length: Up to 12 h (Hyperbrowser) versus 15 min to 5 h by plan (Notte).

What they have in common

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

Hyperbrowser vs Notte at a glance

AttributeHyperbrowserNotte
What it isCredit-billed cloud Chrome sessions with profiles, stealth and captcha solving, plus one-shot agent runs (Claude Computer Use, OpenAI CUA, Browser Use) and separate VM-based code sandboxes.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
IsolationSessions are described as isolated browser instances running in the cloud; the boundary is not named. The separate Sandboxes product states commands run in isolated virtual machinesSessions 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, CLI, REST API, MCP serverPython, JavaScript/TypeScript, CLI, REST API, MCP server
Cold start (vendor claim)Homepage claims under 500 ms from request to a ready browserNot documented
Max sessionTeam default timeout (configurable in settings); per-session timeoutMinutes from 1 to 720 (12 hours); keepAlive keeps a session running after CDP disconnect until timeout or stopmax_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 snapshot the user data directory (cookies, local storage, session storage, cache) and reload it in later sessions; persistChanges controls writes; profiles.fork() copies a profileProfiles 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 documented for browsers; GPU (CUDA) sandboxes exist in the separate Sandboxes productNot documented
NetworkingResidential proxies at $10/GB with country/state/city selection or custom proxies; captcha solving; basic and ultra stealth modesResidential 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
PricingCredits, 1,000 credits = $1. Browser $0.10/hour, proxy $10/GB, sandboxes $0.045/vCPU-hour + $0.015/GiB-hour, HyperAgent/Browser Use $0.02/step. Free: 5,000 credits, 1 concurrent. Startup $30/month: 30,000 credits, 25 concurrent. Scale $100/month: 100,000 credits, 100 concurrent. Enterprise: custom, 1,000+ concurrentBrowser 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 tierFree plan: 5,000 credits (about 50 browser hours at base rate), 1 concurrent session, 7-day retentionFree plan: $10 credits granted once with no expiry, 5 concurrent browsers, 15-minute sessions, 5 vaults and 5 personas
ComplianceSecurity programme aligned with SOC 2 Trust Services Criteria with independent assessments; the trust centre lists a SOC 2 Type 1 report on request; production data stored in US cloud databases unless agreed otherwiseSOC 2 Type II; HIPAA and on-premise deployment on Enterprise
Regionsus-central, us-east, us-west, europe-west; asia-south on Enterprise/Select plansNot documented
Company headquartersSan Francisco, California, United StatesSan Francisco, California, United States
Good fit forAgents that need cheap browser hours with a built-in path to run computer-use models as one-shot tasksAgents 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 Hyperbrowser

  • You want low per-hour browser pricing with a usable free tier
  • You need to run Claude Computer Use, OpenAI CUA or Browser Use as a hosted task
  • You want profiles that persist logins and can be forked
  • You need a European or Asian region

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

  • Hyperbrowser: Isolation boundary for browsers is not documented
  • Hyperbrowser: The security page states alignment with SOC 2 criteria; the trust centre lists a SOC 2 Type 1 report on request
  • 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 Hyperbrowser profile and Notte profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Hyperbrowser or Notte better for AI agents?
Neither is better for every workload. Hyperbrowser suits agents that need cheap browser hours with a built-in path to run computer-use models as one-shot tasks. Notte suits agents that need cheap browser sessions with credential vaults and synthetic identities for sign-ups and logins.
What is the difference between Hyperbrowser and Notte?
Notte is open source (SSPL-1.0); Hyperbrowser is not. Session length: Up to 12 h (Hyperbrowser) versus 15 min to 5 h by plan (Notte).
Which is open source, Hyperbrowser or Notte?
Hyperbrowser is not open source; Notte is open source (SSPL-1.0).
How do Hyperbrowser and Notte isolate code?
Hyperbrowser: Sessions are described as isolated browser instances running in the cloud; the boundary is not named. The separate Sandboxes product states commands run in isolated virtual machines. Notte: Sessions are described as isolated browser instances running in the cloud; the container or VM boundary is not named.
How does Hyperbrowser pricing compare with Notte?
Hyperbrowser: Credits, 1,000 credits = $1. Browser $0.10/hour, proxy $10/GB, sandboxes $0.045/vCPU-hour + $0.015/GiB-hour, HyperAgent/Browser Use $0.02/step. Free: 5,000 credits, 1 concurrent. Startup $30/month: 30,000 credits, 25 concurrent. Scale $100/month: 100,000 credits, 100 concurrent. Enterprise: custom, 1,000+ concurrent. 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 Hyperbrowser and Notte pricing pages before deciding.
How long can sessions run on Hyperbrowser and Notte?
Hyperbrowser: Team default timeout (configurable in settings); per-session timeoutMinutes from 1 to 720 (12 hours); keepAlive keeps a session running after CDP disconnect until timeout or stop. 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. hyperbrowser.ai
  2. hyperbrowser.ai/pricing
  3. hyperbrowser.ai/security
  4. hyperbrowser.ai/docs
  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). Hyperbrowser vs Notte. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/hyperbrowser-vs-notte/