Decide whether this move earns its cost

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.

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 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.

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.

Keep the result contract stable

A safe delayed handler, a short caller wait budget and a stored execution reference.

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.

Preserve the evidence contract across the move: Caller timeout, execution reference, handler terminal state, cancellation result and browser release.

Map the workflow's resources

Requirement	Tilion	Notte
Code execution	Not established	Python Functions
Scheduled execution	Not established	Native
Recordings / replay	Not established	Documented

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

Where the code runs

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.

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.

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

Deployment ownership

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.

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.

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.

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.

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 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.

A reason to delay or keep the source

Interrupt the caller and request cancellation in a controlled test. Inspect both the handler outcome and whether its browser remains allocated.

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.