The three-way buying decision
This shortlist starts with Browser Use and Cloudflare Browser Run, then includes Notte as a third implementation path for saved login reuse. A recurring job returns to the same website account in a later browser session. A stored profile must restore the intended user without assuming the website login is still valid.
Saved state can expire or be invalidated by the website. A profile save response establishes that data was stored, not that the next session is authenticated.
A proposed acceptance case
A recurring job returns to the same website account in a later browser session. A stored profile must restore the intended user without assuming the website login is still valid.
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 | An authorized account, its expected identity marker and two separately created browser sessions. |
| Pass condition | The second session reaches a protected page as the expected account after loading the target provider's saved-state resource. |
| Negative case | Invalidate the test website login between sessions. The workflow must detect the expired account state before performing the task. |
| Evidence to retain | Expected account, source and target state references, second-session identity and expired-login 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 | Browser Use | Cloudflare Browser Run | Notte |
|---|---|---|---|
| Saved browser state | Documented | Session reuse / custom state | Documented |
| Credential handling | V4 secret bindings | Application-owned | Documented |
| Website sign-in | Profile / 2FA flows | Not established | Documented |
Sources: docs.browser-use.com [1] ↗docs.browser-use.com [2] ↗developers.cloudflare.com [3] ↗docs.notte.cc [4] ↗docs.notte.cc [5] ↗
What survives a session
Browser Use: Profiles persist cookies, local storage and login state between browsers. Browser settings select a profile for a run. A session's conversation history and a profile's browser state are different resources.
Cloudflare Browser Run: Cloudflare documents reuse of browser sessions and a Durable Objects integration. Keeping a session alive is different from exporting a portable authenticated profile; design the required state store explicitly.
Notte: Profiles save cookies, local storage and session storage. Sessions start with fresh state by default. Persisting a profile writes state back when the session ends; a running session can also save its state explicitly.
Sources: docs.browser-use.com [1] ↗developers.cloudflare.com [2] ↗docs.notte.cc [3] ↗
Website login
Browser Use: V4 secret bindings give credentials aliases and allowed hostnames for use in a run. Profiles reuse existing state; the separate 2FA guide addresses verification during authenticated work.
Cloudflare Browser Run: Use browser code to implement the website's sign-in flow and retain the necessary session state. The reviewed overview does not establish a managed website connection that checks sign-in readiness before a workflow starts.
Notte: Vaults substitute credential placeholders in supported browser actions outside the model context. Managed Auth checks requested saved connections before automation. Personas supply an inbox and optional phone number for verification workflows.
Sources: docs.browser-use.com [1] ↗developers.cloudflare.com [2] ↗docs.notte.cc [3] ↗
Pricing model
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.
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.
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.browser-use.com [1] ↗developers.cloudflare.com [2] ↗notte.cc [3] ↗
What should change the choice?
Notte profiles are relevant for restoring cookies and web storage. Add its managed connection flow when the requirement includes login readiness rather than state restoration alone.
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.
Cloudflare Browser Run: 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.
Keep a source profile or context integration when its documented storage behavior is essential and already verified. State should move only through a supported export/import contract or a fresh authorized login.
Sources: docs.browser-use.com [1] ↗docs.browser-use.com [2] ↗docs.browser-use.com [3] ↗developers.cloudflare.com [4] ↗developers.cloudflare.com [5] ↗docs.notte.cc [6] ↗docs.notte.cc [7] ↗notte.cc [8] ↗
How to remove an option from the shortlist
For this workflow, require the following evidence from Browser Use, Cloudflare Browser Run and Notte: Expected account, source and target state references, second-session identity and expired-login 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.
- The second session reaches a protected page as the expected account after loading the target provider's saved-state resource.
- Invalidate the test website login between sessions. The workflow must detect the expired account state before performing the task.
Sources: docs.browser-use.com [1] ↗developers.cloudflare.com [2] ↗docs.notte.cc [3] ↗
Make a bounded pilot
Save state from an authorized login, start a separate session and verify the exact account on a protected page before running the task.
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 source account-to-profile mapping without treating its identifier as portable.
- Establish an authorized login in a target session and save it using the target profile contract.
- Verify the account in a second target session and in an expired-login test before changing recurring jobs.