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.
Tilion: Arena provides an estimated usage rate for its test. The reviewed public homepage does not establish a self-serve production plan, allowances or overage terms. Obtain those terms before quoting a monthly bill.
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.
Tilion: Arena's observed test concurrency is a test configuration, not an account entitlement. Obtain the production concurrency and session creation limits for your access tier before sizing a fleet.
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.
Tilion: Public documentation reviewed for this comparison does not establish a deployable Function or app-action contract. Confirm where your automation code runs and how invocation, versioning and logs work before choosing the execution path.
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 | Tilion |
|---|---|---|
| Browser control | Documented | Arena integration |
| Saved browser state | Session reuse / custom state | Not established |
| Code execution | Workers composition | Not established |
| Deployment choice | Cloudflare service | Not established |
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 Tilion when you can obtain access and test the product directly, with its current API and commercial terms in hand.
Tilion tradeoff: Arena measurements do not establish public availability or feature completeness. Confirm access, API details and plan terms before planning a production migration.
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.
The reviewed Tilion homepage offers a waitlist and contact route. Arena's tested integration is useful evidence about a run, but a purchasing or migration decision still needs a documented access, state and execution contract; those unknowns must remain visible beside Notte's public docs.
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] ↗tilion.com [2] ↗docs.notte.cc [3] ↗