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
Steel: Compare managed Steel with the documented self-hosted path explicitly. Self-hosting gives the team infrastructure responsibility that a hosted browser subscription would otherwise cover.
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.
Sources: docs.steel.dev [1] ↗tilion.com [2] ↗
Compare the execution model
Steel: The reviewed browser documentation establishes sessions, profiles and credentials. It does not establish a hosted Python handler with deployment and invocation APIs. An external worker can control a Steel browser; price and operate that worker separately.
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.
Sources: docs.steel.dev [1] ↗tilion.com [2] ↗
Compare operational limits
Steel: Steel's pricing and limits page describes hosted account entitlements. For a self-hosted deployment, capacity depends on the resources and orchestration you operate as well as the browser process.
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.
Sources: docs.steel.dev [1] ↗tilion.com [2] ↗
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 | Steel | Tilion |
|---|---|---|
| Browser control | Documented | Arena integration |
| Saved browser state | Documented | Not established |
| Code execution | External worker | Not established |
| Deployment choice | Documented | Not established |
Sources: docs.steel.dev [1] ↗docs.steel.dev [2] ↗docs.steel.dev [3] ↗docs.steel.dev [4] ↗docs.steel.dev [5] ↗docs.steel.dev [6] ↗tilion.com [7] ↗
Which approach fits?
Choose Steel when you want browser infrastructure that can fit a self-hosted deployment, with profiles and credentials available through browser-focused APIs.
Steel tradeoff: Hosted and self-hosted Steel are different operating choices. A cloud feature's documentation does not establish identical packaging, retention or operational support in a self-hosted installation.
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.
Sources: docs.steel.dev [1] ↗tilion.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
Steel's managed and self-hosted choices make infrastructure ownership a concrete deciding factor. Keep that option on the shortlist when operating the browser is intentional; evaluate Notte when owning fewer execution and authentication components is the actual goal.
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: docs.steel.dev [1] ↗tilion.com [2] ↗docs.notte.cc [3] ↗