What Browser Use supplies
Browser Use has separate hosted-browser and hosted-agent paths. For browser infrastructure, create a browser and connect your own code over CDP. Profiles and secret bindings handle different parts of authenticated work.
You use Browser Use's framework or want its hosted browsers while retaining the option of a hosted browser agent.
This is a source-based buying guide, not a claim of hands-on testing across every documented feature. Follow the source for the product and plan you would actually use.
Sources: docs.browser-use.com ↗
Browser control
Browser Use: The V4 browser API creates a browser with a CDP URL. Your Playwright or Browser Use code can connect directly. Stopping the browser requires the browser API; closing CDP alone does not stop it.
Sources: docs.browser-use.com ↗
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.
Sources: docs.browser-use.com ↗
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.
Sources: docs.browser-use.com ↗
Where the code runs
Browser Use: The cloud offers hosted-agent runs and separately created browsers. The reviewed browser documentation does not establish a deploy-your-own Python Function equivalent. Keep an external script runner separate from a hosted agent when comparing execution ownership.
Sources: docs.browser-use.com ↗
Deployment ownership
Browser Use: Use the hosted browser from your own process or send a task to the hosted agent. The open-source local framework is another deployment option and should not be equated with the cloud subscription.
Sources: docs.browser-use.com ↗
Capacity and limits
Browser Use: The concurrency guide distinguishes concurrent browser capacity from the HTTP request budget. Keys in a project share capacity and credits. Polling frequency can exhaust request capacity even when there are free browser slots.
Sources: docs.browser-use.com ↗
Inspecting a run
Browser Use: Browser Use documents live preview and recording. Recording availability follows the browser lifecycle and processing state; a live URL is for an active browser rather than a permanent replay link.
Sources: docs.browser-use.com ↗
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.
Sources: docs.browser-use.com ↗
Where Notte is worth evaluating
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.
Notte combines cloud browser sessions with deployed Python automations and website authentication tools. You can control the browser over CDP or use Notte's actions, then deploy repeated work as a Function.
Retaining Browser Use can be the right outcome when its documented model already fits the application. Compare Notte only against a concrete missing capability, operating responsibility or cost constraint.
Sources: docs.browser-use.com [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗
Questions to settle before buying
A hosted-agent run is a different execution unit from your deployed browser script. Keep comparisons focused on the browser path when measuring session speed and price.
Ask for the exact session, state and execution contract of the proposed account. A published browser observation does not establish feature availability, supported websites or production access.
- Which workload must pass before purchase?
- Who owns the running code, stored browser state and website connection?
- Which browser and handler limits apply to the selected plan?
- What does the invoice include beyond browser usage?
- What would have to be rebuilt to leave this provider?