Compare approaches

Oya vs Stagehand: an agent SDK, or the browser and playbook layer beneath it.

Stagehand gives developers act, extract and observe primitives in code. Compare whether you want an open-source SDK alone, or a browser platform with standalone Playwright playbooks, sealed credentials, audit logs and HIPAA deployment.

Start building
Compare approaches
Oya
Stagehand
What it is built for
Replays a finished task with no model
Replay is standard Playwright you own

Criteria from the comparison below.

Conceptual illustration

Start with what happens after your first script works.

Getting an agent to click through a form once is the easy part. Decide how you will cache or replay runs that touch credentials and personal data, where the browser fleet runs, and what your security team will audit.

Compare the requirements that follow from that task.

Look at agent connections, reuse of completed work, deployment and human intervention. If protected health information (PHI) is involved, check the covered edition and Business Associate Agreement (BAA).

Check the published differences.

The table below uses the linked vendor pages and their stated review date. “Not stated” means the pages reviewed did not say; it does not establish that a capability is absent.

Sources checked 2026-11-20View primary sources (4)
Oya and Stagehand, from each project’s own pages
OyaStagehand
What it is built forBrowser and control plane for signed-in agent workflows: desktop app, Oya Cloud, self-hosted, MCP and CDPOpen-source MIT SDK (TypeScript, Python, Go) with act, extract and observe primitives over local or Browserbase browsers
Replays a finished task with no modelYes: playbooks, and the agent repairs only a step that movedLocal Cache (cacheDir) or Browserbase Cache; docs advise Browserbase Cache only for non-personalized pages without credentials or personal data
Replay is standard Playwright you ownYes: every playbook is a readable Playwright module that runs on any Chromium browser over CDPNot stated: cached actions stay inside Stagehand rather than exporting as standalone Playwright
Model never sees passwordsPasswords and TOTP seeds are sealed and never shown to the modelobserve() returns selectors so your code fills credentials from environment variables without sending them to the model
A person can take over liveWatch live, take over, hand backProvided when paired with Browserbase live view, not built into the standalone SDK
Runs in your own infrastructureEnterprise edition on Docker, ECS, GCP or Kubernetes, with a BAA; community edition free up to 5 browsersRuns locally against your own Chromium or CDP browser (MIT); hosted fleet comes from Browserbase
SOC 2Type I report issued; Type II audit in progressNot stated for standalone SDK; Browserbase states SOC 2 Type II
Signs a BAA for HIPAA workYes: HIPAA mode on Oya Cloud (BAA on request) or self-hosted in your own cloudNot stated for standalone SDK; Browserbase states BAA on its Scale plan
Audit trail of agent and person actionsAppend-only and hash-chained; every read of ePHI audited; kept six years in HIPAA modeNot stated
Free tier, then first paid planFree desktop app and 1 cloud browser hour; $500 a month for 100 hoursFree open-source SDK (MIT); you pay your own model API and browser host costs

Choose Oya when

  • You want finished runs exported as standalone Playwright playbooks that replay with no model, including on authenticated workflows.
  • You need sealed passwords and TOTP, live human takeover, and an append-only audit trail built into the browser platform.
  • You need self-hosted infrastructure or HIPAA mode with a signed BAA on Oya Cloud or the enterprise edition.

Choose Stagehand when

  • You want an open-source MIT SDK in TypeScript, Python or Go built around act, extract and observe primitives.
  • You already host your own browsers or use Browserbase and want lightweight code-first control over each model step.
  • Your caching needs fit Local Cache or Browserbase Cache on non-personalized pages without credentials or personal data.

Run Stagehand v3 on Oya browsers when you want both.

Oya does not route browsers through Stagehand, because Stagehand is an SDK rather than a browser host. Stagehand v3 connects over CDP, so you can point Stagehand v3 at an Oya browser’s CDP URL (cdpUrl) to combine Stagehand code with Oya’s self-hosting, audit trail and HIPAA-mode browsers. Stagehand v4 runs inside its own browser extension, which Oya browsers do not load yet.

Test the fit with your own work.

Use the comparison to shortlist an approach, then evaluate it against a representative workflow.

Sources

What this page says about other companies comes from their own public pages, read on 2026-11-20. Vendors change their pages; check the source before you rely on a cell.

Bring one working automation into your project, then try it with the next set of inputs.

Start building

Questions

Can I use Stagehand with Oya Browser?

Yes, with Stagehand v3. Every Oya browser exposes a CDP URL that Stagehand v3 connects to via cdpUrl, running inside Oya Cloud or self-hosted browsers. Stagehand v4 runs inside its own browser extension, which Oya browsers do not load yet.

How do Oya playbooks differ from Stagehand caching?

Stagehand offers Local Cache (cacheDir) and Browserbase Cache, and its caching docs recommend Browserbase Cache only for non-personalized pages without credentials or personal data. Oya saves finished tasks as readable Playwright playbooks that replay with no model on your own inputs, and the agent repairs only a step that moved.

Does Stagehand include a browser fleet, live view or HIPAA BAA?

Stagehand itself is an open-source MIT SDK. Hosted browser fleets, live view, SOC 2 Type II and a BAA on the Scale plan come from Browserbase rather than the standalone SDK. Oya provides the browser, live takeover, audit trail and HIPAA BAA on Oya Cloud and the enterprise edition.

How do Stagehand and Oya handle login credentials?

Stagehand’s observe() pattern returns selectors so your code fills credentials from environment variables without passing them to the model. Oya seals stored passwords and TOTP seeds inside the platform so the model never sees them, and lets staff take over live for text-message codes.

Can I self-host a HIPAA-compliant agentic browser?

Yes, with the enterprise edition: it runs on Docker, ECS, GCP or Kubernetes, comes with a BAA, and keeps HIPAA workloads in your own infrastructure. Write to sales@getoya.ai. The source-available community edition self-hosts too, without the HIPAA offering. Every playbook exports as Playwright code you keep.