The workflow decision
For budgeted browser fleets, the useful comparison is whether Notte or Cloudflare Browser Run can meet the following outcome: The eligible configuration stays within the modeled budget while completing the required work, with each usage meter and plan credit applied once.
Choose a plan that can run the workload before calculating usage. Retry traffic, idle sessions and rounded minimum time can change the cost per completed job.
A proposed acceptance case
A team has a recurring browser budget and a target number of completed jobs. Plan capacity, billing rounding and failed attempts affect what the budget buys.
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 representative job volume, attempted session durations, concurrency requirement and network usage estimate. |
| Pass condition | The eligible configuration stays within the modeled budget while completing the required work, with each usage meter and plan credit applied once. |
| Negative case | Reprice the workload with additional failed attempts and idle time. The model must expose the higher cost instead of preserving an optimistic cost-per-success figure. |
| Evidence to retain | Attempted and completed jobs, rounded browser usage, separate meters, plan allowance and estimated invoice. |
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 |
|---|---|---|
| Browser control | Documented | Documented |
| Saved browser state | Documented | Session reuse / custom state |
| Live view | Documented | Beta |
| Deployment choice | Enterprise options | Cloudflare service |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗docs.notte.cc [4] ↗developers.cloudflare.com [5] ↗
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.
Browser control
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.
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.
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.
A common browser-usage scenario
For an illustrative fleet of 10 browsers active eight hours a day over 30 days, browser usage is 2,400 hours. The table multiplies that same usage by the saved Arena rate. It excludes other providers' plan minimums, allowances and rounding, so it is not a total-invoice comparison.
Task completion below comes from the separate throughput workload. Preserve its date and failure context; a low usage rate or fast lifecycle does not establish that an authenticated business job completes. BrowserArena is maintained by Notte.
| Provider | Arena rate / browser-hour | Browser usage at 2,400 hours | Throughput task completion |
|---|---|---|---|
| Notte | $0.01 | $24.00 | 91% on 2026-10-18 |
| Cloudflare Browser Run | $0.09 | $216.00 | 100% on 2026-10-17 |
Sources: browserarena.ai [1] ↗browserarena.ai [2] ↗notte.cc [3] ↗developers.cloudflare.com [4] ↗
What should change the choice?
Notte's public $0.01 browser-hour rate makes it a useful cost baseline. Apply its paid-plan minimum and any proxy, execution or identity usage before estimating the actual recurring bill.
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.
Included allowances, a different billing minimum or an existing commercial commitment can make retaining another provider reasonable. Compare invoices for eligible configurations, not hourly labels alone.
Sources: notte.cc [1] ↗docs.notte.cc [2] ↗docs.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.
A representative job volume, attempted session durations, concurrency requirement and network usage estimate.
Make a bounded pilot
Price a representative week from attempted sessions and actual duration, then compare it with the plan's included credits and limits.
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.
- Capture source attempted usage and plan allowance for a representative period.
- Model the same work using the target plan, rounding rules and separate service meters.
- Canary a bounded budget before changing the full fleet's billing path.