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.
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.
Lightpanda is a browser engine built for automation, with a hosted cloud offering. It is an engine choice as well as a hosting choice, so evaluate the site's behavior and the browser APIs your workflow uses.
At a glance
| Requirement | Hyperbrowser | Lightpanda |
|---|---|---|
| Browser control | Documented | Compatibility-dependent |
| Saved browser state | Documented | Not established |
| Credential handling | Credential fill | Application-owned |
| Website sign-in | Credential / profile flows | Not established |
| Code execution | Separate execution options | External worker |
| Scheduled execution | Check execution setup | External scheduler |
| Live view | Documented | Check engine support |
| Recordings / replay | Documented | Not established |
| Deployment choice | Check deployment offering | Engine available |
Sources: hyperbrowser.ai [1] ↗hyperbrowser.ai [2] ↗hyperbrowser.ai [3] ↗hyperbrowser.ai [4] ↗hyperbrowser.ai [5] ↗hyperbrowser.ai [6] ↗lightpanda.io [7] ↗
What survives a session
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.
Lightpanda: The reviewed cloud documentation does not establish a durable profile contract covering cookies and web storage. Determine how the required browser state is saved and restored before moving an authenticated workflow.
Website login
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.
Lightpanda: Browser engine compatibility and website authentication are separate requirements. The reviewed sources do not establish a managed website-auth connection equivalent; verify the login and verification flow on the target sites.
Where the code runs
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.
Lightpanda: The reviewed documentation establishes a browser engine and hosted access, not a deployed Python Function contract. A separate automation process must have its own deployment, triggers and monitoring design.
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 |
|---|---|---|---|---|
| Hyperbrowser | 878 ms | 944 ms | 2.03 | 2026-10-18 / 2026-10-17 |
| Lightpanda | 488 ms | 550 ms | 3.61 | 2026-10-18 / 2026-10-18 |
Sources: browserarena.ai [1] ↗browserarena.ai [2] ↗github.com [3] ↗
Pricing model
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.
Lightpanda: Use the cloud billing unit and account limits for hosted access. A lower rate only helps if the target pages and required actions complete correctly on the selected engine.
Capacity and limits
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.
Lightpanda: Use Lightpanda Cloud's limits and billing documentation for hosted capacity. Self-operated engine instances have a different capacity model and should not inherit cloud account assumptions.
Which approach fits?
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.
Choose Lightpanda when your workflow can use Lightpanda's supported browser APIs and you want to evaluate that engine on the pages you actually automate.
Lightpanda tradeoff: CDP connectivity does not establish complete Chromium compatibility. Validate rendering-dependent steps, downloads and browser features with the selected engine before a migration.
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 Hyperbrowser and Lightpanda 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
Hyperbrowser's profiles, credential tools and Action Caching deserve separate evaluation. A recorded action sequence and a deployed Python handler have different maintenance contracts, so decide which one your team will edit after the website changes.
Lightpanda introduces a browser-engine decision. Keep it on the shortlist when its supported actions fit the real pages you use; a successful CDP connection or text task does not establish visual or full-browser equivalence with the proposed Notte workflow.
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: hyperbrowser.ai [1] ↗lightpanda.io [2] ↗docs.notte.cc [3] ↗