The workflow decision
For browser upload workflows, the useful comparison is whether Notte or Steel can meet the following outcome: The website exposes a completed destination object containing the expected marker, and the application stores its identifier.
The controller needs a supported way to deliver the file to the browser environment. A path on an external worker is not automatically a path on the remote browser host.
A proposed acceptance case
A browser uploads a permitted file and submits a form. The application needs evidence that the website created the intended object from that file.
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 small test file with a known marker, an authorized account and an expected destination record. |
| Pass condition | The website exposes a completed destination object containing the expected marker, and the application stores its identifier. |
| Negative case | Use a controlled rejected file. The job must capture the rejection and avoid treating a successful file-picker interaction as a submitted record. |
| Evidence to retain | Source file marker, upload outcome and final website object ID. |
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] ↗
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?
Consider Notte when the upload is one step in a browser workflow that also needs authenticated state or Python execution. Prove the exact file-input and staging path on the target site first.
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 the current provider when its file staging and browser input behavior are essential and already verified. Provider file references are not portable merely because both browsers accept CDP commands.
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗notte.cc [3] ↗docs.steel.dev [4] ↗docs.steel.dev [5] ↗docs.steel.dev [6] ↗
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: Source file marker, upload outcome and final website object ID.
Sources: notte.cc [1] ↗docs.steel.dev [2] ↗
Make a bounded pilot
Upload a known test file, inspect the website's resulting object, and keep the source file isolated from unrelated sessions.
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 same source file and destination record check for the pilot.
- Replace provider file staging separately from form submission.
- Verify rejection handling and target record creation before moving real uploads.