The workflow decision
For debugging recorded browser runs, the useful comparison is whether Notte or Tilion can meet the following outcome: An investigator can find the correct run, identify the failing step and reconcile the recording with the application's terminal status.
The recording mode, retention and session identifiers determine what can be reconstructed. Some artifacts become available only after the browser stops or processing finishes.
A proposed acceptance case
A support engineer investigates a failed job after the browser has ended. The recording must be connected to the input, execution version and final result.
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 harmless workflow with one deliberately failing step and recording enabled through the documented mechanism. |
| Pass condition | An investigator can find the correct run, identify the failing step and reconcile the recording with the application's terminal status. |
| Negative case | Create a run with the wrong recording configuration in a test environment. The system must expose the missing artifact rather than linking a different run as evidence. |
| Evidence to retain | Job input reference, code version, session ID, recording reference and terminal 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 | Tilion |
|---|---|---|
| Browser control | Documented | Arena integration |
| Saved browser state | Documented | Not established |
| Live view | Documented | Not established |
| Deployment choice | Enterprise options | Not established |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗docs.notte.cc [4] ↗tilion.com [5] ↗
Inspecting 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] ↗
Browser control
Notte: Create an owned browser session, connect Playwright or Puppeteer over CDP, and stop the session when the work finishes. Browser lifecycle management remains necessary even when the control socket disconnects.
Tilion: BrowserArena includes a Tilion session integration. The reviewed public Tilion homepage does not publish the full session API contract; obtain the supported connection and lifecycle instructions through its access flow.
Sources: docs.notte.cc [1] ↗tilion.com [2] ↗
Deployment ownership
Notte: Use a remote browser from your existing process or deploy the browser automation as a Notte Function. These choices put lifecycle, scheduling and monitoring responsibilities in different places.
Tilion: The public access path currently points to a waitlist and contact. A production integration needs an agreed API contract, service access and ownership of the browser lifecycle.
Sources: docs.notte.cc [1] ↗tilion.com [2] ↗
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.
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.
Sources: notte.cc [1] ↗tilion.com [2] ↗
What should change the choice?
Notte is relevant when browser recordings and Python run history need to support the same investigation. Confirm artifact availability and retention for the selected account before relying on it for support.
Tilion: 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.
Keep a provider whose existing replay integration already meets the team's investigation needs if the new system would lose necessary artifacts or history. A green feature label does not establish equivalent retention.
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗notte.cc [4] ↗tilion.com [5] ↗
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: Job input reference, code version, session ID, recording reference and terminal result.
Sources: notte.cc [1] ↗tilion.com [2] ↗
Make a bounded pilot
Create a controlled failure, stop the browser correctly, and retrieve the expected replay, logs and application result using the stored run identifiers.
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.
- Preserve source run and replay references for historical jobs.
- Add target session and Function references to newly canaried jobs.
- Have an investigator reconstruct a controlled failure before moving the support workflow.