Decide whether this move earns its cost
A recurring job signs in, performs a permitted browser task and records its result without an interactive caller. Overlapping triggers must not create unintended duplicate work.
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 is a natural candidate when a scheduled Python handler and its browser should share an execution platform. Check schedule behavior and browser duration independently.
Keep an existing scheduler or a provider-native execution language when it already meets the job contract and a Python port would add unnecessary maintenance. A triggered request is not proof of completion.
Keep the result contract stable
A test schedule with an explicit timezone, fixed inputs and a destination that exposes whether the operation ran once.
Each scheduled attempt has a terminal execution record and a verified business result, and the expected browser cleanup occurs.
Preserve the evidence contract across the move: Scheduled time and timezone, execution ID, business result and overlap outcome.
Map the workflow's resources
| Requirement | Cloudflare Browser Run | Notte |
|---|---|---|
| Code execution | Workers composition | Python Functions |
| Scheduled execution | Workers trigger composition | Native |
| Recordings / replay | Beta | Documented |
Sources: developers.cloudflare.com [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗
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.
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.
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.
- Pause the target schedule while replaying a fixed input manually.
- Verify the Python handler's result and browser cleanup before enabling a canary schedule.
- Run only one authoritative production schedule during cutover and preserve source run history.
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 test schedule with an explicit timezone, fixed inputs and a destination that exposes whether the operation ran once. |
| Pass condition | Each scheduled attempt has a terminal execution record and a verified business result, and the expected browser cleanup occurs. |
| Negative case | Let one test run outlive the next trigger. Inspect the overlap policy and verify the intended number of website changes. |
| Evidence to retain | Scheduled time and timezone, execution ID, business result and overlap outcome. |
A reason to delay or keep the source
Let one test run outlive the next trigger. Inspect the overlap policy and verify the intended number of website changes.
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.