Agent Sandboxesagentsandboxes.org
Head-to-head

Anchor Browser vs Notte

Answer in brief

Choose Anchor Browser for authenticated enterprise workflows that need VM-level isolation per browser and managed logins; choose Notte for agents that need cheap browser sessions with credential vaults and synthetic identities for sign-ups and logins. Anchor Browser uses Dedicated VM per browser isolation; Notte uses Isolated browser instance isolation and is open source.

By the Agent Sandboxes editors · Updated

Key differences between Anchor Browser and Notte

  • Isolation: Anchor Browser uses Dedicated VM per browser; Notte uses Isolated browser instance.
  • Open source: Notte is open source (SSPL-1.0); Anchor Browser is not.
  • Session length: 3 h default, configurable (Anchor Browser) versus 15 min to 5 h by plan (Notte).
  • SDKs and interfaces: Only Notte lists CLI.

What they have in common

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

Anchor Browser vs Notte at a glance

AttributeAnchor BrowserNotte
What it isCloud browsers for agents with a dedicated VM per browser, managed authentication identities, persistent volumes and a Web-Bot-Auth-verified Chromium fork.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
IsolationDedicated, isolated virtual machine for each browser instance; browsers are never reused between sessions or customers; hypervisor 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 / YesNot documented / Not documented
SDKsPython, JavaScript/TypeScript, REST API, MCP serverPython, JavaScript/TypeScript, CLI, REST API, MCP server
Cold start (vendor claim)Not documentedNot documented
Max sessionDefault max_duration 180 minutes and idle_timeout 5 minutes, both configurable per session; no documented upper bound on max_duration; idle timeout can be disabledmax_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)
PersistenceIdentities store credentials, MFA methods and the browser profile from the last sign-in so sessions start logged in; Volumes are team-owned folders that outlive sessions for uploads and downloads; profiles via SDKProfiles 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
NetworkingBuilt-in "Anchor VPN" rather than third-party proxies; custom proxies and geolocation selection on paid plans; automated captcha bypass; Cloudflare-verified browser agents; Web-Bot-AuthResidential 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
PricingCredit plans: Free $0 (5 credits, up to 5 concurrent, up to 500 sessions); Starter $50/month (50 credits, 25 concurrent); Team $500/month (500 credits, 50 concurrent); Growth $2,000/month (2,000 credits, 200 concurrent); Enterprise custom (500+ concurrent). Overage $1.00 per credit; 0.1 credits per completed task. Calculator lists browser duration $0.09/hour, proxy $8/GB, AI steps $0.01Browser 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 credits, up to 5 concurrent browsers, up to 500 browser sessionsFree plan: $10 credits granted once with no expiry, 5 concurrent browsers, 15-minute sessions, 5 vaults and 5 personas
ComplianceSOC 2 Type II, ISO 27001, HIPAA (BAA) and GDPR listed; Zero Data Retention mode; browser session data not stored by designSOC 2 Type II; HIPAA and on-premise deployment on Enterprise
RegionsAWS us-east-2 (Ohio) by default; EU residency in AWS eu-central-1 (Frankfurt) on Growth; custom regions on EnterpriseNot documented
Company headquartersNot documentedSan Francisco, California, United States
Good fit forAuthenticated enterprise workflows that need VM-level isolation per browser and managed loginsAgents 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 Anchor Browser

  • You need a dedicated VM per browser that is never reused
  • You want managed logins with MFA handled for you
  • You need audited compliance (SOC 2 Type II, ISO 27001, HIPAA, GDPR) and EU residency
  • You want to deploy into your own cloud or on-premise

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

  • Anchor Browser: Pricing is in credits; the pricing calculator lists browser duration at $0.09 per hour
  • Anchor Browser: The pricing page lists SOC 2 Type II, ISO 27001 and GDPR on the $2,000/month Growth plan, and HIPAA with a BAA on Enterprise
  • 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 Anchor Browser profile and Notte profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Anchor Browser or Notte better for AI agents?
Neither is better for every workload. Anchor Browser suits authenticated enterprise workflows that need VM-level isolation per browser and managed logins. Notte suits agents that need cheap browser sessions with credential vaults and synthetic identities for sign-ups and logins.
What is the difference between Anchor Browser and Notte?
Anchor Browser uses Dedicated VM per browser; Notte uses Isolated browser instance. Notte is open source (SSPL-1.0); Anchor Browser is not. Session length: 3 h default, configurable (Anchor Browser) versus 15 min to 5 h by plan (Notte). Only Notte lists CLI.
Which is open source, Anchor Browser or Notte?
Anchor Browser is not open source; Notte is open source (SSPL-1.0).
How do Anchor Browser and Notte isolate code?
Anchor Browser: Dedicated, isolated virtual machine for each browser instance; browsers are never reused between sessions or customers; hypervisor not named. Notte: Sessions are described as isolated browser instances running in the cloud; the container or VM boundary is not named.
How does Anchor Browser pricing compare with Notte?
Anchor Browser: Credit plans: Free $0 (5 credits, up to 5 concurrent, up to 500 sessions); Starter $50/month (50 credits, 25 concurrent); Team $500/month (500 credits, 50 concurrent); Growth $2,000/month (2,000 credits, 200 concurrent); Enterprise custom (500+ concurrent). Overage $1.00 per credit; 0.1 credits per completed task. Calculator lists browser duration $0.09/hour, proxy $8/GB, AI steps $0.01. 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 Anchor Browser and Notte pricing pages before deciding.
How long can sessions run on Anchor Browser and Notte?
Anchor Browser: Default max_duration 180 minutes and idle_timeout 5 minutes, both configurable per session; no documented upper bound on max_duration; idle timeout can be disabled. 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. anchorbrowser.io
  2. anchorbrowser.io/#pricing
  3. docs.anchorbrowser.io/introduction
  4. docs.anchorbrowser.io/security.md
  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). Anchor Browser vs Notte. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/anchor-browser-vs-notte/