Agent Sandboxesagentsandboxes.org
Head-to-head

Hyperbrowser vs Steel

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 Steel for teams that want an open-source browser API they can run themselves or scale on a managed cloud. Hyperbrowser uses Isolated browser instance isolation; Steel uses Isolated Chromium session isolation and is open source.

By the Agent Sandboxes editors · Updated

Key differences between Hyperbrowser and Steel

  • Isolation: Hyperbrowser uses Isolated browser instance; Steel uses Isolated Chromium session.
  • Open source: Steel is open source (Apache-2.0); Hyperbrowser is not.
  • Session length: Up to 12 h (Hyperbrowser) 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 list Python, TypeScript, CLI, REST API and MCP server.

Hyperbrowser vs Steel at a glance

AttributeHyperbrowserSteel
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.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 boundary is not named. The separate Sandboxes product states commands run in isolated virtual machinesEach 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 sourceNoYes (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)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 stopSessions 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 the user data directory (cookies, local storage, session storage, cache) and reload it in later sessions; persistChanges controls writes; profiles.fork() copies a profileEach 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 documented for browsers; GPU (CUDA) sandboxes exist in the separate Sandboxes productNo — not offered
NetworkingResidential proxies at $10/GB with country/state/city selection or custom proxies; captcha solving; basic and ultra stealth modesResidential 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
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+ concurrentLaunch $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: 5,000 credits (about 50 browser hours at base rate), 1 concurrent session, 7-day retention$30 one-time credits on the Launch plan (no monthly fee, no card required); Steel Browser is free to self-host
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 otherwiseHIPAA-ready BAA listed on the pricing page for Scale and Enterprise; a trust centre is published behind an access request
Regionsus-central, us-east, us-west, europe-west; asia-south on Enterprise/Select plansNot documented
Company headquartersSan Francisco, California, United StatesNot documented
Good fit forAgents that need cheap browser hours with a built-in path to run computer-use models as one-shot tasksTeams 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 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 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

  • 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
  • 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 Hyperbrowser profile and Steel profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Hyperbrowser or Steel 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. 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 Hyperbrowser and Steel?
Hyperbrowser uses Isolated browser instance; Steel uses Isolated Chromium session. Steel is open source (Apache-2.0); Hyperbrowser is not. Session length: Up to 12 h (Hyperbrowser) versus 15 min / 1 h / 24 h (Steel). Only Steel lists Go and Rust.
Which is open source, Hyperbrowser or Steel?
Hyperbrowser is not open source; Steel is open source (Apache-2.0).
How do Hyperbrowser and Steel 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. 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 Hyperbrowser pricing compare with Steel?
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. 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 Hyperbrowser and Steel pricing pages before deciding.
Can you self-host Hyperbrowser or Steel?
Hyperbrowser: not documented. Steel: yes.
How long can sessions run on Hyperbrowser and Steel?
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. 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. hyperbrowser.ai
  2. hyperbrowser.ai/pricing
  3. hyperbrowser.ai/security
  4. hyperbrowser.ai/docs
  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). Hyperbrowser vs Steel. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/hyperbrowser-vs-steel/