The job and its deciding constraint
A signed-in job requests a report from a website and transfers the completed file to application storage. A download beginning is not the delivery outcome.
A successful click does not establish that the download completed or that the file survives session cleanup. Browser profile persistence does not imply persistent downloaded files.
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 controlled report with a known filename, expected content marker and application-owned destination. |
| Pass condition | The application receives the complete expected file, verifies its content marker and associates it with the originating account and job. |
| Negative case | Close the browser before a deliberately delayed download completes. The job must detect the missing or partial artifact instead of reporting a delivered report. |
| Evidence to retain | Website report ID, file byte count, content verification and destination object reference. |
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 belongs on the shortlist when saved account state and an executable browser workflow simplify the report job. Confirm the chosen file-transfer API and storage boundary in the current docs before moving the delivery step.
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.
A working download-to-storage pipeline is a reason to retain the current provider until an equivalent artifact path is demonstrated. Neither a replay nor a successful page navigation proves that a file arrived.
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
Check download completion, file type, byte count and application access before stopping the session; verify retained results afterward.
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.
- Separate website report generation from provider file retrieval in the current code.
- Keep the destination and content check unchanged while replacing the retrieval path.
- Test delayed and interrupted downloads before switching scheduled report delivery.