The workflow decision
For credential isolation, the useful comparison is whether Notte or Browserbase can meet the following outcome: The website authenticates the test account and the observed credential path matches the declared exposure boundary.
Environment variables, model secret aliases and browser-side credential fill expose values to different components. The destination website still receives the value needed to authenticate.
A proposed acceptance case
A browser submits a credential while the application restricts which models, processes and logs receive its raw value. The destination website still needs the submitted secret.
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 disposable test credential, the intended fill path and an explicit list of components allowed to handle its value. |
| Pass condition | The website authenticates the test account and the observed credential path matches the declared exposure boundary. |
| Negative case | Inspect controlled prompts and ordinary application logs after the test. Fail the evaluation if the test secret appears outside the components intentionally allowed to handle it. |
| Evidence to retain | Approved component boundary, secret reference, fill result and exposure-check outcome; never the raw value. |
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 vault placeholders are relevant when supported browser actions should substitute credentials outside the model context. Function secrets and application environment variables have a different exposure boundary.
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.
Keep an established secret manager integration when its exposure boundary and browser fill path already meet the requirement. A placeholder feature should not be assumed to protect arbitrary application code.
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: Approved component boundary, secret reference, fill result and exposure-check outcome; never the raw value.
Sources: notte.cc [1] ↗browserbase.com [2] ↗
Make a bounded pilot
Trace the credential through the supported fill path, inspect the declared exposure boundary, and verify that ordinary model prompts and application logs do not contain the raw value.
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.
- Trace the source credential path before changing the secret store or browser.
- Provision a target test secret through the supported path and use its reference in the browser workflow.
- Inspect prompts, logs and account identity before moving real credential-dependent tasks.