The job and its deciding constraint
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
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 | Notte | Browserbase | Steel |
|---|---|---|---|
| Browser control | Documented | Documented | Documented |
| Saved browser state | Documented | Contexts | Documented |
| Live view | Documented | Documented | Documented |
| Deployment choice | Enterprise options | Hosted service | Documented |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗docs.notte.cc [4] ↗docs.browserbase.com [5] ↗docs.browserbase.com [6] ↗docs.browserbase.com [7] ↗docs.browserbase.com [8] ↗docs.steel.dev [9] ↗docs.steel.dev [10] ↗docs.steel.dev [11] ↗docs.steel.dev [12] ↗
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.
Browserbase: Browserbase documents live session views, recordings and observability. Function results also include a session association, so correlate the handler outcome with the actual browser 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.
Sources: docs.notte.cc [1] ↗docs.browserbase.com [2] ↗docs.steel.dev [3] ↗
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.
Browserbase: Create a managed browser session and connect a supported browser library to its connection URL. The session API and the browser connection have separate lifecycles.
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.
Sources: docs.notte.cc [1] ↗docs.browserbase.com [2] ↗docs.steel.dev [3] ↗
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.
Browserbase: Publish TypeScript Functions through the supported deployment flow. The reviewed Function overview lists us-west-2 availability; this is narrower than assuming every browser region also hosts Functions.
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.
Sources: docs.notte.cc [1] ↗docs.browserbase.com [2] ↗docs.steel.dev [3] ↗
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.
Browserbase: Compare the public plan's included browser allowance and overage with the workflow's duration. Include proxy traffic and any separately priced services; an Arena browser-hour estimate does not describe the whole Browserbase bill.
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] ↗browserbase.com [2] ↗docs.steel.dev [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.
Browserbase: Browserbase's TypeScript Function contract is a reason to retain it when that is the deployed language your team wants. A move to Notte Functions includes a Python execution decision; moving only the browser can leave your existing controller in place.
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.
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.notte.cc [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗notte.cc [4] ↗docs.browserbase.com [5] ↗docs.browserbase.com [6] ↗docs.browserbase.com [7] ↗browserbase.com [8] ↗docs.steel.dev [9] ↗docs.steel.dev [10] ↗docs.steel.dev [11] ↗docs.steel.dev [12] ↗
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.