Browser platforms / Notte alternative

A Notte browser alternative

Notte combines browser sessions, saved browser profiles, session-owned file storage and serverless browser Functions. These features retain useful state, but have different scope from a complete Linux computer. Compare the automation service and its current credit/rate conditions with the persistent execution environment beneath your own agent.

Start buildingCompare capabilities ↓

Reviewed 2026-10-19 · Published by the Sandbox0 team

When Notte fits

Notte fits managed browser automation with browser controls, profiles, personas, credential services, Functions and schedules. Its SDK file service can retrieve session downloads after a session ends, so persistent artifact access is a genuine feature to account for.

When to consider Sandbox0

Consider Sandbox0 when compatible agent tools, system configuration and accumulated data need one growing durable RootFS and supported paused file operations. Browser identity, managed automation, scheduling and model/provider integration still require an application or retained Notte services.

Capabilities

Notte and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeNottePublic plan maximum session durations are 15, 120 and 300 minutes for Free, Developer and Startup; Enterprise terms differ.View evidence ↗Sandbox0ttl and hard_ttl default to 0 (disabled). Configure idle pause and deletion policies for the same persistent sandbox identity; an idle running sandbox still accrues compute charges.Read documentation →
Persistent filesNotteSession-file retrieval and browser profiles are established, but a general-purpose durable root disk is not.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSNotteProfiles explicitly save selected browser storage; complete Linux RootFS persistence is not established.View evidence ↗Sandbox0Persistence extends beyond /workspace to paths such as /usr/local, /etc, and /home. Runtime tmpfs and virtual filesystems are excluded.Read documentation →
Release compute, keep stateNotteStopping/reconnecting browser sessions is not evidence of a compute-free arbitrary-machine checkpoint.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateNotteA browser profile is selected serialized state, not verified arbitrary execution memory.View evidence ↗Sandbox0Experimental memory checkpoints can preserve compatible process state. Use memory: true on both pause and resume on a compatible deployment. A filesystem checkpoint alone does not preserve running processes.Read documentation →

Online RootFS growth

On growth-enabled images, Sandbox0 automatically expands the writable RootFS as free space runs low, within a configured sparse logical ceiling up to 64 TiB. Agent processes keep running. Growth is enabled in the qualified Cloud region; confirm activation for other regions. Existing images and snapshots retain their captured storage geometry. The ceiling is logical capacity, not preallocated host disk.

Notte profiles and session-file storage preserve browser identity and artifacts, not a verified complete writable Linux RootFS growth contract. Function deployment and a larger browser-session allowance do not themselves establish automatic online expansion of the agent’s installed system.

Files while compute is paused

Sandbox0's Files API reads persistent files without resuming compute. Filesystem-only pauses also permit edits; retained-memory pauses are read-only and reject mutations with 409. SSH, SFTP, file watching, and runtime-only mounts require running compute.

The File Storage guide explicitly shows retrieving downloads after a browser Session ends. That is real post-session artifact access. It does not establish arbitrary paused Linux RootFS edits; Sandbox0 supports those filesystem-only paused mutations while protecting memory checkpoints.

See paused file operations →

A profile captures selected browser state

Notte profiles preserve cookies, localStorage and sessionStorage. The profile guide excludes HTTP cache, history and extensions, and sessions start fresh unless given a profile. Saving browser identity is useful for returning workflows, but does not establish persistence of installed operating-system tools or arbitrary process memory.

Source 1 ↗

File storage and Functions add capabilities beyond a profile

File Storage manages session-owned uploads/downloads and documents listing/downloading after the Session context ends. Functions deploy browser scripts behind API calls, schedules and events. Retain those artifact and orchestration functions in a replacement design, while verifying retention terms separately from the live browser lifetime.

Source 1 ↗Source 2 ↗

Current public pricing and its documentation export differ

