Hyperbeam
Embeddable hosted virtual computers (Chromium browsers, plus Android and console emulators on request) created by REST API and streamed into web apps for multi-user control. A co-browsing embed product rather than an agent sandbox; usable for agent-plus-human browsing but lacking the automation hooks of agent-focused browser services.
Overview
Hyperbeam provides "virtual computers" that developers embed in their own websites and apps. A POST to the REST API starts a Chromium browser session (Android and NES emulators are available on request) and returns an embed_url for the @hyperbeam/web client, plus an admin_token that unlocks programmatic navigation and permission control. Sessions are tuned at creation with resolution (up to 1920x1080), frame rate (24 to 60), kiosk mode, extensions, locale, search engine and region (NA, EU or AS). The product grew out of a consumer watch-party platform and is built around multi-user streaming with synchronised audio and video.
Timeouts are configurable per session: an absolute cap, an inactivity cap and an offline cap (default one hour with no connected users), with webhooks for timeout warnings. Chrome profiles can be persisted to encrypted S3 storage and reloaded by session ID. The home page advertises 10,000 free minutes a month and pay-as-you-go at $0.007 per minute thereafter. Hyperbeam does not market itself for AI agents and documents no server-side screenshot, mouse or keyboard API, CDP endpoint or Playwright connection; the isolation technology is not described.
Notable
- 10,000 free minutes per month, then $0.007 per participant-minute with automatic volume discounts (home page)
- Sessions default to no absolute time limit; the offline timeout defaults to 3,600 seconds
- Persisted browser profiles are deleted after three months without access
Hyperbeam specifications
| Attribute | Details |
|---|---|
| Isolation | Not documented; the vendor calls each session a "virtual computer" and the REST endpoint is /vm, but no hypervisor or container runtime is named |
| Deployment | Hosted platform |
| Open source | No |
| SDKs and interfaces | REST API, JavaScript/TypeScript, Unity |
| Cold start (vendor claim) | Not documented |
| Max session length | No absolute limit by default: timeout.absolute and timeout.inactive default to null; timeout.offline (no connected users) defaults to 3,600 s |
| Persistence | Optional Chrome profile persistence (bookmarks, history, cookies, passwords) stored encrypted in S3 and reloaded by session ID; unused profiles expire after three months |
| GPU | Home page mentions "custom-built servers made for GPU-intensive workloads" for WebGL; webgl is a per-session flag |
| Networking | Outbound internet from the hosted browser; regions NA, EU and AS selectable per session; no proxy or domain-filtering options documented |
| Pricing | Pay as you go after a free allowance; the home-page estimator shows $0.007 per participant-minute with automatic volume discounts and custom pricing at high volume |
| Free tier | 10,000 free minutes every month, no credit card required (home page) |
| Compliance | Not documented |
| Regions | NA (default), EU and AS |
Facts from Hyperbeam’s public documentation, verified November 9, 2026. Performance numbers are vendor claims.
Strengths and trade-offs
Strengths
- You want to embed a streamed browser in your own product that humans and an agent can share
- You need EU or Asia hosting and fine control over resolution, frame rate and timeouts
- You are prototyping and want a large monthly free allowance
Trade-offs
- Not positioned for AI agents: no documented server-side computer-use actions, CDP or Playwright access
- Isolation technology and compliance attestations are not documented
- Browser only by default; Android and console emulators require access requests
Good fit for: Products that embed a shared, streamed browser for users, where an agent may also drive it through the client SDK.
How Hyperbeam compares
| Sandbox | Isolation | Open source | Self-host / BYOC | Cold start (vendor) | Max session | Snapshots / pause | GPU | SDKs |
|---|---|---|---|---|---|---|---|---|
| Hyperbeam | Not documented | No | No / No | Not documented | Unlimited by default | No / No | Not documented | REST API, JavaScript/TypeScript, Unity |
| Browserbase | Isolated Chromium session | No | No / No | <2 s (claim) | 6 h (15 min Free) | No / No | No | Python, JavaScript/TypeScript, REST API, MCP server |
| Steel | Isolated Chromium session | Yes | Yes / No | Not documented | 15 min / 1 h / 24 h | No / No | No | Python, JavaScript/TypeScript, Go, Rust, CLI, REST API, MCP server |
| Browserless | Not documented | Yes | Yes / No | Not documented | 2 min to 60 min by plan | No / No | Yes | JavaScript/TypeScript, Python, CLI, REST API, MCP server |
| Hyperbrowser | Isolated browser instance | No | No / No | <500 ms (claim) | Up to 12 h | No / No | No | Python, JavaScript/TypeScript, CLI, REST API, MCP server |
| Anchor Browser | Dedicated VM per browser | No | No / Yes | Not documented | 3 h default, configurable | No / No | No | Python, JavaScript/TypeScript, REST API, MCP server |
| Kasm Workspaces | Docker container | No | Yes / No | Not documented | Admin-defined | No / Not documented | Yes | REST API |
Frequently asked questions
What is Hyperbeam?
How does Hyperbeam isolate code?
Is Hyperbeam open source?
How much does Hyperbeam cost?
What are the alternatives to Hyperbeam?
Sources
Cite this page
Agent Sandboxes. (2026). Hyperbeam. agentsandboxes.org. Last reviewed November 9, 2026. https://agentsandboxes.org/sandboxes/hyperbeam/
Found an error or a missing sandbox? Submit a correction — every entry links to the sources it relies on.