Which parts of the browser stack will your team operate?
Managed browser access removes one infrastructure responsibility. Your team may still own the code runner, state store, scheduler and artifacts. A self-hosted engine moves more of that responsibility back into your environment.
Moving a browser to another region while leaving the controller in place changes the network path of every action. The advertised browser creation time does not describe those repeated round trips.
Compare deployment ownership
Notte: Use a remote browser from your existing process or deploy the browser automation as a Notte Function. These choices put lifecycle, scheduling and monitoring responsibilities in different places.
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.
Compare the execution model
Notte: Functions deploy Python code with a run() entry point. Invoke them over HTTP or with an SDK, inspect run history, and roll back code by redeploying an earlier version as the latest version.
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.
Compare operational limits
Notte: The public plans list 5, 25 and 100 concurrent browser sessions, with custom limits on Enterprise. Session duration and concurrent capacity are separate plan limits; a larger technical API limit does not override the plan.
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.
How to evaluate this choice
Use the deployment that fits the work your team wants to own. Reusing an existing runner can be practical; a hosted Function can reduce operations; self-hosting can meet a specific infrastructure requirement at the cost of operating it.
- Draw the controller, browser, state store and scheduler as separate components.
- Check the available browser and execution regions independently.
- Identify which provider owns upgrades, capacity and recordings.
- Verify code and stored-state portability before changing providers.
- Include maintenance and on-call work in a self-hosting decision.
Requirements side by side
| Requirement | Notte | Cloudflare Browser Run |
|---|---|---|
| Browser control | Documented | Documented |
| Saved browser state | Documented | Session reuse / custom state |
| Code execution | Python Functions | Workers composition |
| Deployment choice | Enterprise options | Cloudflare service |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗docs.notte.cc [4] ↗docs.notte.cc [5] ↗docs.notte.cc [6] ↗developers.cloudflare.com [7] ↗
Which approach fits?
Choose Notte when your browser workflow needs saved logins, credential fill or scheduled Python code alongside the browser.
Notte tradeoff: A saved profile restores browser state; it does not prove that a website still considers the user signed in. Use Managed Auth when the workflow needs connection readiness before it starts.
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.
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.