The workflow decision
For embedded live browsers, the useful comparison is whether Notte or Steel can meet the following outcome: The intended user sees the correct browser and the tested interaction mode matches the product contract; closing the session leaves a clear ended state.
A live URL has its own access and lifecycle rules. An embeddable view, a read-only view and a user taking over control are different requirements.
A proposed acceptance case
An application embeds an active browser so an authorized user can inspect a task or take over a step. The viewer must follow the browser's lifecycle.
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 test session, its documented viewer mechanism and the application user who is allowed to view it. |
| Pass condition | The intended user sees the correct browser and the tested interaction mode matches the product contract; closing the session leaves a clear ended state. |
| Negative case | End the browser while the embedded viewer is open. Verify that the application does not continue presenting an apparently live, controllable session. |
| Evidence to retain | Application user, browser session reference, viewer mode and ended-session behavior. |
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 | Notte | Steel |
|---|---|---|
| Browser control | Documented | Documented |
| Saved browser state | Documented | Documented |
| Live view | Documented | Documented |
| Deployment choice | Enterprise options | Documented |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗docs.notte.cc [4] ↗docs.steel.dev [5] ↗docs.steel.dev [6] ↗docs.steel.dev [7] ↗docs.steel.dev [8] ↗
Inspecting a run
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.
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 control
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.
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.
Deployment ownership
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.
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.
Pricing model
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.
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.
Sources: notte.cc [1] ↗docs.steel.dev [2] ↗
What should change the choice?
Notte's live view is relevant when a browser workflow needs inspection alongside its session and execution records. Check whether the specific embed and interaction mode required by your UI is documented.
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.
An established embedded viewer can justify keeping the current service if changing it would alter the handoff experience. An active viewer and a recording of a past run are different products.
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗notte.cc [4] ↗docs.steel.dev [5] ↗docs.steel.dev [6] ↗docs.steel.dev [7] ↗docs.steel.dev [8] ↗
The cost boundary
Use the same attempted work and eligible account capacity in both estimates. The browser-hour rate does not include every proxy, execution or identity meter, and the cost of an incomplete job is still part of the workflow budget.
The workload evidence should include: Application user, browser session reference, viewer mode and ended-session behavior.
Sources: notte.cc [1] ↗docs.steel.dev [2] ↗
Make a bounded pilot
Open the viewer as the intended user, test its interaction mode, and confirm how the application behaves after the session closes.
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.
- Record the viewer interaction mode the application actually promises.
- Pilot the target viewer with a disposable session and intended user.
- Switch embeds only after session-end behavior and the handoff path are verified.