The workflow decision
For long-running browser Functions, the useful comparison is whether Notte or Tilion can meet the following outcome: The application can determine the execution's terminal state and browser ownership after the caller stops waiting, then retrieve or cancel work through the documented path.
Handler runtime, browser lifetime and client waiting time are separate clocks. A client timeout does not necessarily cancel server-side execution or release its browser.
A proposed acceptance case
A deployed handler performs browser work longer than the caller is willing to wait. The execution must have an observable outcome even after the request ends.
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 safe delayed handler, a short caller wait budget and a stored execution reference. |
| Pass condition | The application can determine the execution's terminal state and browser ownership after the caller stops waiting, then retrieve or cancel work through the documented path. |
| Negative case | Interrupt the caller and request cancellation in a controlled test. Inspect both the handler outcome and whether its browser remains allocated. |
| Evidence to retain | Caller timeout, execution reference, handler terminal state, cancellation result and browser release. |
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 |
|---|---|---|
| Code execution | Python Functions | Not established |
| Scheduled execution | Native | Not established |
| Recordings / replay | Documented | Not established |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗tilion.com [3] ↗
Where the code runs
Notte: Functions deploy Python code with a run() entry point. Invoke them over HTTP or with an SDK, inspect run history, and roll back code by redeploying an earlier version as the latest version.
Tilion: Public documentation reviewed for this comparison does not establish a deployable Function or app-action contract. Confirm where your automation code runs and how invocation, versioning and logs work before choosing the execution path.
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 worth evaluating when a Python handler's run history can replace ad hoc background-job tracking. Confirm the actual runtime and cancellation contract rather than borrowing browser session limits.
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.
An existing worker or provider execution service may fit a long task better when its runtime and cancellation behavior are already proven. A successful browser connection is not a runtime entitlement.
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗notte.cc [3] ↗tilion.com [4] ↗
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: Caller timeout, execution reference, handler terminal state, cancellation result and browser release.
Sources: notte.cc [1] ↗tilion.com [2] ↗
Make a bounded pilot
Use a safe controlled run to inspect status after the caller stops waiting, then cancel through the supported path and verify terminal cleanup.
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 source caller, handler and browser timeouts as separate budgets.
- Port the handler without changing the business completion check.
- Prove post-timeout status lookup, cancellation and browser cleanup before moving long jobs.