Skip to content

pricing.mdx

Latest commit

 

History

History
118 lines (84 loc) · 5.23 KB

pricing.mdx

File metadata and controls

118 lines (84 loc) · 5.23 KB
title Pricing & Limits

With Kernel, you only pay for what you use and nothing more. You don't pay for idle time thanks to Standby Mode, and you're never charged for proxies.

Pricing

Browser type Price ($/sec)
Headless 0.0000166667
Headful 0.0001333336
Headful + GPU acceleration 0.0008000016

Note: GPU acceleration is only available on headful, on-demand browsers. Standby mode is not supported for GPU-accelerated browsers.

Pricing calculator

import { PricingCalculator } from '/snippets/calculator.jsx';

Managed infrastructure

Feature Developer (free + usage) Hobbyist ($30 / mo + usage) Start-Up ($200 / mo + usage) Enterprise
Included credits / mo $5 $10 $50 Custom
Extended browser timeouts ✅ ✅ ✅ ✅
Browser live view ✅ ✅ ✅ ✅
Configurable browser viewports ✅ ✅ ✅ ✅
Managed stealth mode ✅ ✅ ✅ ✅
Computer controls API ✅ ✅ ✅ ✅
Browser replays ❌ 7 days 30 days Custom
Browser profiles ❌ ✅ ✅ ✅
Managed auth profiles ❌ ✅ ✅ ✅
File uploads & downloads ❌ ✅ ✅ ✅
Configurable browser extensions ❌ ❌ ✅ ✅
Configurable & BYO proxies ❌ ❌ ✅ ✅
Browser pools ❌ ❌ ✅ ✅
Support Discord Discord Email Shared Slack
SOC2 compliance ✅ ✅ ✅ ✅
GPU acceleration ❌ ❌ ✅ ✅
HIPAA compliance (BAA) ❌ ❌ ❌ ✅

Note: Included monthly credits apply to usage costs only.

Reserved browsers (browser pools)

With Browser Pools, you pay the standard usage-based price per GB-second while browsers run, plus a small disk space charge when they are idle.

Headful Headless
Disk price per GB/hour $0.001 $0.001
Disk allocation per browser 4 GB 1 GB
Example: 50 browsers idle/month $144/month $36/month

Note: Disk space charges are waived for Enterprise plan customers.

Note: GPU acceleration is not available for browser pools.

Managed Auth

Managed Auth is included on all paid plans with no per-connection fees. Under the hood, it uses browser sessions to log in and keep your sessions fresh—these count toward your browser usage and concurrency like any other browser session.

Auth sessions are fast (typically 5-30 seconds each). Kernel monitors session health and re-authenticates automatically when sessions expire—most stay valid for days. For example, keeping 100 auth connections logged in typically costs less than $5/month in browser usage.

Concurrency limits

Feature Developer (free + usage) Hobbyist ($30 / mo + usage) Start-Up ($200 / mo + usage) Enterprise
Reserved browsers (browser pools) 0 0 100 Custom
On-demand browsers 5 10 50 Custom
App invocations 5 10 50 Custom
App invocations (per-app) 5 10 20 Custom
Managed auth health check interval N/A 1 hour minimum 20 minutes minimum Custom

Note: Browsers in Standby Mode count against on-demand concurrency limits.

Note: Limits are org-wide by default unless stated otherwise. Managed auth profiles refer to the number of active auth connections that Kernel maintains using your stored Credentials or 1Password connection.

Rate limiting

Kernel enforces per-organization rate limits on API requests to ensure platform stability. 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 limits by plan

Plan Requests per minute (burst) Sustained rate
Enterprise 250 ~4 req/sec
Start-Up 100 ~1.7 req/sec
Hobbyist 25 ~0.4 req/sec
Developer (free) 10 ~0.2 req/sec

Rate limits use a token bucket algorithm. The burst capacity allows short spikes above the sustained rate, while the sustained rate determines the long-term throughput ceiling.

Rate-limited endpoints

Endpoint Description
POST /browsers Create a browser session
POST /invocations Launch an app invocation
POST /browsers/{id}/process/exec Execute a command synchronously
POST /browsers/{id}/process/spawn Execute a command asynchronously
POST /browsers/{id}/playwright/execute Execute Playwright code

Response headers

Rate-limited endpoints include these headers on every response:

Header Description
X-RateLimit-Limit Maximum requests allowed per minute
X-RateLimit-Remaining Requests remaining in the current window
Retry-After Seconds to wait before retrying (only on 429 responses)

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.