Decide whether this move earns its cost

A recurring job returns to the same website account in a later browser session. A stored profile must restore the intended user without assuming the website login is still valid.

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 profiles are relevant for restoring cookies and web storage. Add its managed connection flow when the requirement includes login readiness rather than state restoration alone.

Keep a source profile or context integration when its documented storage behavior is essential and already verified. State should move only through a supported export/import contract or a fresh authorized login.

Keep the result contract stable

An authorized account, its expected identity marker and two separately created browser sessions.

The second session reaches a protected page as the expected account after loading the target provider's saved-state resource.

Preserve the evidence contract across the move: Expected account, source and target state references, second-session identity and expired-login result.

Map the workflow's resources

Requirement	Kernel	Notte
Saved browser state	Documented	Documented
Credential handling	Vaults (preview)	Documented
Website sign-in	Documented	Documented

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

What survives a session

Kernel: Profiles preserve browser user-data-directory state, including cookies, site data, tabs and preferences. Profile sharing and save behavior need explicit treatment when parallel workers use seeded state.

Notte: Profiles save cookies, local storage and session storage. Sessions start with fresh state by default. Persisting a profile writes state back when the session ends; a running session can also save its state explicitly.

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

Website login

Kernel: Managed Auth handles website login and eligible connection recovery. Vault fill is a separate flow for applications that control navigation and form submission; the reviewed vault documentation labels that surface as preview.

Notte: Vaults substitute credential placeholders in supported browser actions outside the model context. Managed Auth checks requested saved connections before automation. Personas supply an inbox and optional phone number for verification workflows.

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 the source account-to-profile mapping without treating its identifier as portable.
Establish an authorized login in a target session and save it using the target profile contract.
Verify the account in a second target session and in an expired-login test before changing recurring 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	An authorized account, its expected identity marker and two separately created browser sessions.
Pass condition	The second session reaches a protected page as the expected account after loading the target provider's saved-state resource.
Negative case	Invalidate the test website login between sessions. The workflow must detect the expired account state before performing the task.
Evidence to retain	Expected account, source and target state references, second-session identity and expired-login result.

A reason to delay or keep the source

Invalidate the test website login between sessions. The workflow must detect the expired account state before performing the task.

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.