Anchor Browser vs Kernel
Choose Anchor Browser for authenticated enterprise workflows that need VM-level isolation per browser and managed logins; choose Kernel for agents that need fast, hypervisor-isolated browsers with pay-only-while-active billing. Anchor Browser uses Dedicated VM per browser isolation; Kernel uses Unikernel VM per browser isolation and is open source.
Key differences between Anchor Browser and Kernel
- Isolation: Anchor Browser uses Dedicated VM per browser; Kernel uses Unikernel VM per browser.
- Open source: Kernel is open source (Apache-2.0); Anchor Browser is not.
- Session length: 3 h default, configurable (Anchor Browser) versus Up to 72 h (Kernel).
- SDKs and interfaces: Only Kernel lists Go and CLI.
What they have in common
- Both are hosted platforms.
- Both list Python, TypeScript, REST API and MCP server.
Anchor Browser vs Kernel at a glance
| Attribute | Anchor Browser | Kernel |
|---|---|---|
| What it is | Cloud browsers for agents with a dedicated VM per browser, managed authentication identities, persistent volumes and a Web-Bot-Auth-verified Chromium fork. | 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. |
| Type | Hosted platform | Hosted platform |
| Isolation | Dedicated, isolated virtual machine for each browser instance; browsers are never reused between sessions or customers; hypervisor not named | 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 |
| Open source | No | Yes (Apache-2.0) |
| Self-host / BYOC | Not documented / Yes | Yes / Not documented |
| SDKs | Python, JavaScript/TypeScript, REST API, MCP server | JavaScript/TypeScript, Python, Go, CLI, REST API, MCP server |
| Cold start (vendor claim) | Not documented | 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 |
| Max session | 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 | Timeout defaults to 60 seconds and starts when the browser enters standby (5 seconds after the last client disconnects); configurable up to 72 hours |
| Persistence | Identities 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 SDK | 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 |
| Snapshots / pause | Not documented / Not documented | Yes / Yes |
| GPU | Not documented | Headful browsers with GPU acceleration at $0.0008000016 per second on Start-Up and Enterprise plans |
| Networking | Built-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-Auth | 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 |
| Pricing | 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 | 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 |
| Free tier | Free plan: 5 credits, up to 5 concurrent browsers, up to 500 browser sessions | Free plan: $5 monthly credits, 5 concurrent browsers, 1-day replays; images are free to run yourself |
| Compliance | SOC 2 Type II, ISO 27001, HIPAA (BAA) and GDPR listed; Zero Data Retention mode; browser session data not stored by design | 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 |
| Regions | AWS us-east-2 (Ohio) by default; EU residency in AWS eu-central-1 (Frankfurt) on Growth; custom regions on Enterprise | us-east (default), eu-west, ap-southeast; region selection on Start-Up and Enterprise plans |
| Company headquarters | Not documented | San Francisco, California, United States |
| Good fit for | Authenticated enterprise workflows that need VM-level isolation per browser and managed logins | Agents that need fast, hypervisor-isolated browsers with pay-only-while-active billing |
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 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
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
- 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
Both are worth piloting with your own image and region. See the full Anchor Browser profile and Kernel profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Anchor Browser or Kernel better for AI agents?
What is the difference between Anchor Browser and Kernel?
Which is open source, Anchor Browser or Kernel?
How do Anchor Browser and Kernel isolate code?
How does Anchor Browser pricing compare with Kernel?
Do Anchor Browser and Kernel support GPUs?
Can you self-host Anchor Browser or Kernel?
How long can sessions run on Anchor Browser and Kernel?
Do Anchor Browser and Kernel 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). Anchor Browser vs Kernel. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/anchor-browser-vs-kernel/