Decide whether this move earns its cost

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.

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 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.

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.

Keep the result contract stable

A safe delayed handler, a short caller wait budget and a stored execution reference.

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.

Preserve the evidence contract across the move: Caller timeout, execution reference, handler terminal state, cancellation result and browser release.

Map the workflow's resources

Requirement	Kernel	Notte
Code execution	TypeScript / Python Apps	Python Functions
Scheduled execution	App invocation path	Native
Recordings / replay	Documented	Documented

Sources: kernel.sh [1] ↗kernel.sh [2] ↗docs.notte.cc [3] ↗docs.notte.cc [4] ↗

Where the code runs

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.

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.

Sources: kernel.sh [1] ↗docs.notte.cc [2] ↗

Deployment ownership

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.

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.

Sources: kernel.sh [1] ↗docs.notte.cc [2] ↗

Pricing model

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.

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.

Sources: kernel.sh [1] ↗notte.cc [2] ↗

Cut over one responsibility at a time

For this Kernel-to-Notte migration, keep the business assertion outside provider resource management. Source profile, connection, file and execution IDs are not valid target IDs; use a documented transfer path or establish the corresponding resource in Notte.

Retain source job history and a rollback route until the target pilot passes. A migration checklist is not evidence that saved state or runtime behavior is automatically portable.

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.

Sources: kernel.sh [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗

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.

A reason to delay or keep the source

Interrupt the caller and request cancellation in a controlled test. Inspect both the handler outcome and whether its browser remains allocated.

Kernel: Browser-local code changes the deployment model. Check app action behavior, account limits and persistent-state ownership before moving an external worker into it.

Delay cutover when the target's selected plan, required artifact path or supported website-account flow is not established. Resolve that gap before moving real jobs, even if the rate comparison favors the target.