Decide whether this move earns its cost
A signed-in job requests a report from a website and transfers the completed file to application storage. A download beginning is not the delivery outcome.
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 belongs on the shortlist when saved account state and an executable browser workflow simplify the report job. Confirm the chosen file-transfer API and storage boundary in the current docs before moving the delivery step.
A working download-to-storage pipeline is a reason to retain the current provider until an equivalent artifact path is demonstrated. Neither a replay nor a successful page navigation proves that a file arrived.
Keep the result contract stable
A controlled report with a known filename, expected content marker and application-owned destination.
The application receives the complete expected file, verifies its content marker and associates it with the originating account and job.
Preserve the evidence contract across the move: Website report ID, file byte count, content verification and destination object reference.
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.
- Separate website report generation from provider file retrieval in the current code.
- Keep the destination and content check unchanged while replacing the retrieval path.
- Test delayed and interrupted downloads before switching scheduled report delivery.
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 controlled report with a known filename, expected content marker and application-owned destination. |
| Pass condition | The application receives the complete expected file, verifies its content marker and associates it with the originating account and job. |
| Negative case | Close the browser before a deliberately delayed download completes. The job must detect the missing or partial artifact instead of reporting a delivered report. |
| Evidence to retain | Website report ID, file byte count, content verification and destination object reference. |
A reason to delay or keep the source
Close the browser before a deliberately delayed download completes. The job must detect the missing or partial artifact instead of reporting a delivered report.
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.