What Cloudflare Browser Run supplies
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.
You already deploy Workers and want browser automation within that application's execution and scheduling model.
This is a source-based buying guide, not a claim of hands-on testing across every documented feature. Follow the source for the product and plan you would actually use.
Sources: developers.cloudflare.com ↗
Browser control
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.
Sources: developers.cloudflare.com ↗
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.
Sources: developers.cloudflare.com ↗
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.
Sources: developers.cloudflare.com ↗
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.
Sources: developers.cloudflare.com ↗
Deployment ownership
Cloudflare Browser Run: A Worker-based deployment fits Cloudflare application infrastructure; direct CDP keeps the controller elsewhere. Durable Objects are a composition for stateful browser work rather than a generic persistent browser profile.
Sources: developers.cloudflare.com ↗
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.
Sources: developers.cloudflare.com ↗
Inspecting a run
Cloudflare Browser Run: The Browser Run documentation lists live view, human-in-the-loop and session recording as beta features. Check current availability for the selected integration; beta support is not the same as a universal default.
Sources: developers.cloudflare.com ↗
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.
Sources: developers.cloudflare.com ↗
Where Notte is worth evaluating
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.
Notte combines cloud browser sessions with deployed Python automations and website authentication tools. You can control the browser over CDP or use Notte's actions, then deploy repeated work as a Function.
Retaining Cloudflare Browser Run can be the right outcome when its documented model already fits the application. Compare Notte only against a concrete missing capability, operating responsibility or cost constraint.
Sources: developers.cloudflare.com [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗
Questions to settle before buying
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.
Ask for the exact session, state and execution contract of the proposed account. A published browser observation does not establish feature availability, supported websites or production access.
- Which workload must pass before purchase?
- Who owns the running code, stored browser state and website connection?
- Which browser and handler limits apply to the selected plan?
- What does the invoice include beyond browser usage?
- What would have to be rebuilt to leave this provider?