Browserbase vs AWS AgentCore Browser

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.

Browserbase provides managed browser sessions and TypeScript Functions that run next to a browser. Contexts preserve browser state, while its identity and secret tools address different parts of the sign-in workflow.

Amazon Bedrock AgentCore Browser provides isolated managed browser sessions with live interaction and AWS observability. Browser automation libraries use its streaming endpoints; the surrounding AWS execution layer is a separate choice.

At a glance

Sources: docs.browserbase.com [1] ↗docs.browserbase.com [2] ↗docs.browserbase.com [3] ↗docs.browserbase.com [4] ↗docs.browserbase.com [5] ↗docs.aws.amazon.com [6] ↗

What survives a session

Browserbase: Contexts preserve browser data between sessions. Associate the intended Context with each user's browser and decide which sessions may update it; a Context is distinct from a live running session.

AWS AgentCore Browser: The Browser Tool documentation describes ephemeral sessions that reset after use. State that must outlive a session needs an explicit storage or authentication design rather than an assumption of permanent browser state.

Sources: docs.browserbase.com [1] ↗docs.aws.amazon.com [2] ↗

Website login

Browserbase: The identity documentation covers website authentication and reuse of login state. Contexts and Function Secrets serve different roles: retained browser state versus values available to executing code.

AWS AgentCore Browser: AWS credentials and IAM control access to the Browser Tool. Website login remains a separate concern: the identity used to authorize an AWS API call does not automatically sign the browser in to a third-party application.

Sources: docs.browserbase.com [1] ↗docs.aws.amazon.com [2] ↗

Where the code runs

Browserbase: A Function is TypeScript code published with an entry point. Invocation starts asynchronously, creates a browser, passes its connection URL to the handler, and stores the result, logs and session ID. Function webhooks report status changes.

AWS AgentCore Browser: The Browser Tool supplies the browser environment. An external process or another AWS execution service runs the application code that controls it. Identify that service and its runtime before comparing it with a deployed browser Function.

Sources: docs.browserbase.com [1] ↗docs.aws.amazon.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

Browserbase: Compare the public plan's included browser allowance and overage with the workflow's duration. Include proxy traffic and any separately priced services; an Arena browser-hour estimate does not describe the whole Browserbase bill.

AWS AgentCore Browser: A complete AWS workflow may include browser use, the controlling compute service, storage and other metered services. Price the selected architecture and region instead of treating a browser benchmark rate as the final invoice.

Sources: browserbase.com [1] ↗aws.amazon.com [2] ↗

Capacity and limits

Browserbase: Browser and Function constraints have separate documentation. Check the account's concurrent browser limit, the Function runtime cap and the Function region rather than assuming a browser entitlement covers every execution path.

AWS AgentCore Browser: AgentCore Browser supports multiple simultaneous sessions. Review AWS quotas and the chosen tool/session configuration; the browser session's timeout and the controller's execution timeout are separate limits.

Sources: docs.browserbase.com [1] ↗docs.aws.amazon.com [2] ↗

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 AWS AgentCore Browser when your application already uses AWS identity, logging and storage, and browser workflows need to fit those systems.

AWS AgentCore Browser tradeoff: The browser tool is not the entire AgentCore platform. Do not assign capabilities from unrelated AgentCore execution or identity products to a browser session without specifying the composition.

Sources: docs.browserbase.com [1] ↗docs.aws.amazon.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 Browserbase and AWS AgentCore Browser 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

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.

AgentCore Browser's AWS integration can matter more than moving a browser endpoint. Retain AWS identity and observability requirements in the evaluation, and separately account for the code runner and website login before comparing Notte's integrated 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: docs.browserbase.com [1] ↗docs.aws.amazon.com [2] ↗docs.notte.cc [3] ↗

Keep comparing