How much time does the browser add to a task?
A session creation number measures one API operation. A usable browser also needs a connection and a navigation, and a long-running workflow pays for many actions after startup. Compare lifecycle latency and running-task throughput separately.
A workflow with one navigation and a hundred browser actions may favor a different execution path than a workload that opens and closes a browser for every action. Test both shapes before making a platform-wide speed claim.
Compare the browser lifecycle
Browserbase: Create a managed browser session and connect a supported browser library to its connection URL. The session API and the browser connection have separate lifecycles.
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.
Compare the evidence from a run
Browserbase: Browserbase documents live session views, recordings and observability. Function results also include a session association, so correlate the handler outcome with the actual browser run.
Tilion: The reviewed public homepage does not establish live view, replay or artifact retention. For production evaluation, request those capabilities explicitly and inspect a real failed workflow with the provider.
Compare deployment ownership
Browserbase: Publish TypeScript Functions through the supported deployment flow. The reviewed Function overview lists us-west-2 availability; this is narrower than assuming every browser region also hosts Functions.
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.
How to evaluate this choice
For short tools, lifecycle overhead can dominate. For a browser that stays open, action latency, task completion and drift matter more. Select the measurement that resembles your application.
- Use the same target page, browser configuration and controller workload.
- Record the runner and browser regions, account plan and concurrency.
- Keep the measured sample count and any warmup or retry behavior visible.
- Calculate tail percentiles from per-session totals, not sums of phase percentiles.
- Classify configuration failures before interpreting them as product failures.
Published browser measurements
These are the latest provider runs in the saved BrowserArena snapshot checked on October 18, 2026. Dates and runner environments can differ. A lifecycle test opens, connects, navigates and releases a browser; the throughput test runs a separate browser action sequence. Neither measures managed authentication or deployed Function reliability.
Use these observations to choose what to test in your application. An account-configuration failure, an incompatible page action and a timed-out navigation require different interpretations. BrowserArena is maintained by Notte and publishes its source and methodology.
| Provider | Lifecycle median | Lifecycle P95 | Actions / second | Run dates |
|---|---|---|---|---|
| Browserbase | 600 ms | 638 ms | 3.5 | 2026-10-18 / 2026-10-17 |
| Tilion | 124 ms | 292 ms | 5.49 | 2026-10-18 / 2026-10-17 |
Sources: browserarena.ai [1] ↗browserarena.ai [2] ↗github.com [3] ↗
Which approach fits?
Choose Browserbase when you want to deploy TypeScript browser logic or already use Browserbase's browser and Stagehand tooling.
Browserbase tradeoff: An identity feature, a persisted Context and a Function secret solve different problems. Select the required combination instead of treating all three as automatic login.
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.
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
Browserbase's TypeScript Function contract is a reason to retain it when that is the deployed language your team wants. A move to Notte Functions includes a Python execution decision; moving only the browser can leave your existing controller in place.
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.
Sources: docs.browserbase.com [1] ↗tilion.com [2] ↗docs.notte.cc [3] ↗