Kernel vs Steel
Choose Kernel for agents that need fast, hypervisor-isolated browsers with pay-only-while-active billing; choose Steel for teams that want an open-source browser API they can run themselves or scale on a managed cloud. Kernel uses Unikernel VM per browser isolation and is open source; Steel uses Isolated Chromium session isolation and is open source.
Key differences between Kernel and Steel
- Isolation: Kernel uses Unikernel VM per browser; Steel uses Isolated Chromium session.
- Session length: Up to 72 h (Kernel) versus 15 min / 1 h / 24 h (Steel).
- SDKs and interfaces: Only Steel lists Rust.
What they have in common
- Both are hosted platforms.
- Both are open source.
- Both can be self-hosted.
- Both list TypeScript, Python, Go, CLI, REST API and MCP server.
Kernel vs Steel at a glance
| Attribute | Kernel | Steel |
|---|---|---|
| What it is | Browsers for agents where each Chromium runs in its own Unikraft unikernel VM, with standby that stops billing, profiles, and open-source images under Apache-2.0. | 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. |
| Type | Hosted platform | Hosted platform |
| Isolation | Each browser runs in a dedicated Unikraft-based unikernel VM, isolated at the hypervisor level with no shared host kernel; hypervisor not named in the docs | 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 |
| Open source | Yes (Apache-2.0) | Yes (Apache-2.0) |
| Self-host / BYOC | Yes / Not documented | Yes / Not documented |
| SDKs | JavaScript/TypeScript, Python, Go, CLI, REST API, MCP server | Python, JavaScript/TypeScript, Go, Rust, CLI, REST API, MCP server |
| Cold start (vendor claim) | Docs state a browser is created in about 30 ms at p50 and 105 ms at p99; the unikernels page claims cold starts under 20 ms | Not documented |
| Max session | Timeout defaults to 60 seconds and starts when the browser enters standby (5 seconds after the last client disconnects); configurable up to 72 hours | 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 |
| Persistence | Standby keeps browser state without billing until a client reconnects; Profiles capture the user data directory (cookies, auth, local storage, tabs) and are saved with save_changes; encrypted per organisation | Each 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 / pause | Yes / Yes | Not documented / Not documented |
| GPU | Headful browsers with GPU acceleration at $0.0008000016 per second on Start-Up and Enterprise plans | No — not offered |
| Networking | Managed residential proxy and captcha solver in stealth mode; configurable and bring-your-own proxies on higher plans; egress allowlists cover browser traffic through the proxy | Residential 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 |
| Pricing | Usage per second: headless $0.0000166667/s, headful $0.0001333336/s, headful + GPU $0.0008000016/s; standby and idle pool browsers are not billed. Plans: Free $0 + usage ($5 credits, 5 concurrent), Hobbyist $30/month ($10 credits, 10 concurrent), Start-Up $200/month ($50 credits, 150 concurrent, regions, GPU), Enterprise custom | 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 |
| Free tier | Free plan: $5 monthly credits, 5 concurrent browsers, 1-day replays; images are free to run yourself | $30 one-time credits on the Launch plan (no monthly fee, no card required); Steel Browser is free to self-host |
| Compliance | SOC 2 Type II (report on request); HIPAA; PCI DSS Level 4 (SAQ A); ISO 27001 and GDPR listed as in progress; zero data retention on Enterprise | HIPAA-ready BAA listed on the pricing page for Scale and Enterprise; a trust centre is published behind an access request |
| Regions | us-east (default), eu-west, ap-southeast; region selection on Start-Up and Enterprise plans | Not documented |
| Company headquarters | San Francisco, California, United States | Not documented |
| Good fit for | Agents that need fast, hypervisor-isolated browsers with pay-only-while-active billing | Teams 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 Kernel
- You want each browser in its own VM without paying for idle time
- You need long-lived browsers (up to 72 hours) that survive client disconnects
- You want to inspect or run the browser images yourself
- You need GPU-accelerated headful browsers or regional placement
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
- Kernel: The docs do not say which hypervisor the cloud uses; the unikernel build in kernel-images deploys to Unikraft Cloud, while the Docker image runs locally
- Kernel: Region selection, GPU and BYO proxies require the $200/month Start-Up plan
- 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 Kernel profile and Steel profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Kernel or Steel better for AI agents?
What is the difference between Kernel and Steel?
Which is open source, Kernel or Steel?
How do Kernel and Steel isolate code?
How does Kernel pricing compare with Steel?
Do Kernel and Steel support GPUs?
Can you self-host Kernel or Steel?
How long can sessions run on Kernel and Steel?
Do Kernel and Steel support snapshots or pause and resume?
Sources
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). Kernel vs Steel. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/kernel-vs-steel/