How does the browser get into the right account?
Website authentication crosses several boundaries: the user who authorizes access, the system that holds credentials, the browser that submits them, and any model or code driving the page. Reusing a login and collecting a new identity are separate workflows.
For a customer-facing app, associate each stored connection with the correct application user before opening a browser. Reusing another user's profile can produce a technically successful run in the wrong account.
Compare the login path
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.
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.
Sources: docs.notte.cc [1] ↗tilion.com [2] ↗
Compare saved 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.
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.
Sources: docs.notte.cc [1] ↗tilion.com [2] ↗
Compare the evidence from a run
Notte: Live view shows an active browser and can be embedded in an application. Recordings let you review a finished session. Function runs have their own history and results, so keep the run ID alongside the browser session ID.
Tilion: The reviewed public homepage does not establish live view, replay or artifact retention. For production evaluation, request those capabilities explicitly and inspect a real failed workflow with the provider.
Sources: docs.notte.cc [1] ↗tilion.com [2] ↗
How to evaluate this choice
Compare the concrete login path. A vault can fill a secret while your code controls the workflow; a managed connection may own more of the login process. Neither should be described as a universal guarantee that every website remains signed in.
- Identify whether the task uses an existing account or creates an approved new identity.
- Separate profile restoration from credential fill and connection readiness.
- Document which component can access credential values and which only handles references.
- Verify the expected tenant and account after login.
- Provide a human handoff when the website requires user interaction.
Requirements side by side
| Requirement | Notte | Tilion |
|---|---|---|
| Saved browser state | Documented | Not established |
| Credential handling | Documented | Not established |
| Website sign-in | Documented | Not established |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗docs.notte.cc [4] ↗docs.notte.cc [5] ↗docs.notte.cc [6] ↗tilion.com [7] ↗
Which approach fits?
Choose Notte when your browser workflow needs saved logins, credential fill or scheduled Python code alongside the browser.
Notte tradeoff: A saved profile restores browser state; it does not prove that a website still considers the user signed in. Use Managed Auth when the workflow needs connection readiness before it starts.
Choose Tilion when you can obtain access and test the product directly, with its current API and commercial terms in hand.
Tilion tradeoff: Arena measurements do not establish public availability or feature completeness. Confirm access, API details and plan terms before planning a production migration.
Sources: docs.notte.cc [1] ↗tilion.com [2] ↗
A useful acceptance check
Write a pass/fail result for the real task before running the evaluation. Record the account, configuration and code version next to that result. Repeat failures need an explanation, not an automatically different browser configuration.