Limits and billing

Lightpanda Cloud bills by browser time. You start on the free plan, and you can upgrade when you need more hours or more concurrency.

Plans

• Explorer is free, with a browser-hour pool and concurrency limit sized for testing, and community support on Discord.
• Builder is for production workloads: a larger monthly pool of browser hours and concurrent sessions, billed at a per-hour rate once you go over the included hours, plus email and Slack support.
• Enterprise is custom volume, concurrency, and support, with an SLA. For high-volume needs, on-premise, or a private cloud, contact us.

Upgrade, download invoices, or cancel from the billing page  in the console, which opens the Stripe customer portal.

How usage is measured

Browser hours are the total time your sessions stay open, metered by the second and summed over your billing period, so short sessions cost little. This is the number that counts against your monthly pool and, on paid plans, drives the overage rate.

Concurrent sessions are the sessions open at one instant. This limit is about parallelism, not total volume: a plan’s concurrency cap still lets you run many sessions a day, as long as no more than that cap overlap at once.

Both limits apply regardless of how you open a session: over CDP, MCP, the HTTP API, or from the playground.

When you reach a limit

If you open more sessions than your concurrency limit allows, the extra sessions are rejected with HTTP 429 Too Many Requests. Retry once a running session ends, or upgrade for more concurrency.

When you use up your monthly browser hours, the behavior depends on your plan. The free plan stops until its monthly pool resets. Paid plans keep running and bill the overage at your plan’s per-hour rate.

Some limits do not depend on your plan. A CDP connection closes after 15 minutes, whatever your pool has left, so split long jobs across sessions. An MCP session closes after 5 minutes without a request, so an active one keeps running.