The three-way buying decision
This shortlist starts with Steel and Tilion, then includes Notte as a third implementation path for short browser tools. A caller asks for the title and canonical URL of one public page, then discards the browser. The browser has no reason to keep account state after returning that result.
Session startup and minimum billing can dominate a short task. Reuse a session only when the task's isolation and state requirements allow it.
A proposed acceptance case
A caller asks for the title and canonical URL of one public page, then discards the browser. The browser has no reason to keep account state after returning that result.
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 public test URL and an expected title, supplied before either provider is run. |
| Pass condition | The caller receives the expected page identity and the session is released; record elapsed time from allocation through release. |
| Negative case | Point the tool at a controlled unavailable page. It must report a failed task and release the browser rather than returning an empty success. |
| Evidence to retain | Expected and observed page identity, allocation-to-release duration, terminal session status. |
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 | Steel | Tilion | Notte |
|---|---|---|---|
| Browser control | Documented | Arena integration | Documented |
| Saved browser state | Documented | Not established | Documented |
| Live view | Documented | Not established | Documented |
| Deployment choice | Documented | Not established | Enterprise options |
Sources: docs.steel.dev [1] ↗docs.steel.dev [2] ↗docs.steel.dev [3] ↗docs.steel.dev [4] ↗tilion.com [5] ↗docs.notte.cc [6] ↗docs.notte.cc [7] ↗docs.notte.cc [8] ↗docs.notte.cc [9] ↗
Browser control
Steel: Steel sessions expose browser connection details for existing automation code. Create and release the owned session through Steel's lifecycle API; a browser library is the controller, not the infrastructure scheduler.
Tilion: BrowserArena includes a Tilion session integration. The reviewed public Tilion homepage does not publish the full session API contract; obtain the supported connection and lifecycle instructions through its access flow.
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.
Sources: docs.steel.dev [1] ↗tilion.com [2] ↗docs.notte.cc [3] ↗
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.
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.
Sources: docs.steel.dev [1] ↗tilion.com [2] ↗docs.notte.cc [3] ↗
Pricing model
Steel: Hosted browser plans and a self-hosted browser have different cost structures. For self-hosting, include the worker, compute, networking, storage and operations rather than assigning the open-source code a zero operating cost.
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.
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.
The measured lifecycle starting point
The saved lifecycle observation includes creation, connection, navigation and release at concurrency one. It helps select a short-tool pilot; it does not predict this workflow's latency or fleet behavior.
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 | Lifecycle median | Lifecycle run | Throughput task completion |
|---|---|---|---|
| Steel | 1496 ms | 2026-10-18 | 100% on 2026-10-17 |
| Tilion | 124 ms | 2026-10-18 | 100% on 2026-10-17 |
| Notte | 332 ms | 2026-10-18 | 91% on 2026-10-18 |
Sources: browserarena.ai [1] ↗browserarena.ai [2] ↗docs.steel.dev [3] ↗tilion.com [4] ↗notte.cc [5] ↗
What should change the choice?
Notte is worth shortlisting when CDP control and a low browser-hour rate fit a caller that already owns its execution loop. Its lifecycle observation is relevant here because acquisition happens on every call.
Steel: 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.
Tilion: 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.
Keep the current provider when the complete tool already meets its latency and cost budget. A new connection URL is not valuable enough by itself to justify moving a working integration.
Sources: docs.steel.dev [1] ↗docs.steel.dev [2] ↗docs.steel.dev [3] ↗tilion.com [4] ↗docs.notte.cc [5] ↗docs.notte.cc [6] ↗notte.cc [7] ↗
How to remove an option from the shortlist
For this workflow, require the following evidence from Steel, Tilion and Notte: Expected and observed page identity, allocation-to-release duration, terminal session status.
Remove a proposed configuration when its documented mechanism or a controlled pilot cannot meet the pass condition. Keep an undocumented feature as an unresolved question instead of inventing an equivalence. Do not select a provider solely because it appears in this shortlist.
- The caller receives the expected page identity and the session is released; record elapsed time from allocation through release.
- Point the tool at a controlled unavailable page. It must report a failed task and release the browser rather than returning an empty success.
Sources: docs.steel.dev [1] ↗tilion.com [2] ↗docs.notte.cc [3] ↗
Make a bounded pilot
Record the complete create, connect, navigate and release lifecycle, with a correctness check on the returned result.
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.
- Keep the existing page-reading logic and replace only session allocation and release.
- Compare the returned title and canonical URL before comparing timing.
- Canary the new provider with fresh sessions and count failed starts in the tool budget.