The job and its deciding constraint
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.
Environment variables, model secret aliases and browser-side credential fill expose values to different components. The destination website still receives the value needed to authenticate.
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. |
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 | Kernel | Anchor Browser |
|---|---|---|---|
| Saved browser state | Documented | Documented | Documented |
| Credential handling | Documented | Vaults (preview) | Managed identities |
| Website sign-in | Documented | Documented | Documented |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗kernel.sh [3] ↗kernel.sh [4] ↗docs.anchorbrowser.io [5] ↗docs.anchorbrowser.io [6] ↗
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.
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.
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.
Sources: docs.notte.cc [1] ↗kernel.sh [2] ↗docs.anchorbrowser.io [3] ↗
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.
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.
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.
Sources: docs.notte.cc [1] ↗kernel.sh [2] ↗docs.anchorbrowser.io [3] ↗
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.
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.
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] ↗kernel.sh [2] ↗anchorbrowser.io [3] ↗
What should change the choice?
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.
Kernel: 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.
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 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.
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗notte.cc [3] ↗kernel.sh [4] ↗kernel.sh [5] ↗kernel.sh [6] ↗docs.anchorbrowser.io [7] ↗docs.anchorbrowser.io [8] ↗anchorbrowser.io [9] ↗
Make a bounded pilot
Trace the credential through the supported fill path, inspect the declared exposure boundary, and verify that ordinary model prompts and application logs do not contain the raw value.
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.
- 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.