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
Kernel: Kernel documents concurrent browsers, browser creation rate and per-browser resources separately. Standby browsers can still consume concurrency. Pools change how browsers are acquired; they do not erase account limits.
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: kernel.sh [1] ↗tilion.com [2] ↗
Compare the browser lifecycle
Kernel: Kernel exposes browser creation and control APIs. Its documentation distinguishes on-demand browsers from configured browser pools, so compare the acquisition path your application will actually use.
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: kernel.sh [1] ↗tilion.com [2] ↗
Compare the billing contract
Kernel: Use the plan and browser configuration in Kernel's pricing documentation. Managed networking, account allowances and app execution make a browser-hour comparison only one part of the decision.
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: kernel.sh [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 | Kernel | Tilion |
|---|---|---|
| Browser control | Documented | Arena integration |
| Saved browser state | Documented | Not established |
| Code execution | TypeScript / Python Apps | Not established |
| Deployment choice | Check deployment offering | Not established |
Sources: kernel.sh [1] ↗kernel.sh [2] ↗kernel.sh [3] ↗kernel.sh [4] ↗kernel.sh [5] ↗kernel.sh [6] ↗tilion.com [7] ↗
Which approach fits?
Choose Kernel when your code makes many browser calls and you want to deploy it beside the browser, or you need Kernel's managed sign-in flow.
Kernel tradeoff: Browser-local code changes the deployment model. Check app action behavior, account limits and persistent-state ownership before moving an external worker into it.
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: kernel.sh [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.
When Notte belongs on this shortlist
Kernel's browser-local Apps make execution placement part of the decision. Compare the repeated action path with the proposed Notte controller or Function deployment before concluding that a lifecycle or hourly-rate difference decides the workflow.
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: 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.
Consider this third option when its documented mechanism addresses a requirement left open by the two providers above. A working configuration on either original provider can still be the better choice; compare the task and ownership cost before switching.