Decide whether this move earns its cost

A customer authorizes an application to operate an existing website account. The application must distinguish a usable connection from a browser that merely started.

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 Managed Auth is relevant when a saved website connection and its readiness check should precede browser execution. A profile and a credential vault remain distinct resources.

Another provider's managed-auth flow can be the better fit when it already supports the application's consent and handoff experience. Confirm supported websites and the actual user path rather than comparing the feature name.

Keep the result contract stable

A consenting test user, the intended website account and an application-owned connection mapping.

The task waits for a usable connection and verifies the expected account before taking an action on the customer's behalf.

Preserve the evidence contract across the move: Consenting application user, intended account, connection reference and readiness outcome.

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.

Inventory the source connection's owner and the actions the user authorized.
Create a target connection through an authorized user flow instead of copying provider-owned IDs.
Verify readiness, account identity and the user handoff before moving customer 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 consenting test user, the intended website account and an application-owned connection mapping.
Pass condition	The task waits for a usable connection and verifies the expected account before taking an action on the customer's behalf.
Negative case	Start a test with a connection that is not ready. The browser workflow must stop or request the required user step rather than acting in an anonymous or different account.
Evidence to retain	Consenting application user, intended account, connection reference and readiness outcome.

A reason to delay or keep the source

Start a test with a connection that is not ready. The browser workflow must stop or request the required user step rather than acting in an anonymous or different account.

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.