Decide whether this move earns its cost
A queue receives more browser jobs than the account can run at once. Workers must wait for capacity and recover slots after failed jobs.
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 candidate when its published concurrency tiers fit the queue and the team wants browser and Python execution resources in one platform. Capacity must be checked separately from the hourly rate.
An existing pool or queue integration can outweigh a rate difference when it already handles the burst reliably. A single-session latency result does not establish fleet behavior for any provider.
Keep the result contract stable
A fixed burst of jobs, the account's documented concurrency entitlement and a bounded application queue.
The queue drains without exceeding the entitlement; every allocated browser is associated with one job and eventually released.
Preserve the evidence contract across the move: Queue arrival and start times, allocated sessions, completion counts and recovered capacity.
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] ↗
Capacity and limits
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.
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.
Browser control
Cloudflare Browser Run: Browser Run supports direct browser control through CDP or the documented Playwright and Puppeteer integrations. Browser sessions are a separate integration path from one-request Quick Actions.
Notte: Create an owned browser session, connect Playwright or Puppeteer over CDP, and stop the session when the work finishes. Browser lifecycle management remains necessary even when the control socket disconnects.
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.
- Keep admission control in place while introducing the target provider.
- Move one queue partition and record allocation failures separately from task failures.
- Compare drained jobs, leaked slots and cost per completed job before raising concurrency.
Sources: developers.cloudflare.com [1] ↗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 fixed burst of jobs, the account's documented concurrency entitlement and a bounded application queue. |
| Pass condition | The queue drains without exceeding the entitlement; every allocated browser is associated with one job and eventually released. |
| Negative case | Fail a job after browser allocation. Verify that the next queued job can acquire the recovered slot and that retries do not create untracked sessions. |
| Evidence to retain | Queue arrival and start times, allocated sessions, completion counts and recovered capacity. |
A reason to delay or keep the source
Fail a job after browser allocation. Verify that the next queued job can acquire the recovered slot and that retries do not create untracked sessions.
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.