Notte vs Kernel: fast browsers, but then what?
Kernel and Notte compared on pricing, features, and what each platform includes beyond the browser runtime. Where Kernel's VM isolation and per-second billing genuinely win. Numbers as of May 2026.
Kernel is solid infrastructure. Fast instance launches, per-VM isolation via Firecracker, per-second billing. They raised $22M, they're trusted by Cash App and Framer, and they've been shipping steadily: Managed Auth, an App Platform, GPU acceleration in preview.
A year ago the pitch was "Kernel is 3.4x faster than Browserbase." The public Browser Arena leaderboard (open-source, 100 sequential runs per provider, May 2026) currently shows Kernel at 341ms and Notte at 394ms. Kernel is still the fastest provider on the board, but the gap between the top three has compressed to tens of milliseconds, not multiples. Browser Arena is maintained by Notte Labs but is open-source and reproducible.
The speed story is mostly settled. What matters more now is what each platform ships beyond the browser runtime.
What Kernel has shipped recently
Managed Auth handles credentials without exposing them to LLMs. Same concept as Notte's vaults: you store credentials, the platform applies them in the browser, the secret stays out of the prompt. Managed Auth requires the Hobbyist tier ($30/mo); on Notte, vaults are available on all tiers.
The App Platform lets you deploy TypeScript or Python code co-located with the browser. Similar to Notte Functions, but Kernel runs your code in the same VM as the browser (zero network hop), while Notte runs it in the same datacenter with a small hop between function and session. For latency-sensitive co-located compute, Kernel's architecture is tighter.
Session replay is on Hobbyist+ with 7-day retention (30 days on Startup at $200/mo). Free-tier users get live view only.
What Notte includes that Kernel doesn't
Personas. If a workflow needs to sign up for something, receive a verification email, or handle an SMS code, Notte handles it inside the session with managed identities that have real inboxes and phone numbers. Kernel has nothing equivalent. Building persona infrastructure yourself is a deeper project than it sounds: you need email hosting, phone number provisioning, verification code parsing, and session coordination.
Structured extraction. Notte's scrape API returns typed objects in a single call. Kernel gives you a browser. Getting clean, typed data out of a page is your problem to solve.
Hybrid workflows. When a site changes layout midstream, pure scripts break. Notte runs deterministic steps as code and falls back to AI reasoning only when the page deviates from the expected structure. Kernel doesn't operate at that layer because it's a browser runtime, not a workflow engine.
CLI integration with AI editors. Kernel's CLI covers infrastructure: deploy apps, invoke actions, manage sessions. Notte's CLI does the same, but also works as a skill inside Claude Code, Cursor, and Windsurf. Same tool for ops and development.
Pricing
Now the cost side. Per-hour rates are close enough that the real differences are in tier gating. All prices from public pricing pages as of May 2026.
| Notte | Kernel | |
|---|---|---|
| Browser time | $0.05/hr | $0.06/hr |
| Billing granularity | Per minute, 1-min minimum | Per minute, 1-min minimum |
| Free tier | 100 hrs lifetime, 5 concurrent | $5/mo credits, 5 concurrent |
| Entry paid tier | Developer $20/mo | Hobbyist $30/mo |
| Mid tier | Startup $100/mo | Startup $200/mo |
| CAPTCHA solving | All tiers | All tiers |
| Advanced stealth | Paid tiers | Free tier |
| Residential proxies | $10/GB, all paid tiers | Default proxy free, geotargeting Hobbyist+ |
| Session replays | All tiers | Hobbyist+ (7-day retention) |
| Managed credentials | All tiers (Vault) | Hobbyist+ (Managed Auth) |
| Compliance | Enterprise only | SOC 2 + HIPAA on Enterprise |
Per-hour cost is close: $0.05 vs $0.06. Both bill per minute with a 1-minute minimum, so the billing model is the same. The difference is just the $0.01/hr gap on the rate itself.
Both platforms include CAPTCHA solving on all tiers. Kernel includes advanced stealth (fingerprint evasion) on its free tier, while Notte gates that behind paid plans. In practice, advanced stealth only matters if you're hitting specific sites with aggressive bot detection. Notte's free tier is more generous on hours (100 lifetime vs. $5/mo in credits) and includes vault and replays.
Source: Kernel pricing, Notte pricing
Where Kernel wins
VM isolation. Per-VM isolation via Firecracker is a stronger security boundary than shared containers. For regulated workloads that need hard multi-tenancy, this is a real architectural advantage, backed by SOC 2 Type II and HIPAA.
Concurrency primitives. Browser pools (pre-warmed instances on the Startup tier) and standby mode (suspend idle browsers to disk) are built for high-concurrency workloads. If you're running hundreds of parallel sessions and cold-start latency on each matters, Kernel's architecture is designed for that.
Raw latency. Kernel is the fastest provider on Browser Arena at 341ms. The gap over Notte (394ms) is 53ms. Small, but it's there. If raw cold-start speed is your primary criterion, Kernel wins it.
When to use which
Kernel if you've already built credential handling, extraction, and scheduling, and you need a fast isolated browser runtime with strong multi-tenancy.
Notte if you want personas, structured extraction, hybrid workflows, and vault/replay without building the glue yourself. Assembling a browser runtime, a secrets manager, a proxy provider, a scheduler, and a replay tool from separate vendors works fine individually. Getting them to work together reliably is where teams burn weeks: credentials flowing into sessions without leaking into logs, replays covering the full workflow, scheduled runs using the same profiles as dev sessions.