Where does the browser automation code run?
An external worker, a hosted browser Function, a browser-local app action and a hosted agent are different execution models. The choice determines who deploys the code, starts the browser, records the result and stops the run.
A scheduled job should return a verified result and stop its owned browser even when an action fails. The scheduler's successful HTTP trigger is not proof that the browser completed the business operation.
Compare the execution model
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.
Kernel: Deploy a TypeScript or Python App and expose Actions that callers invoke. Kernel co-locates code with the browser environments the app creates. An Action invocation is the execution unit rather than a bare CDP connection.
Compare 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.
Kernel: Kernel Apps move the automation process next to the browser. Alternatively, an external process can control a browser through the browser API. Choose based on execution locality and deployment ownership.
Compare the evidence from 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.
Kernel: Live browser URLs support an embedded view and a read-only option. Replays and browser telemetry are separate observability surfaces; app invocation logs add execution context.
How to evaluate this choice
Keep an external runner when you already operate one and need portability. A native execution layer can remove deployment work; browser-local code can reduce repeated network calls. Compare actual workload behavior before assuming either always wins.
- Confirm the supported language, entry point and dependency packaging.
- Trace deployment, version selection, invocation and cancellation.
- Keep the handler runtime limit separate from browser session duration.
- Decide whether scheduling is native or supplied by another service.
- Associate results and logs with both the code version and browser session.
Requirements side by side
| Requirement | Browserbase | Kernel |
|---|---|---|
| Code execution | TypeScript Functions | TypeScript / Python Apps |
| Scheduled execution | External trigger path | App invocation path |
| Recordings / replay | Documented | Documented |
Sources: docs.browserbase.com [1] ↗docs.browserbase.com [2] ↗docs.browserbase.com [3] ↗docs.browserbase.com [4] ↗docs.browserbase.com [5] ↗kernel.sh [6] ↗kernel.sh [7] ↗kernel.sh [8] ↗kernel.sh [9] ↗kernel.sh [10] ↗kernel.sh [11] ↗
Which approach fits?
Choose Browserbase when you want to deploy TypeScript browser logic or already use Browserbase's browser and Stagehand tooling.
Browserbase tradeoff: 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.
Choose Kernel when your code makes many browser calls and you want to deploy it beside the browser, or you need Kernel's managed sign-in flow.
Kernel tradeoff: Browser-local code changes the deployment model. Check app action behavior, account limits and persistent-state ownership before moving an external worker into it.
A useful acceptance check
Write a pass/fail result for the real task before running the evaluation. Record the account, configuration and code version next to that result. Repeat failures need an explanation, not an automatically different browser configuration.
When Notte belongs on this shortlist
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.
Kernel's browser-local Apps make execution placement part of the decision. Compare the repeated action path with the proposed Notte controller or Function deployment before concluding that a lifecycle or hourly-rate difference decides the workflow.
Notte: Functions deploy Python code with a run() entry point. Invoke them over HTTP or with an SDK, inspect run history, and roll back code by redeploying an earlier version as the latest version.
Consider this third option when its documented mechanism addresses a requirement left open by the two providers above. A working configuration on either original provider can still be the better choice; compare the task and ownership cost before switching.
Sources: docs.browserbase.com [1] ↗kernel.sh [2] ↗docs.notte.cc [3] ↗