The public price page says Notte-managed LLM tokens have no Notte markup and lists Startup bring-your-own proxy bandwidth at $0.20/GB. The official full documentation export instead lists Developer/Startup token markups and a $3/GB net custom-proxy fee after credit. It also specifies minute-ceiling browser billing while the public page defers to billing policy. Confirm effective tenant terms before estimating an invoice.

Source 1 ↗Source 2 ↗

Pricing

Compare billing models, then price your workload

CPU allocation, memory, billing minimums, disk, plan fees, and supported workload differ. These meters are not equal-performance machine quotes. Confirm region, resource units, and included allowances before estimating a total.

Notte

Pricing reviewed 2026-10-19

Browser sessions
$0.01 per browser-hour
Rounded according to the effective billing policy.
Rate source ↗
Browser Functions
$0.05 per function-hour
Function runtime is a separate meter from browser sessions.
Rate source ↗
Developer
$20/month including $20 monthly credits
25 browser concurrency; 120-minute maximum session duration.
Rate source ↗
Startup
$100/month including $100 monthly credits
100 browser concurrency; 300-minute maximum session duration.
Rate source ↗
Residential proxy
$10 per GB
The current public page lists Startup bring-your-own proxy bandwidth at $0.20/GB; the full documentation export still describes a $3/GB net fee after credit. Confirm effective billing.
Rate source ↗
Free
$10 one-time credits on a $0 plan
Non-expiring grant; 15-minute maximum session duration.
Rate source ↗

Monthly subscription credits expire each cycle; purchased top-ups and the free grant do not. Credits cover multiple services, so they are not guaranteed browser hours. Managed-token markup, bring-your-own proxy fees and exact time rounding differ between the public pricing page and the full documentation export; verify the account policy before forecasting.

Check current Notte pricing ↗

Sandbox0

$0.015/GiB-hour compute (billed by the second at approximately $0.000004167/GiB-second), plus $0.02/GiB-month of retained incremental RootFS and memory checkpoint data. Shared base images and platform recovery retention are excluded; paused sandboxes accrue storage charges only.

Compute / GiB-hour
$0.015
Retained data / GiB-month
$0.02
Paused compute
$0.00

A 4 GiB agent, 100 running hours

$6.00 compute

4 GiB × 100 hours, billed by the second. Keeping 20 GiB of billable incremental data for a full billing month adds $0.40. CPU is derived from memory by the platform; choose a tier that fits your workload.

Understand storage billing →

Before migrating from Notte

  1. Export needed session files, saved browser profiles and Function definitions, recording credentials, schedule and retention dependencies through supported account workflows.
  2. Port compatible agent/browser code to Sandbox0 and retain or rebuild profiles, file transport, Functions, schedules and provider integrations deliberately.
  3. Test login and artifact continuity, system-tool retention, RootFS growth, paused files and a bill using the effective browser/function/proxy/token policies.

Common questions

Is Sandbox0 a drop-in Notte replacement?

Evaluate API compatibility and product scope. These products serve different core workflows, so a change may require a different architecture.

Does keeping files also keep a running agent?

Filesystem state and volatile process state are separate. Sandbox0 requires explicit compatible memory checkpoints to preserve running processes; its default filesystem resume starts fresh processes.

Sources and review scope

The Boat team's Battleships directory is the discovery source. References below describe the product and plan discussed on this page. Check current availability, regional terms and billing units before migrating. Where the cited material does not establish a capability or price, the comparison identifies that uncertainty.

Battleships research record ↗docs.notte.cc/features/sessions/browser-profiles ↗docs.notte.cc/concepts/file-storage ↗docs.notte.cc/concepts/functions ↗www.notte.cc/pricing ↗docs.notte.cc/llms-full.txt ↗docs.notte.cc/features/sessions/lifecycle ↗Sandbox0 RootFS capacity →

Related comparisons

Airtop vs Sandbox0 →Anchor Browser vs Sandbox0 →Bright Data Browser API vs Sandbox0 →Browser Use Cloud vs Sandbox0 →BrowserAct vs Sandbox0 →Browserbase vs Sandbox0 →