Decide whether this move earns its cost

A team releases a browser automation change, discovers a regression and needs to restore a known implementation while retaining the history of affected runs.

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's Python deployment and run-history layer is relevant when release management belongs with browser execution. Its documented rollback approach redeploys an earlier implementation as the latest version.

Retain another execution platform when its language, dependency packaging or version-selection contract is essential to the application. Similar version numbers do not establish the same invocation semantics.

Keep the result contract stable

Two harmless code versions that return different markers and a recorded invocation for each version.

New runs execute the intended implementation after rollback, while historical runs remain associated with the implementation that actually ran.

Preserve the evidence contract across the move: Deployed implementation marker, invocation configuration, historical run version and rollback result.

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] ↗

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] ↗

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] ↗

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.

Save the source implementation and the version behavior callers rely on.
Deploy two target implementations with visible markers and record which one runs.
Rehearse restoring the earlier implementation before routing production invocations.

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	Two harmless code versions that return different markers and a recorded invocation for each version.
Pass condition	New runs execute the intended implementation after rollback, while historical runs remain associated with the implementation that actually ran.
Negative case	Invoke after changing the latest deployment and check whether the caller runs a pinned or latest version. The application must not infer the executed version from a filename.
Evidence to retain	Deployed implementation marker, invocation configuration, historical run version and rollback result.

A reason to delay or keep the source

Invoke after changing the latest deployment and check whether the caller runs a pinned or latest version. The application must not infer the executed version from a filename.

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.