Skip to main content
With Kernel, you only pay for what you use and nothing more. You don’t pay for idle time thanks to Standby Mode, idle browsers in a browser pool incur no usage charges, and you’re never charged for proxies.

​
Plan Pricing

​
Usage Rates

Included monthly credits apply to usage costs only.

​
Pricing calculator

​
Managed infrastructure

​
Concurrency limits

Kernel enforces a single concurrency limit covering all browsers you run at once—whether created on demand with browsers.create() or reserved in a browser pool. Your full limit is available to either API in any mix.

​
Notes

  • Reserved capacity in a browser pool counts toward your concurrency limit whether or not the browsers are currently acquired—a pool sized to 40 browsers uses 40 of your limit.
  • Browsers in Standby Mode count against your concurrency limit.
  • Limits are org-wide by default unless stated otherwise.

​
Rate limiting

Kernel enforces per-organization rate limits on API requests. When you exceed the rate limit, the API returns a 429 Too Many Requests response with a Retry-After header indicating how many seconds to wait before retrying. Rate-limited endpoints include these headers on every response: All Kernel SDKs automatically retry 429 responses up to 2 times, respecting the Retry-After header for delay timing. If retries are exhausted, the SDK throws a typed RateLimitError with the response headers accessible for custom backoff logic. If you need higher rate limits, contact us.

​
FAQ

App invocations are billed for active compute time, not per API call. The invocation rate in Usage Rates is based on the current 4 GB memory allocation at $0.0000166667 per GB-second.Billing starts when your code begins executing and stops when it finishes. You aren’t charged for queued time, deploying an app, or leaving a deployed app idle. Failed and canceled invocations still accrue charges for the time they ran.Browsers created by an invocation are billed separately for their active runtime at the browser rates above. Services your code calls, such as an LLM API, also bill you independently.The app invocation limits are concurrency limits, not a number of invocations included with your plan.
see this guide on spending controls.
Only for active runtime. timeout_seconds sets an idle auto-delete ceiling, not a billing window. Once a browser goes idle — 5 seconds after the last CDP or Live View activity — it enters Standby Mode and stops accruing usage cost, even if it stays alive until the timeout is reached. Deleting a browser early doesn’t lower cost any further (idle time is already free), but it does free up your concurrency slot sooner.
you pay the standard usage-based price per GB-second while browsers are running. Idle browsers in a pool incur no disk charges—you only pay when a browser is actively in use.Note: A browser pool counts toward your concurrency limit whether or not its browsers are currently acquired — a browser pool sized to 40 browsers uses 40 of your limit. Browser pools are available on Start-Up and Enterprise plans.
Managed Auth is included on all plans with no per-connection fees. It uses browser sessions for login, health checks, and eligible automatic reauthentication. These count toward your browser usage and concurrency like any other browser session.Auth sessions are fast, typically 5-30 seconds each, and most website sessions remain valid for days. For example, monitoring 100 auth connections typically costs less than $5/month in browser usage.
Regional browsers are charged at the same usage rates as our default, US-based browsers.
Free users can create up to three vaults. Unlimited vaults are included in paid plans. There are no surcharges to use Kernel’s agentic payments products.