What will the same completed work cost?
Start with the work that has to finish: executions per month, browser time per execution, concurrent browsers and network traffic. Choose the cheapest eligible plan for that workload. An hourly rate can be lower while the bill is higher because a plan floor, billing minimum or extra service applies.
For 10,000 runs lasting three minutes, browser time is 500 hours before rounding, setup and retries. At Notte's published $0.01 browser-hour rate, that meter is $5. Paid-plan eligibility and any proxy or Function usage still determine the total bill.
Compare the billing contract
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.
AWS AgentCore Browser: A complete AWS workflow may include browser use, the controlling compute service, storage and other metered services. Price the selected architecture and region instead of treating a browser benchmark rate as the final invoice.
Sources: developers.cloudflare.com [1] ↗aws.amazon.com [2] ↗
Compare operational 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.
AWS AgentCore Browser: AgentCore Browser supports multiple simultaneous sessions. Review AWS quotas and the chosen tool/session configuration; the browser session's timeout and the controller's execution timeout are separate limits.
Sources: developers.cloudflare.com [1] ↗docs.aws.amazon.com [2] ↗
Compare the execution model
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.
AWS AgentCore Browser: The Browser Tool supplies the browser environment. An external process or another AWS execution service runs the application code that controls it. Identify that service and its runtime before comparing it with a deployed browser Function.
Sources: developers.cloudflare.com [1] ↗docs.aws.amazon.com [2] ↗
How to evaluate this choice
A useful cost comparison gives both a usage estimate and the eligible monthly plan. Keep an unsupported workload out of the price ranking even if a rate can be multiplied into an attractive number.
- Count attempted runs as well as successful runs.
- Apply the provider's rounding rule to each session before adding usage.
- Separate browser time, function compute, proxy traffic and identity services.
- Apply included credits once; do not add the same subscription fee again.
- Mark an ineligible plan as a capacity mismatch rather than a cheap option.
Requirements side by side
| Requirement | Cloudflare Browser Run | AWS AgentCore Browser |
|---|---|---|
| Browser control | Documented | Browser automation endpoint |
| Saved browser state | Session reuse / custom state | Explicit state design |
| Code execution | Workers composition | External AWS compute |
| Deployment choice | Cloudflare service | AWS service |
Sources: developers.cloudflare.com [1] ↗docs.aws.amazon.com [2] ↗
Which approach fits?
Choose Cloudflare Browser Run when you already deploy Workers and want browser automation within that application's execution and scheduling model.
Cloudflare Browser Run tradeoff: 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.
Choose AWS AgentCore Browser when your application already uses AWS identity, logging and storage, and browser workflows need to fit those systems.
AWS AgentCore Browser tradeoff: The browser tool is not the entire AgentCore platform. Do not assign capabilities from unrelated AgentCore execution or identity products to a browser session without specifying the composition.
Sources: developers.cloudflare.com [1] ↗docs.aws.amazon.com [2] ↗
A useful acceptance check
Write a pass/fail result for the real task before running the evaluation. Record the account, configuration and code version next to that result. Repeat failures need an explanation, not an automatically different browser configuration.
When Notte belongs on this shortlist
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.
AgentCore Browser's AWS integration can matter more than moving a browser endpoint. Retain AWS identity and observability requirements in the evaluation, and separately account for the code runner and website login before comparing Notte's integrated workflow.
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.
Consider this third option when its documented mechanism addresses a requirement left open by the two providers above. A working configuration on either original provider can still be the better choice; compare the task and ownership cost before switching.
Sources: developers.cloudflare.com [1] ↗docs.aws.amazon.com [2] ↗docs.notte.cc [3] ↗