Decide whether this move earns its cost
A controller loses its connection midway through a safe task and attempts to continue. Starting a fresh browser is not always equivalent to reconnecting to a live page.
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.
Evaluate Notte when browser ownership can be tracked independently of a transient controller socket. Confirm the supported reconnection path and distinguish it from loading a saved profile.
A provider's documented reconnect product can be decisive for a workflow that depends on a live page. Do not replace it with profile persistence without changing the task's continuation design.
Keep the result contract stable
A page with unsaved in-memory state, a stored provider session reference and a controlled controller interruption.
The application determines whether the original browser is still alive and either resumes the expected state or explicitly restarts the task.
Preserve the evidence contract across the move: Original session reference, page-state marker, connection interruption and resume-or-restart decision.
Map the workflow's resources
| Requirement | Cloudflare Browser Run | Notte |
|---|---|---|
| Browser control | Documented | Documented |
| Saved browser state | Session reuse / custom state | Documented |
| Live view | Beta | Documented |
| Deployment choice | Cloudflare service | Enterprise options |
Sources: developers.cloudflare.com [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗docs.notte.cc [4] ↗docs.notte.cc [5] ↗
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.
Notte: Profiles save cookies, local storage and session storage. Sessions start with fresh state by default. Persisting a profile writes state back when the session ends; a running session can also save its state explicitly.
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.
Notte: Vaults substitute credential placeholders in supported browser actions outside the model context. Managed Auth checks requested saved connections before automation. Personas supply an inbox and optional phone number for verification workflows.
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.
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.
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.
Notte: The public usage rates are $0.01 per browser-hour, $0.05 per Function-hour and $10 per GB of managed proxy traffic. Paid plans return their price as usage credits. Price the relevant meters and plan eligibility for the workload.
Cut over one responsibility at a time
For this Cloudflare Browser Run-to-Notte migration, keep the business assertion outside provider resource management. Source profile, connection, file and execution IDs are not valid target IDs; use a documented transfer path or establish the corresponding resource in Notte.
Retain source job history and a rollback route until the target pilot passes. A migration checklist is not evidence that saved state or runtime behavior is automatically portable.
- Inventory which steps depend on unsaved page state.
- Test the target session's documented connection path before moving continuation logic.
- Retain a restart path for ended sessions and verify that cleanup still occurs.
Sources: developers.cloudflare.com [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗
A proposed acceptance case
This is an evaluation design, not a claim that this workflow has been executed successfully on every provider.
| Part of the test | Required observation |
|---|---|
| Controlled input | A page with unsaved in-memory state, a stored provider session reference and a controlled controller interruption. |
| Pass condition | The application determines whether the original browser is still alive and either resumes the expected state or explicitly restarts the task. |
| Negative case | Repeat the reconnect after the browser has ended. The application must not treat a new session or restored profile as the original live page. |
| Evidence to retain | Original session reference, page-state marker, connection interruption and resume-or-restart decision. |
A reason to delay or keep the source
Repeat the reconnect after the browser has ended. The application must not treat a new session or restored profile as the original live page.
Cloudflare Browser Run: 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.
Delay cutover when the target's selected plan, required artifact path or supported website-account flow is not established. Resolve that gap before moving real jobs, even if the rate comparison favors the target.