Decide whether this move earns its cost

An application event causes a browser operation. Delivery can be repeated, while the browser may finish after the original HTTP caller stops waiting.

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.

Consider Notte when an HTTP-invoked Python Function can own the browser task and expose its run history. Your application still needs its own event identity and duplicate-delivery policy.

A TypeScript Function, browser-local action or existing external worker may be the better fit when it already integrates with the event system. Moving the browser does not require moving every webhook handler.

Keep the result contract stable

A test event with a stable application event ID and an operation whose resulting object can be counted.

The application tracks a terminal run and the intended number of website changes for that event, including after duplicate delivery.

Preserve the evidence contract across the move: Event ID, invocation acknowledgement, execution ID, terminal state and resulting website object.

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.

Preserve the application's event ID when replacing invocation plumbing.
Invoke the target from a test event and track its terminal result separately from the initial response.
Route one event partition to the target and keep duplicate handling enabled during cutover.

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 test event with a stable application event ID and an operation whose resulting object can be counted.
Pass condition	The application tracks a terminal run and the intended number of website changes for that event, including after duplicate delivery.
Negative case	Send the same event twice and interrupt the first caller. Verify that run tracking and idempotency still describe the intended outcome.
Evidence to retain	Event ID, invocation acknowledgement, execution ID, terminal state and resulting website object.

A reason to delay or keep the source

Send the same event twice and interrupt the first caller. Verify that run tracking and idempotency still describe the intended outcome.

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.