Decide whether this move earns its cost

A team releases a browser automation change, discovers a regression and needs to restore a known implementation while retaining the history of affected runs.

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's Python deployment and run-history layer is relevant when release management belongs with browser execution. Its documented rollback approach redeploys an earlier implementation as the latest version.

Retain another execution platform when its language, dependency packaging or version-selection contract is essential to the application. Similar version numbers do not establish the same invocation semantics.

Keep the result contract stable

Two harmless code versions that return different markers and a recorded invocation for each version.

New runs execute the intended implementation after rollback, while historical runs remain associated with the implementation that actually ran.

Preserve the evidence contract across the move: Deployed implementation marker, invocation configuration, historical run version and rollback result.

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] ↗

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] ↗

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] ↗

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.

Save the source implementation and the version behavior callers rely on.
Deploy two target implementations with visible markers and record which one runs.
Rehearse restoring the earlier implementation before routing production invocations.

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	Two harmless code versions that return different markers and a recorded invocation for each version.
Pass condition	New runs execute the intended implementation after rollback, while historical runs remain associated with the implementation that actually ran.
Negative case	Invoke after changing the latest deployment and check whether the caller runs a pinned or latest version. The application must not infer the executed version from a filename.
Evidence to retain	Deployed implementation marker, invocation configuration, historical run version and rollback result.

A reason to delay or keep the source

Invoke after changing the latest deployment and check whether the caller runs a pinned or latest version. The application must not infer the executed version from a filename.

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.