Can the provider start and run the fleet you need?
Concurrent sessions, session creation rate and HTTP request rate are different limits. A plan that allows a hundred open browsers may still need time to start them. Polling or retrying without a budget can exhaust API capacity before the browser cap is reached.
If a thousand jobs arrive together but only fifty browser slots are available, queue jobs before allocating browsers. Starting all jobs immediately can turn ordinary capacity management into timeouts, retries and idle browser charges.
Compare operational limits
Notte: The public plans list 5, 25 and 100 concurrent browser sessions, with custom limits on Enterprise. Session duration and concurrent capacity are separate plan limits; a larger technical API limit does not override the plan.
Tilion: Arena's observed test concurrency is a test configuration, not an account entitlement. Obtain the production concurrency and session creation limits for your access tier before sizing a fleet.
Sources: notte.cc [1] ↗tilion.com [2] ↗
Compare the browser lifecycle
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] ↗
Compare the billing contract
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] ↗
How to evaluate this choice
A quota table establishes what an account may request. A measured concurrency curve establishes how the tested workload behaved. Keep both in the decision and avoid extrapolating a single-session result to a large fleet.
- Specify the number of simultaneously open browsers and the burst arrival rate.
- Measure time until every requested browser is ready for work.
- Record rate limits and honor the returned retry delay.
- Cap worker concurrency and keep queued tasks outside browser sessions.
- Include failed starts and cleanup in the load test's result.
Requirements side by side
| Requirement | Notte | Tilion |
|---|---|---|
| Browser control | Documented | Arena integration |
| Saved browser state | Documented | Not established |
| Code execution | Python Functions | 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] ↗docs.notte.cc [5] ↗docs.notte.cc [6] ↗tilion.com [7] ↗
Which approach fits?
Choose Notte when your browser workflow needs saved logins, credential fill or scheduled Python code alongside the browser.
Notte tradeoff: A saved profile restores browser state; it does not prove that a website still considers the user signed in. Use Managed Auth when the workflow needs connection readiness before it starts.
Choose Tilion when you can obtain access and test the product directly, with its current API and commercial terms in hand.
Tilion tradeoff: Arena measurements do not establish public availability or feature completeness. Confirm access, API details and plan terms before planning a production migration.
Sources: docs.notte.cc [1] ↗tilion.com [2] ↗
A useful acceptance check
Write a pass/fail result for the real task before running the evaluation. Record the account, configuration and code version next to that result. Repeat failures need an explanation, not an automatically different browser configuration.