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.
Lightpanda introduces a browser-engine decision. Keep it on the shortlist when its supported actions fit the real pages you use; a successful CDP connection or text task does not establish visual or full-browser equivalence with the proposed Notte 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 | Lightpanda | Notte |
|---|---|---|
| Saved browser state | Not established | Documented |
| Credential handling | Application-owned | Documented |
| Website sign-in | Not established | Documented |
Sources: lightpanda.io [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗
What survives a session
Lightpanda: The reviewed cloud documentation does not establish a durable profile contract covering cookies and web storage. Determine how the required browser state is saved and restored before moving an authenticated workflow.
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.
Website login
Lightpanda: Browser engine compatibility and website authentication are separate requirements. The reviewed sources do not establish a managed website-auth connection equivalent; verify the login and verification flow on the target sites.
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.
Pricing model
Lightpanda: Use the cloud billing unit and account limits for hosted access. A lower rate only helps if the target pages and required actions complete correctly on the selected engine.
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: lightpanda.io [1] ↗notte.cc [2] ↗
Cut over one responsibility at a time
For this Lightpanda-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: lightpanda.io [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.
Lightpanda: CDP connectivity does not establish complete Chromium compatibility. Validate rendering-dependent steps, downloads and browser features with the selected engine before a migration.
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.
Sources: lightpanda.io [1] ↗notte.cc [2] ↗