Browser Use vs Tilion

The decision

Start with the product contracts for browser control, saved browser state, credential handling, website sign-in. Different labels do not establish different functionality; compare the implementation and conditions behind each one.

Browser Use has separate hosted-browser and hosted-agent paths. For browser infrastructure, create a browser and connect your own code over CDP. Profiles and secret bindings handle different parts of authenticated work.

Tilion appears in BrowserArena's browser infrastructure cohort. Its reviewed public homepage currently offers a waitlist and a contact path; that establishes less implementation detail than a public session API guide.

At a glance

Sources: docs.browser-use.com [1] ↗docs.browser-use.com [2] ↗docs.browser-use.com [3] ↗docs.browser-use.com [4] ↗tilion.com [5] ↗

What survives a session

Browser Use: Profiles persist cookies, local storage and login state between browsers. Browser settings select a profile for a run. A session's conversation history and a profile's browser state are different resources.

Tilion: The reviewed public homepage does not establish profile save/restore behavior. Ask for a documented state contract and test the same signed-in workflow across two separate sessions before relying on persistence.

Sources: docs.browser-use.com [1] ↗tilion.com [2] ↗

Website login

Browser Use: V4 secret bindings give credentials aliases and allowed hostnames for use in a run. Profiles reuse existing state; the separate 2FA guide addresses verification during authenticated work.

Tilion: The reviewed public material does not establish managed website authentication, credential fill or verification handling. Treat those as open requirements to validate with the provider, not as absent features.

Sources: docs.browser-use.com [1] ↗tilion.com [2] ↗

Where the code runs

Browser Use: The cloud offers hosted-agent runs and separately created browsers. The reviewed browser documentation does not establish a deploy-your-own Python Function equivalent. Keep an external script runner separate from a hosted agent when comparing execution ownership.

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.

Sources: docs.browser-use.com [1] ↗tilion.com [2] ↗

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.

Sources: browserarena.ai [1] ↗browserarena.ai [2] ↗github.com [3] ↗

Pricing model

Browser Use: Browser time and hosted-agent/model usage are separate pricing questions. Select the infrastructure path before comparing rates, and account for retained idle browser time and network usage where applicable.

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: docs.browser-use.com [1] ↗tilion.com [2] ↗

Capacity and limits

Browser Use: The concurrency guide distinguishes concurrent browser capacity from the HTTP request budget. Keys in a project share capacity and credits. Polling frequency can exhaust request capacity even when there are free browser slots.

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: docs.browser-use.com [1] ↗tilion.com [2] ↗

Which approach fits?

Choose Browser Use when you use Browser Use's framework or want its hosted browsers while retaining the option of a hosted browser agent.

Browser Use tradeoff: A hosted-agent run is a different execution unit from your deployed browser script. Keep comparisons focused on the browser path when measuring session speed and price.

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.browser-use.com [1] ↗tilion.com [2] ↗

Check the browser connection

Install playwright-core in your application and provision a session through the provider's documented creation flow. Run this smoke test from the intended controller region with the returned CDP endpoint. It checks connection and navigation, not login, rendering parity or a complete business workflow.

Keep browser connection URLs on your backend. After the test, release the owned session through the provider's API. Product-specific lifecycle APIs and profile identifiers are not portable between providers.

import { chromium } from "playwright-core";

// Provision the owned browser using the provider's documented session API.
// Keep the connection URL in your backend's secret environment.
const endpoint = process.env.BROWSER_CDP_URL;
if (!endpoint) throw new Error("Set BROWSER_CDP_URL for an owned session");

const browser = await chromium.connectOverCDP(endpoint);
try {
  const context = browser.contexts()[0] ?? await browser.newContext();
  const page = context.pages()[0] ?? await context.newPage();
  await page.goto("https://example.com", { waitUntil: "domcontentloaded" });
  if ((await page.title()) !== "Example Domain") {
    throw new Error("The browser did not reach the expected page");
  }
  console.log({ connected: true, expectedPage: true });
} finally {
  await browser.close();
  // Release the owned session with the provider's documented API as well.
  // A disconnected socket alone is not a portable session-cleanup contract.
}

Sources: playwright.dev ↗

Before you switch

Keep the same target workflow when evaluating both products. Separate infrastructure facts from measurements and test the required account state, action sequence and artifacts. A successful connection test does not establish that a long or authenticated task will complete.

Use the focused guides for Browser Use and Tilion below when the deciding requirement is pricing, persistence or code execution. Provider-owned resources such as session IDs, profiles and managed connections need a new mapping during migration.

When Notte belongs on this shortlist

Browser Use's hosted-agent offering and standalone browser infrastructure are separate options. Keep the comparison at the browser layer when your application already owns its controller; compare execution ownership separately if the hosted agent is part of the requirement.

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.browser-use.com [1] ↗tilion.com [2] ↗docs.notte.cc [3] ↗

Keep comparing