The workflow decision
For browsers inside a multi-user app, the useful comparison is whether Notte or Browserbase can meet the following outcome: Each browser returns its own expected tenant identity, including after saved state is restored in a later session.
Tenant identity and stored browser state must follow the application user. Browser concurrency is shared capacity; it is not authorization to share one user's profile with another.
A proposed acceptance case
Two application users connect accounts on the same website. Their tasks run in parallel and must return results from the correct account every time.
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 | Two authorized test accounts with visibly different tenant identifiers and separate application users. |
| Pass condition | Each browser returns its own expected tenant identity, including after saved state is restored in a later session. |
| Negative case | Deliberately supply the other user's connection reference in a controlled test. The application must reject the mismatch before taking an account-changing action. |
| Evidence to retain | Application user ID, expected tenant, provider resource references and verified tenant, without credential values. |
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 |
|---|---|---|
| Saved browser state | Documented | Contexts |
| Credential handling | Documented | Identity / Secrets |
| Website sign-in | Documented | Website auth tools |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗docs.browserbase.com [3] ↗docs.browserbase.com [4] ↗
Website login
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.
Browserbase: The identity documentation covers website authentication and reuse of login state. Contexts and Function Secrets serve different roles: retained browser state versus values available to executing code.
What survives a session
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.
Browserbase: Contexts preserve browser data between sessions. Associate the intended Context with each user's browser and decide which sessions may update it; a Context is distinct from a live running session.
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.
Sources: notte.cc [1] ↗browserbase.com [2] ↗
What should change the choice?
Notte's profiles, vaults and managed connections are relevant when account resources need to follow an application user. Your own application still has to enforce the user-to-resource mapping.
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.
Retain the current integration if its account isolation is already verified and the proposed replacement does not simplify a concrete ownership problem. A different profile object name is not an isolation improvement.
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗notte.cc [3] ↗docs.browserbase.com [4] ↗docs.browserbase.com [5] ↗browserbase.com [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: Application user ID, expected tenant, provider resource references and verified tenant, without credential values.
Sources: notte.cc [1] ↗browserbase.com [2] ↗
Make a bounded pilot
Start two users' workflows in parallel and verify the account identity, connection ownership and resulting artifacts independently.
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.
- Inventory user-to-profile and user-to-connection mappings without copying secret values into the inventory.
- Establish target resources separately for each test user.
- Compare tenant identity after parallel runs and a later restored session before expanding the canary.