Skip to main content
One entry per product. Start here if you’re evaluating Kernel or looking for the canonical page on something.

Managed auth

Kernel performs the login for you — credentials, MFA, SSO redirects, account and organization pickers — then keeps the session alive with background health checks and reauthentication for supported flows. Credentials never enter your agent’s context or your codebase. Log in through Kernel’s hosted UI, your own React flow, or programmatically.

Stealth

Every Kernel browser ships with anti-detection defaults. One flag adds a static ISP proxy and the managed CAPTCHA solver on top. The bot anti-detection guide covers what sites measure and which configuration gets through.

Proxies

Datacenter, ISP, residential, mobile, or your own. Create a proxy once and reuse it across sessions, hot-swap it on a running browser, and bypass it per host. Kernel-provided proxies aren’t metered or billed.

Browser pools

A fixed set of identically-configured browsers that Kernel keeps ready, so acquiring one costs nothing and isn’t subject to the create rate. Idle browsers in a pool incur no usage charges.

GPU browsers

Hardware-accelerated rendering for WebGL, canvas-heavy pages, and video — and a stronger fingerprint, since software-rendered output doesn’t match any real consumer GPU.

Profiles

Persisted browser state — cookies, local storage, logins, history, open tabs — that you attach to any browser by name. What managed auth writes into, and useful on its own for anything that has to survive between runs.

Browser telemetry

Structured events for navigation, network requests and failures, CDP commands, CAPTCHA challenges, and proxy errors. Stream them live or read them after a session is gone.

Replays and live view

Watch a running session in your browser or embed it in your own app, hand control to a person mid-run, and record any session as an MP4 replay for debugging, demos, or compliance.

App Platform

Deploy your agent next to its browser and invoke it on demand, on a schedule, or from your own backend. Co-location removes the per-action round trip, the disconnects, and the screenshot bandwidth that a remote CDP connection costs you.

Ways in