The three-way buying decision
This shortlist starts with Steel and Browser Use, then includes Notte as a third implementation path for debugging recorded browser runs. A support engineer investigates a failed job after the browser has ended. The recording must be connected to the input, execution version and final result.
The recording mode, retention and session identifiers determine what can be reconstructed. Some artifacts become available only after the browser stops or processing finishes.
A proposed acceptance case
A support engineer investigates a failed job after the browser has ended. The recording must be connected to the input, execution version and final 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 harmless workflow with one deliberately failing step and recording enabled through the documented mechanism. |
| Pass condition | An investigator can find the correct run, identify the failing step and reconcile the recording with the application's terminal status. |
| Negative case | Create a run with the wrong recording configuration in a test environment. The system must expose the missing artifact rather than linking a different run as evidence. |
| Evidence to retain | Job input reference, code version, session ID, recording reference and terminal result. |
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 | Browser Use | Notte |
|---|---|---|---|
| Browser control | Documented | Documented | Documented |
| Saved browser state | Documented | Documented | Documented |
| Live view | Documented | Documented | Documented |
| Deployment choice | Documented | Local framework available | Enterprise options |
Sources: docs.steel.dev [1] ↗docs.steel.dev [2] ↗docs.steel.dev [3] ↗docs.steel.dev [4] ↗docs.browser-use.com [5] ↗docs.browser-use.com [6] ↗docs.browser-use.com [7] ↗docs.notte.cc [8] ↗docs.notte.cc [9] ↗docs.notte.cc [10] ↗docs.notte.cc [11] ↗
Inspecting a run
Steel: Steel documents live and past sessions as well as Agent Traces. Browser recordings answer what happened on the page; traces add context around the agent or application driving it.
Browser Use: Browser Use documents live preview and recording. Recording availability follows the browser lifecycle and processing state; a live URL is for an active browser rather than a permanent replay link.
Notte: Live view shows an active browser and can be embedded in an application. Recordings let you review a finished session. Function runs have their own history and results, so keep the run ID alongside the browser session ID.
Sources: docs.steel.dev [1] ↗docs.browser-use.com [2] ↗docs.notte.cc [3] ↗
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.
Browser Use: The V4 browser API creates a browser with a CDP URL. Your Playwright or Browser Use code can connect directly. Stopping the browser requires the browser API; closing CDP alone does not stop it.
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] ↗docs.browser-use.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.
Browser Use: Use the hosted browser from your own process or send a task to the hosted agent. The open-source local framework is another deployment option and should not be equated with the cloud subscription.
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] ↗docs.browser-use.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.
Browser Use: Browser time and hosted-agent/model usage are separate pricing questions. Select the infrastructure path before comparing rates, and account for retained idle browser time and network usage where applicable.
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.
Sources: docs.steel.dev [1] ↗docs.browser-use.com [2] ↗notte.cc [3] ↗
What should change the choice?
Notte is relevant when browser recordings and Python run history need to support the same investigation. Confirm artifact availability and retention for the selected account before relying on it for support.
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.
Browser Use: Browser Use's hosted-agent offering and standalone browser infrastructure are separate options. Keep the comparison at the browser layer when your application already owns its controller; compare execution ownership separately if the hosted agent is part of the requirement.
Keep a provider whose existing replay integration already meets the team's investigation needs if the new system would lose necessary artifacts or history. A green feature label does not establish equivalent retention.
Sources: docs.steel.dev [1] ↗docs.steel.dev [2] ↗docs.steel.dev [3] ↗docs.steel.dev [4] ↗docs.browser-use.com [5] ↗docs.browser-use.com [6] ↗docs.browser-use.com [7] ↗docs.notte.cc [8] ↗docs.notte.cc [9] ↗docs.notte.cc [10] ↗notte.cc [11] ↗
How to remove an option from the shortlist
For this workflow, require the following evidence from Steel, Browser Use and Notte: Job input reference, code version, session ID, recording reference and terminal result.
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.
- An investigator can find the correct run, identify the failing step and reconcile the recording with the application's terminal status.
- Create a run with the wrong recording configuration in a test environment. The system must expose the missing artifact rather than linking a different run as evidence.
Sources: docs.steel.dev [1] ↗docs.browser-use.com [2] ↗docs.notte.cc [3] ↗
Make a bounded pilot
Create a controlled failure, stop the browser correctly, and retrieve the expected replay, logs and application result using the stored run identifiers.
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.
- Preserve source run and replay references for historical jobs.
- Add target session and Function references to newly canaried jobs.
- Have an investigator reconstruct a controlled failure before moving the support workflow.