Lightpanda · Rate Limits

Lightpanda Rate Limits

Lightpanda's interface is the Chrome DevTools Protocol over WebSocket rather than a metered REST API, so there are no documented per-request RPM/TPM quotas. For the open-source self-hosted server (`lightpanda serve`), practical limits are bounded by host compute, memory, and the number of concurrent WebSocket/CDP sessions and browser targets you run. For Lightpanda Cloud, concurrency and usage are governed by the (request-based) account and token; specific published limits were not available and are not reconciled in this artifact.

Lightpanda Rate Limits is the machine-readable rate-limit profile for Lightpanda on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring connections, sessions, and usage.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Headless Browser, Browser Automation, CDP, WebSocket, and Rate Limiting.

3 Limits Throttle: see provider documentation
Headless BrowserBrowser AutomationCDPWebSocketRate LimitingQuotasThrottling

Limits

Concurrent CDP Sessions (Self-Hosted) instance
connections
bounded by host compute
Open-source server concurrency is limited by CPU/RAM, not a provider quota.
Concurrent Browsers / Targets (Cloud) account
sessions
see provider documentation
Governed by Lightpanda Cloud account/token; not publicly documented.
Cloud Usage account
usage
see provider documentation
Request-based access; published usage limits not available at artifact time.

Policies

Self-Hosted Scaling
Scale horizontally by running multiple `lightpanda serve` instances; concurrency is bounded by your own infrastructure.
Backoff Strategy
CDP clients (Puppeteer/Playwright/chromedp) should handle dropped WebSocket connections with reconnect and backoff.

Sources