Notte vs Hyperbrowser

The decision

Both document saved profiles and credential fill. Their persistence descriptions differ: Hyperbrowser describes user-data-directory state including cache, while Notte documents cookies and web storage. For code execution, compare the exact Hyperbrowser execution option with Notte's Python Function contract.

Notte combines cloud browser sessions with deployed Python automations and website authentication tools. You can control the browser over CDP or use Notte's actions, then deploy repeated work as a Function.

Hyperbrowser provides cloud browser sessions with profile persistence and browser credential fill. Its broader catalog also has sandboxes and other APIs; this comparison concerns the browser and the code or authentication attached to it.

At a glance

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] ↗hyperbrowser.ai [7] ↗hyperbrowser.ai [8] ↗hyperbrowser.ai [9] ↗hyperbrowser.ai [10] ↗hyperbrowser.ai [11] ↗hyperbrowser.ai [12] ↗

What survives a session

Notte: Profiles save cookies, local storage and session storage. Sessions start with fresh state by default. Persisting a profile writes state back when the session ends; a running session can also save its state explicitly.

Hyperbrowser: Profiles save browser user-data-directory state, including cookies, local storage, session storage and cache. A fresh session has a fresh directory unless a profile is attached and its save behavior is selected.

Sources: docs.notte.cc [1] ↗hyperbrowser.ai [2] ↗

Website login

Notte: Vaults substitute credential placeholders in supported browser actions outside the model context. Managed Auth checks requested saved connections before automation. Personas supply an inbox and optional phone number for verification workflows.

Hyperbrowser: Credential fill refers to stored secrets or vaults by name and fills selected inputs. The documented flow supports credentials and one-time codes; saved profiles address browser state after sign-in.

Sources: docs.notte.cc [1] ↗hyperbrowser.ai [2] ↗

Where the code runs

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.

Hyperbrowser: Action Caching records a HyperAgent action sequence for deterministic replay. The broader platform also offers sandbox compute. Check how a handler is deployed, invoked and versioned before choosing the execution path.

Sources: docs.notte.cc [1] ↗hyperbrowser.ai [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

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.

Hyperbrowser: The reviewed pricing page lists $0.10 per browser-hour and $10 per GB of proxy traffic. Credits acquired through subscriptions and direct purchases have different refresh or expiry behavior.

Sources: notte.cc [1] ↗hyperbrowser.ai [2] ↗

Capacity and 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.

Hyperbrowser: Session concurrency and configuration are account-dependent. Use the session API's supported settings and public limits rather than assuming that available sandbox capacity is browser concurrency.

Sources: notte.cc [1] ↗hyperbrowser.ai [2] ↗

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 Hyperbrowser when you need existing Playwright, Puppeteer or Selenium code to use a managed browser with saved state and named credentials.

Hyperbrowser tradeoff: Browser sessions, sandbox execution and action caching are separate surfaces. A cached action sequence is not the same deployment contract as an independently versioned browser Function.

Sources: docs.notte.cc [1] ↗hyperbrowser.ai [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 Notte and Hyperbrowser 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.

Keep comparing