The workflow decision
For scheduled browser Functions, the useful comparison is whether Notte or Cloudflare Browser Run can meet the following outcome: Each scheduled attempt has a terminal execution record and a verified business result, and the expected browser cleanup occurs.
Scheduling must specify timezone, overlapping runs, parameters and what happens after a failed execution. A successful schedule trigger is not a successful browser task.
A proposed acceptance case
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.
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. |
Documented mechanisms, side by side
These labels describe product mechanisms. The linked source and the acceptance case determine whether a mechanism meets this workflow's requirement.
| Requirement | Notte | Cloudflare Browser Run |
|---|---|---|
| Code execution | Python Functions | Workers composition |
| Scheduled execution | Native | Workers trigger composition |
| Recordings / replay | Documented | Beta |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗developers.cloudflare.com [3] ↗
Where the code runs
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.
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.
Pricing model
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.
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.
What should change the choice?
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.
Cloudflare Browser Run: 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.
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.
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗notte.cc [3] ↗developers.cloudflare.com [4] ↗developers.cloudflare.com [5] ↗
The cost boundary
Use the same attempted work and eligible account capacity in both estimates. The browser-hour rate does not include every proxy, execution or identity meter, and the cost of an incomplete job is still part of the workflow budget.
The workload evidence should include: Scheduled time and timezone, execution ID, business result and overlap outcome.
Make a bounded pilot
Run a controlled scheduled job, verify its business result and browser cleanup, then inspect the recorded schedule state and execution history.
Use the same authorized account, input and final-state check in each configuration. Treat a missing product contract as an open question; do not turn an undocumented capability into an unsupported claim or a successful test result.
- 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.