Decide whether this move earns its cost

A browser submits a credential while the application restricts which models, processes and logs receive its raw value. The destination website still needs the submitted secret.

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 vault placeholders are relevant when supported browser actions should substitute credentials outside the model context. Function secrets and application environment variables have a different exposure boundary.

Keep an established secret manager integration when its exposure boundary and browser fill path already meet the requirement. A placeholder feature should not be assumed to protect arbitrary application code.

Keep the result contract stable

A disposable test credential, the intended fill path and an explicit list of components allowed to handle its value.

The website authenticates the test account and the observed credential path matches the declared exposure boundary.

Preserve the evidence contract across the move: Approved component boundary, secret reference, fill result and exposure-check outcome; never the raw value.

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

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

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

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.

Trace the source credential path before changing the secret store or browser.
Provision a target test secret through the supported path and use its reference in the browser workflow.
Inspect prompts, logs and account identity before moving real credential-dependent tasks.

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 disposable test credential, the intended fill path and an explicit list of components allowed to handle its value.
Pass condition	The website authenticates the test account and the observed credential path matches the declared exposure boundary.
Negative case	Inspect controlled prompts and ordinary application logs after the test. Fail the evaluation if the test secret appears outside the components intentionally allowed to handle it.
Evidence to retain	Approved component boundary, secret reference, fill result and exposure-check outcome; never the raw value.

A reason to delay or keep the source

Inspect controlled prompts and ordinary application logs after the test. Fail the evaluation if the test secret appears outside the components intentionally allowed to handle it.

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.