What Browserbase supplies
Browserbase provides managed browser sessions and TypeScript Functions that run next to a browser. Contexts preserve browser state, while its identity and secret tools address different parts of the sign-in workflow.
You want to deploy TypeScript browser logic or already use Browserbase's browser and Stagehand tooling.
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.browserbase.com ↗
Browser control
Browserbase: Create a managed browser session and connect a supported browser library to its connection URL. The session API and the browser connection have separate lifecycles.
Sources: docs.browserbase.com ↗
What survives a session
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.
Sources: docs.browserbase.com ↗
Website login
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.
Sources: docs.browserbase.com ↗
Where the code runs
Browserbase: A Function is TypeScript code published with an entry point. Invocation starts asynchronously, creates a browser, passes its connection URL to the handler, and stores the result, logs and session ID. Function webhooks report status changes.
Sources: docs.browserbase.com ↗
Deployment ownership
Browserbase: Publish TypeScript Functions through the supported deployment flow. The reviewed Function overview lists us-west-2 availability; this is narrower than assuming every browser region also hosts Functions.
Sources: docs.browserbase.com ↗
Capacity and limits
Browserbase: Browser and Function constraints have separate documentation. Check the account's concurrent browser limit, the Function runtime cap and the Function region rather than assuming a browser entitlement covers every execution path.
Sources: docs.browserbase.com ↗
Inspecting a run
Browserbase: Browserbase documents live session views, recordings and observability. Function results also include a session association, so correlate the handler outcome with the actual browser run.
Sources: docs.browserbase.com ↗
Pricing model
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: browserbase.com ↗
Where Notte is worth evaluating
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.
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 Browserbase 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.browserbase.com [1] ↗docs.browserbase.com [2] ↗docs.notte.cc [3] ↗docs.notte.cc [4] ↗
Questions to settle before buying
An identity feature, a persisted Context and a Function secret solve different problems. Select the required combination instead of treating all three as automatic login.
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?