Which parts of the browser stack will your team operate?
Managed browser access removes one infrastructure responsibility. Your team may still own the code runner, state store, scheduler and artifacts. A self-hosted engine moves more of that responsibility back into your environment.
Moving a browser to another region while leaving the controller in place changes the network path of every action. The advertised browser creation time does not describe those repeated round trips.
Compare 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.
Tilion: The public access path currently points to a waitlist and contact. A production integration needs an agreed API contract, service access and ownership of the browser lifecycle.
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.
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.
How to evaluate this choice
Use the deployment that fits the work your team wants to own. Reusing an existing runner can be practical; a hosted Function can reduce operations; self-hosting can meet a specific infrastructure requirement at the cost of operating it.
- Draw the controller, browser, state store and scheduler as separate components.
- Check the available browser and execution regions independently.
- Identify which provider owns upgrades, capacity and recordings.
- Verify code and stored-state portability before changing providers.
- Include maintenance and on-call work in a self-hosting decision.
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: 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.
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] ↗