The job and its deciding constraint
A deployed handler performs browser work longer than the caller is willing to wait. The execution must have an observable outcome even after the request ends.
Handler runtime, browser lifetime and client waiting time are separate clocks. A client timeout does not necessarily cancel server-side execution or release its browser.
A proposed acceptance case
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 safe delayed handler, a short caller wait budget and a stored execution reference. |
| Pass condition | The application can determine the execution's terminal state and browser ownership after the caller stops waiting, then retrieve or cancel work through the documented path. |
| Negative case | Interrupt the caller and request cancellation in a controlled test. Inspect both the handler outcome and whether its browser remains allocated. |
| Evidence to retain | Caller timeout, execution reference, handler terminal state, cancellation result and browser release. |
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 | Kernel |
|---|---|---|---|
| Code execution | Python Functions | TypeScript Functions | TypeScript / Python Apps |
| Scheduled execution | Native | External trigger path | App invocation path |
| Recordings / replay | Documented | Documented | Documented |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗docs.browserbase.com [3] ↗docs.browserbase.com [4] ↗kernel.sh [5] ↗kernel.sh [6] ↗
Where the code runs
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.
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.
Sources: docs.notte.cc [1] ↗docs.browserbase.com [2] ↗kernel.sh [3] ↗
Deployment ownership
Notte: Use a remote browser from your existing process or deploy the browser automation as a Notte Function. These choices put lifecycle, scheduling and monitoring responsibilities in different places.
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.
Sources: docs.notte.cc [1] ↗docs.browserbase.com [2] ↗kernel.sh [3] ↗
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.
Kernel: Use the plan and browser configuration in Kernel's pricing documentation. Managed networking, account allowances and app execution make a browser-hour comparison only one part of the decision.
What should change the choice?
Notte is worth evaluating when a Python handler's run history can replace ad hoc background-job tracking. Confirm the actual runtime and cancellation contract rather than borrowing browser session limits.
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.
Kernel: 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.
An existing worker or provider execution service may fit a long task better when its runtime and cancellation behavior are already proven. A successful browser connection is not a runtime entitlement.
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗notte.cc [3] ↗docs.browserbase.com [4] ↗browserbase.com [5] ↗kernel.sh [6] ↗kernel.sh [7] ↗kernel.sh [8] ↗
Make a bounded pilot
Use a safe controlled run to inspect status after the caller stops waiting, then cancel through the supported path and verify terminal cleanup.
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.
- Record source caller, handler and browser timeouts as separate budgets.
- Port the handler without changing the business completion check.
- Prove post-timeout status lookup, cancellation and browser cleanup before moving long jobs.