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.

The reviewed Tilion homepage offers a waitlist and contact route. Arena's tested integration is useful evidence about a run, but a purchasing or migration decision still needs a documented access, state and execution contract; those unknowns must remain visible beside Notte's public docs.

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	Tilion	Notte
Saved browser state	Not established	Documented
Credential handling	Not established	Documented
Website sign-in	Not established	Documented

Sources: tilion.com [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗

Website login

Tilion: The reviewed public material does not establish managed website authentication, credential fill or verification handling. Treat those as open requirements to validate with the provider, not as absent features.

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: tilion.com [1] ↗docs.notte.cc [2] ↗

What survives a session

Tilion: The reviewed public homepage does not establish profile save/restore behavior. Ask for a documented state contract and test the same signed-in workflow across two separate sessions before relying on persistence.

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: tilion.com [1] ↗docs.notte.cc [2] ↗

Pricing model

Tilion: Arena provides an estimated usage rate for its test. The reviewed public homepage does not establish a self-serve production plan, allowances or overage terms. Obtain those terms before quoting a monthly bill.

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: tilion.com [1] ↗notte.cc [2] ↗

Cut over one responsibility at a time

For this Tilion-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: tilion.com [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.

Tilion: Arena measurements do not establish public availability or feature completeness. Confirm access, API details and plan terms before planning a production 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.