What will the same completed work cost?
Start with the work that has to finish: executions per month, browser time per execution, concurrent browsers and network traffic. Choose the cheapest eligible plan for that workload. An hourly rate can be lower while the bill is higher because a plan floor, billing minimum or extra service applies.
For 10,000 runs lasting three minutes, browser time is 500 hours before rounding, setup and retries. At Notte's published $0.01 browser-hour rate, that meter is $5. Paid-plan eligibility and any proxy or Function usage still determine the total bill.
Compare the billing contract
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.
Cloudflare Browser Run: Price browser usage and the Worker execution components required by the workload. The Browser Run pricing page, rather than a single browser-hour estimate, defines included allowances and applicable limits.
Sources: docs.steel.dev [1] ↗developers.cloudflare.com [2] ↗
Compare operational limits
Steel: Steel's pricing and limits page describes hosted account entitlements. For a self-hosted deployment, capacity depends on the resources and orchestration you operate as well as the browser process.
Cloudflare Browser Run: Browser Run has its own limits and pricing alongside Workers. Account browser capacity, session creation limits and the Worker execution budget constrain different parts of a workflow.
Sources: docs.steel.dev [1] ↗developers.cloudflare.com [2] ↗
Compare the execution model
Steel: The reviewed browser documentation establishes sessions, profiles and credentials. It does not establish a hosted Python handler with deployment and invocation APIs. An external worker can control a Steel browser; price and operate that worker separately.
Cloudflare Browser Run: Deploy browser automation within a Cloudflare Worker or connect to Browser Run from an external process over CDP. Workers provide the execution layer; compare their runtime and deployment model separately from browser access.
Sources: docs.steel.dev [1] ↗developers.cloudflare.com [2] ↗
How to evaluate this choice
A useful cost comparison gives both a usage estimate and the eligible monthly plan. Keep an unsupported workload out of the price ranking even if a rate can be multiplied into an attractive number.
- Count attempted runs as well as successful runs.
- Apply the provider's rounding rule to each session before adding usage.
- Separate browser time, function compute, proxy traffic and identity services.
- Apply included credits once; do not add the same subscription fee again.
- Mark an ineligible plan as a capacity mismatch rather than a cheap option.
Requirements side by side
| Requirement | Steel | Cloudflare Browser Run |
|---|---|---|
| Browser control | Documented | Documented |
| Saved browser state | Documented | Session reuse / custom state |
| Code execution | External worker | Workers composition |
| Deployment choice | Documented | Cloudflare service |
Sources: docs.steel.dev [1] ↗docs.steel.dev [2] ↗docs.steel.dev [3] ↗docs.steel.dev [4] ↗docs.steel.dev [5] ↗docs.steel.dev [6] ↗developers.cloudflare.com [7] ↗
Which approach fits?
Choose Steel when you want browser infrastructure that can fit a self-hosted deployment, with profiles and credentials available through browser-focused APIs.
Steel tradeoff: Hosted and self-hosted Steel are different operating choices. A cloud feature's documentation does not establish identical packaging, retention or operational support in a self-hosted installation.
Choose Cloudflare Browser Run when you already deploy Workers and want browser automation within that application's execution and scheduling model.
Cloudflare Browser Run tradeoff: A Worker and a browser session have separate resource and lifecycle constraints. Confirm the chosen browser library and binding path instead of assuming an unchanged local browser script will deploy directly.
Sources: docs.steel.dev [1] ↗developers.cloudflare.com [2] ↗
A useful acceptance check
Write a pass/fail result for the real task before running the evaluation. Record the account, configuration and code version next to that result. Repeat failures need an explanation, not an automatically different browser configuration.
When Notte belongs on this shortlist
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.
Cloudflare can be an economical architectural choice when Workers and the surrounding scheduling already exist in your application. Notte is worth evaluating when a browser, deployed Python handler and authentication workflow should share a product rather than a Workers composition.
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.
Consider this third option when its documented mechanism addresses a requirement left open by the two providers above. A working configuration on either original provider can still be the better choice; compare the task and ownership cost before switching.
Sources: docs.steel.dev [1] ↗developers.cloudflare.com [2] ↗docs.notte.cc [3] ↗