The decision
Start with the product contracts for browser control, saved browser state, code execution, scheduled execution. Different labels do not establish different functionality; compare the implementation and conditions behind each one.
Cloudflare Browser Run provides headless browser sessions through CDP and browser code deployed in Workers. This comparison concerns sessions and their execution model, rather than the separate Quick Actions APIs.
Lightpanda is a browser engine built for automation, with a hosted cloud offering. It is an engine choice as well as a hosting choice, so evaluate the site's behavior and the browser APIs your workflow uses.
At a glance
| Requirement | Cloudflare Browser Run | Lightpanda |
|---|---|---|
| Browser control | Documented | Compatibility-dependent |
| Saved browser state | Session reuse / custom state | Not established |
| Credential handling | Application-owned | Application-owned |
| Website sign-in | Not established | Not established |
| Code execution | Workers composition | External worker |
| Scheduled execution | Workers trigger composition | External scheduler |
| Live view | Beta | Check engine support |
| Recordings / replay | Beta | Not established |
| Deployment choice | Cloudflare service | Engine available |
What survives a session
Cloudflare Browser Run: Cloudflare documents reuse of browser sessions and a Durable Objects integration. Keeping a session alive is different from exporting a portable authenticated profile; design the required state store explicitly.
Lightpanda: The reviewed cloud documentation does not establish a durable profile contract covering cookies and web storage. Determine how the required browser state is saved and restored before moving an authenticated workflow.
Website login
Cloudflare Browser Run: Use browser code to implement the website's sign-in flow and retain the necessary session state. The reviewed overview does not establish a managed website connection that checks sign-in readiness before a workflow starts.
Lightpanda: Browser engine compatibility and website authentication are separate requirements. The reviewed sources do not establish a managed website-auth connection equivalent; verify the login and verification flow on the target sites.
Where the code runs
Cloudflare Browser Run: Deploy browser automation within a Cloudflare Worker or connect to Browser Run from an external process over CDP. Workers provide the execution layer; compare their runtime and deployment model separately from browser access.
Lightpanda: The reviewed documentation establishes a browser engine and hosted access, not a deployed Python Function contract. A separate automation process must have its own deployment, triggers and monitoring design.
Published browser measurements
These are the latest provider runs in the saved BrowserArena snapshot checked on October 18, 2026. Dates and runner environments can differ. A lifecycle test opens, connects, navigates and releases a browser; the throughput test runs a separate browser action sequence. Neither measures managed authentication or deployed Function reliability.
Use these observations to choose what to test in your application. An account-configuration failure, an incompatible page action and a timed-out navigation require different interpretations. BrowserArena is maintained by Notte and publishes its source and methodology.
| Provider | Lifecycle median | Lifecycle P95 | Actions / second | Run dates |
|---|---|---|---|---|
| Cloudflare Browser Run | 769 ms | 1339 ms | 2.73 | 2026-10-18 / 2026-10-17 |
| Lightpanda | 488 ms | 550 ms | 3.61 | 2026-10-18 / 2026-10-18 |
Sources: browserarena.ai [1] ↗browserarena.ai [2] ↗github.com [3] ↗
Pricing model
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.
Capacity and 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.
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.
Check the browser connection
Install playwright-core in your application and provision a session through the provider's documented creation flow. Run this smoke test from the intended controller region with the returned CDP endpoint. It checks connection and navigation, not login, rendering parity or a complete business workflow.
Keep browser connection URLs on your backend. After the test, release the owned session through the provider's API. Product-specific lifecycle APIs and profile identifiers are not portable between providers.
import { chromium } from "playwright-core";
// Provision the owned browser using the provider's documented session API.
// Keep the connection URL in your backend's secret environment.
const endpoint = process.env.BROWSER_CDP_URL;
if (!endpoint) throw new Error("Set BROWSER_CDP_URL for an owned session");
const browser = await chromium.connectOverCDP(endpoint);
try {
const context = browser.contexts()[0] ?? await browser.newContext();
const page = context.pages()[0] ?? await context.newPage();
await page.goto("https://example.com", { waitUntil: "domcontentloaded" });
if ((await page.title()) !== "Example Domain") {
throw new Error("The browser did not reach the expected page");
}
console.log({ connected: true, expectedPage: true });
} finally {
await browser.close();
// Release the owned session with the provider's documented API as well.
// A disconnected socket alone is not a portable session-cleanup contract.
}Sources: playwright.dev ↗
Before you switch
Keep the same target workflow when evaluating both products. Separate infrastructure facts from measurements and test the required account state, action sequence and artifacts. A successful connection test does not establish that a long or authenticated task will complete.
Use the focused guides for Cloudflare Browser Run and Lightpanda below when the deciding requirement is pricing, persistence or code execution. Provider-owned resources such as session IDs, profiles and managed connections need a new mapping during migration.
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] ↗