The workflow decision
For short browser tools, the useful comparison is whether Notte or Kernel can meet the following outcome: The caller receives the expected page identity and the session is released; record elapsed time from allocation through release.
Session startup and minimum billing can dominate a short task. Reuse a session only when the task's isolation and state requirements allow it.
A proposed acceptance case
A caller asks for the title and canonical URL of one public page, then discards the browser. The browser has no reason to keep account state after returning that result.
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 public test URL and an expected title, supplied before either provider is run. |
| Pass condition | The caller receives the expected page identity and the session is released; record elapsed time from allocation through release. |
| Negative case | Point the tool at a controlled unavailable page. It must report a failed task and release the browser rather than returning an empty success. |
| Evidence to retain | Expected and observed page identity, allocation-to-release duration, terminal session status. |
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 | Kernel |
|---|---|---|
| Browser control | Documented | Documented |
| Saved browser state | Documented | Documented |
| Live view | Documented | Documented |
| Deployment choice | Enterprise options | Check deployment offering |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗docs.notte.cc [4] ↗kernel.sh [5] ↗kernel.sh [6] ↗kernel.sh [7] ↗kernel.sh [8] ↗
Browser control
Notte: Create an owned browser session, connect Playwright or Puppeteer over CDP, and stop the session when the work finishes. Browser lifecycle management remains necessary even when the control socket disconnects.
Kernel: Kernel exposes browser creation and control APIs. Its documentation distinguishes on-demand browsers from configured browser pools, so compare the acquisition path your application will actually use.
Sources: docs.notte.cc [1] ↗kernel.sh [2] ↗
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.
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] ↗kernel.sh [2] ↗
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.
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.
Sources: notte.cc [1] ↗kernel.sh [2] ↗
The measured lifecycle starting point
The saved lifecycle observation includes creation, connection, navigation and release at concurrency one. It helps select a short-tool pilot; it does not predict this workflow's latency or fleet behavior.
Task completion below comes from the separate throughput workload. Preserve its date and failure context; a low usage rate or fast lifecycle does not establish that an authenticated business job completes. BrowserArena is maintained by Notte.
| Provider | Lifecycle median | Lifecycle run | Throughput task completion |
|---|---|---|---|
| Notte | 332 ms | 2026-10-18 | 91% on 2026-10-18 |
| Kernel | 334 ms | 2026-10-18 | 69% on 2026-10-17 |
Sources: browserarena.ai [1] ↗browserarena.ai [2] ↗notte.cc [3] ↗kernel.sh [4] ↗
What should change the choice?
Notte is worth shortlisting when CDP control and a low browser-hour rate fit a caller that already owns its execution loop. Its lifecycle observation is relevant here because acquisition happens on every call.
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.
Keep the current provider when the complete tool already meets its latency and cost budget. A new connection URL is not valuable enough by itself to justify moving a working integration.
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗notte.cc [3] ↗kernel.sh [4] ↗kernel.sh [5] ↗kernel.sh [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: Expected and observed page identity, allocation-to-release duration, terminal session status.
Sources: notte.cc [1] ↗kernel.sh [2] ↗
Make a bounded pilot
Record the complete create, connect, navigate and release lifecycle, with a correctness check on the returned result.
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.
- Keep the existing page-reading logic and replace only session allocation and release.
- Compare the returned title and canonical URL before comparing timing.
- Canary the new provider with fresh sessions and count failed starts in the tool budget.