Project Mariner vs Stagehand

Project Mariner vs Stagehand: side-by-side comparison of two computer-use & desktop agents systems — architecture, taxonomy, license, pricing, MCP/A2A support, and direct edges.

Project Mariner · Stagehand

Cost & capability

Project MarinerStagehand
Capability bandcompetentcompetent
Capability composite7358
Cost tiermidfree
$/Mtok input0
$/Mtok output0
Use casesScoped AgenticScoped Agentic, Code Generation Focused

Where they differ (15)

Rows where both sides have data and the values disagree — the shortlist of dimensions that actually distinguish these two systems.

Project MarinerStagehand
Capability composite7358
Cost tiermidfree
Use casesScoped AgenticScoped Agentic, Code Generation Focused
TypeGoogle DeepMind browser-agent (research preview)OSS browser-automation framework (Browserbase OSS)
Created2024-122024 (Browserbase release)
PricingBundled with Gemini Advanced ($19.99/mo)OSS free; Browserbase Cloud handles runtime
FundingGoogle DeepMind parent (Alphabet)Maintained by Browserbase ($40M Series B Q4 2024; Kleiner Perkins)
Backend storageGoogle-managed session stateLocal Playwright state; Browserbase-managed when cloud-hosted
DeploymentChrome extension + Google CloudLibrary — runs anywhere Playwright runs; Browserbase Cloud for managed
API surfaceChrome extension; underlying Gemini 2.0 APITS API (act/extract/observe); npm: @browserbasehq/stagehand
Multi-tenancySingle-tenant per Google accountPer-process in OSS; per-tenant in Browserbase Cloud
MCPsearched not foundComposes with Browserbase MCP server
A2AGoogle's own A2A protocol — likely first-party compatiblesearched not found
Optimised forGemini 2.0-powered Chrome agentPlaywright-replacement with AI verbs (act / extract / observe)
Anti-fitResearch preview only; Chrome only; Gemini Advanced tierTS-only; not a finished agent — caller wires logic; tied closely to Browserbase ecosystem

At a glance

Project MarinerStagehand
SectionComputer-use & desktop agents Computer-use & desktop agents
TierT1 T1
TypeGoogle DeepMind browser-agent (research preview) OSS browser-automation framework (Browserbase OSS)
Created2024-12 2024 (Browserbase release)
Latest release v2.x; active monthly releases (npm: @browserbasehq/stagehand)
License MIT
GitHub github.com/browserbase/stagehand — 9k+ stars
PricingBundled with Gemini Advanced ($19.99/mo) OSS free; Browserbase Cloud handles runtime
FundingGoogle DeepMind parent (Alphabet) Maintained by Browserbase ($40M Series B Q4 2024; Kleiner Perkins)
Backend storageGoogle-managed session state Local Playwright state; Browserbase-managed when cloud-hosted
DeploymentChrome extension + Google Cloud Library — runs anywhere Playwright runs; Browserbase Cloud for managed
API surfaceChrome extension; underlying Gemini 2.0 API TS API (act/extract/observe); npm: @browserbasehq/stagehand
Multi-tenancySingle-tenant per Google account Per-process in OSS; per-tenant in Browserbase Cloud
MCPsearched not found Composes with Browserbase MCP server
A2AGoogle's own A2A protocol — likely first-party compatible searched not found
OpenTelemetrysearched not found searched not found
Optimised forGemini 2.0-powered Chrome agent Playwright-replacement with AI verbs (act / extract / observe)
Anti-fitResearch preview only; Chrome only; Gemini Advanced tier TS-only; not a finished agent — caller wires logic; tied closely to Browserbase ecosystem

Taxonomy

AxisProject MarinerStagehand
storagekvfile
retrievalinjectioninjection
persistencesessionsession
updateagent-controlledagent-controlled
unitturndocument
governanceopaqueinspectable
conflictstatelesshuman-arbitrate

Pros & cons

Project Mariner

Pros: Strong WebVoyager numbers; Google distribution; A2A first-party adjacency.

Cons: Research preview; Chrome / Gemini Advanced tier; closed source.

Stagehand

Pros: Browserbase-backed OSS; clean act/extract/observe primitive; growing TS-agent ecosystem.

Cons: TS-only (no Python parity); ties best with Browserbase Cloud (vendor adjacency).

Rows last verified 2026-05-14 / 2026-05-14. Data is CC-BY-4.0 — see how to read this.