The workflow decision
For saved login reuse, the useful comparison is whether Notte or Anchor Browser can meet the following outcome: The second session reaches a protected page as the expected account after loading the target provider's saved-state resource.
Saved state can expire or be invalidated by the website. A profile save response establishes that data was stored, not that the next session is authenticated.
A proposed acceptance case
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.
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. |
Documented mechanisms, side by side
These labels describe product mechanisms. The linked source and the acceptance case determine whether a mechanism meets this workflow's requirement.
| Requirement | Notte | Anchor Browser |
|---|---|---|
| Saved browser state | Documented | Documented |
| Credential handling | Documented | Managed identities |
| Website sign-in | Documented | Documented |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗docs.anchorbrowser.io [3] ↗docs.anchorbrowser.io [4] ↗
What survives a session
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.
Anchor Browser: Anchor documents browser profiles alongside an Applications and Identities model. A profile retains state; an identity supplies a managed sign-in connection used with browser sessions.
Website login
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.
Anchor Browser: Applications define the target website and authentication behavior. Identities attach managed sign-in to sessions. OmniConnect supplies an embeddable flow for end users to sign in from a product.
Pricing model
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.
Anchor Browser: Compare the selected browser and task offering using Anchor's current commercial terms. Include network usage and the execution path actually used; a batch API's capacity is not a price quote for that batch.
Sources: notte.cc [1] ↗anchorbrowser.io [2] ↗
What should change the choice?
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.
Anchor Browser: Anchor's demonstration or prompt-authored Automation Tasks and Notte's Python Functions suit different authoring preferences. Both document website-authentication tooling, so a credible recommendation must address the actual login and workflow-editing path.
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.
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗notte.cc [3] ↗docs.anchorbrowser.io [4] ↗docs.anchorbrowser.io [5] ↗anchorbrowser.io [6] ↗
The cost boundary
Use the same attempted work and eligible account capacity in both estimates. The browser-hour rate does not include every proxy, execution or identity meter, and the cost of an incomplete job is still part of the workflow budget.
The workload evidence should include: Expected account, source and target state references, second-session identity and expired-login result.
Sources: notte.cc [1] ↗anchorbrowser.io [2] ↗
Make a bounded pilot
Save state from an authorized login, start a separate session and verify the exact account on a protected page before running the task.
Use the same authorized account, input and final-state check in each configuration. Treat a missing product contract as an open question; do not turn an undocumented capability into an unsupported claim or a successful test result.
- 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.