Can the provider start and run the fleet you need?
Concurrent sessions, session creation rate and HTTP request rate are different limits. A plan that allows a hundred open browsers may still need time to start them. Polling or retrying without a budget can exhaust API capacity before the browser cap is reached.
If a thousand jobs arrive together but only fifty browser slots are available, queue jobs before allocating browsers. Starting all jobs immediately can turn ordinary capacity management into timeouts, retries and idle browser charges.
Compare operational limits
Cloudflare Browser Run: Browser Run has its own limits and pricing alongside Workers. Account browser capacity, session creation limits and the Worker execution budget constrain different parts of a workflow.
Lightpanda: Use Lightpanda Cloud's limits and billing documentation for hosted capacity. Self-operated engine instances have a different capacity model and should not inherit cloud account assumptions.
Compare the browser lifecycle
Cloudflare Browser Run: Browser Run supports direct browser control through CDP or the documented Playwright and Puppeteer integrations. Browser sessions are a separate integration path from one-request Quick Actions.
Lightpanda: Lightpanda Cloud supplies browser access for automation. Connect using the documented cloud path and evaluate compatibility with the control library and site behavior needed by the workflow.
Compare the billing contract
Cloudflare Browser Run: Price browser usage and the Worker execution components required by the workload. The Browser Run pricing page, rather than a single browser-hour estimate, defines included allowances and applicable limits.
Lightpanda: Use the cloud billing unit and account limits for hosted access. A lower rate only helps if the target pages and required actions complete correctly on the selected engine.
How to evaluate this choice
A quota table establishes what an account may request. A measured concurrency curve establishes how the tested workload behaved. Keep both in the decision and avoid extrapolating a single-session result to a large fleet.
- Specify the number of simultaneously open browsers and the burst arrival rate.
- Measure time until every requested browser is ready for work.
- Record rate limits and honor the returned retry delay.
- Cap worker concurrency and keep queued tasks outside browser sessions.
- Include failed starts and cleanup in the load test's result.
Requirements side by side
| Requirement | Cloudflare Browser Run | Lightpanda |
|---|---|---|
| Browser control | Documented | Compatibility-dependent |
| Saved browser state | Session reuse / custom state | Not established |
| Code execution | Workers composition | External worker |
| Deployment choice | Cloudflare service | Engine available |
Which approach fits?
Choose Cloudflare Browser Run when you already deploy Workers and want browser automation within that application's execution and scheduling model.
Cloudflare Browser Run tradeoff: A Worker and a browser session have separate resource and lifecycle constraints. Confirm the chosen browser library and binding path instead of assuming an unchanged local browser script will deploy directly.
Choose Lightpanda when your workflow can use Lightpanda's supported browser APIs and you want to evaluate that engine on the pages you actually automate.
Lightpanda tradeoff: CDP connectivity does not establish complete Chromium compatibility. Validate rendering-dependent steps, downloads and browser features with the selected engine before a migration.
A useful acceptance check
Write a pass/fail result for the real task before running the evaluation. Record the account, configuration and code version next to that result. Repeat failures need an explanation, not an automatically different browser configuration.
When Notte belongs on this shortlist
Cloudflare can be an economical architectural choice when Workers and the surrounding scheduling already exist in your application. Notte is worth evaluating when a browser, deployed Python handler and authentication workflow should share a product rather than a Workers composition.
Lightpanda introduces a browser-engine decision. Keep it on the shortlist when its supported actions fit the real pages you use; a successful CDP connection or text task does not establish visual or full-browser equivalence with the proposed Notte workflow.
Notte: Create an owned browser session, connect Playwright or Puppeteer over CDP, and stop the session when the work finishes. Browser lifecycle management remains necessary even when the control socket disconnects.
Consider this third option when its documented mechanism addresses a requirement left open by the two providers above. A working configuration on either original provider can still be the better choice; compare the task and ownership cost before switching.
Sources: developers.cloudflare.com [1] ↗lightpanda.io [2] ↗docs.notte.cc [3] ↗