Browserbase vs Microsoft Edge Copilot Mode + Journeys
Browserbase vs Microsoft Edge Copilot Mode + Journeys: side-by-side comparison of two browser-agent memory systems — architecture, taxonomy, license, pricing, MCP/A2A support, and direct edges.
Browserbase · Microsoft Edge Copilot Mode + Journeys
Cost & capability
| Browserbase | Microsoft Edge Copilot Mode + Journeys | |
|---|---|---|
| Capability band | competent | competent |
| Capability composite | 50 | 60 |
| Cost tier | free | — |
| $/Mtok input | 0 | — |
| $/Mtok output | 0 | — |
| Use cases | Scoped Agentic, Long Running Session | Scoped Agentic, Memory Augmented Chat, Long Running Session |
Where they differ (11)
Rows where both sides have data and the values disagree — the shortlist of dimensions that actually distinguish these two systems.
| Browserbase | Microsoft Edge Copilot Mode + Journeys | |
|---|---|---|
| Capability composite | 50 | 60 |
| Use cases | Scoped Agentic, Long Running Session | Scoped Agentic, Memory Augmented Chat, Long Running Session |
| Type | Programmatic session persistence (dev infra) | Tab-context + Journeys session-grouping |
| Created | 2024-06 | 2025-07-28 (Copilot Mode announced); 2025-10 (rolled out all Copilot markets) |
| Pricing | Free + paid | Free with Edge + Microsoft account; M365 Copilot features require M365 subscription |
| Funding | $40M total $300M val Series B · 2025-04 | Microsoft public (MSFT); ~$3T market cap |
| Backend storage | custom | custom (Microsoft-managed) |
| Deployment | Managed-only | Managed-only (Edge browser with Microsoft account) |
| MCP | native (first-party) — Browserbase MCP | searched not found |
| Optimised for | programmatic browser session persistence | tab-context grouping into resumable Journeys |
| Anti-fit | not for end-users; developer infrastructure only | not for non-Edge browsers |
At a glance
| Browserbase | Microsoft Edge Copilot Mode + Journeys | |
|---|---|---|
| Section | Browser-agent memory | Browser-agent memory |
| Tier | T1 | T1 |
| Type | Programmatic session persistence (dev infra) | Tab-context + Journeys session-grouping |
| Created | 2024-06 | 2025-07-28 (Copilot Mode announced); 2025-10 (rolled out all Copilot markets) |
| Pricing | Free + paid | Free with Edge + Microsoft account; M365 Copilot features require M365 subscription |
| Funding | $40M total $300M val Series B · 2025-04 | Microsoft public (MSFT); ~$3T market cap |
| Backend storage | custom | custom (Microsoft-managed) |
| Deployment | Managed-only | Managed-only (Edge browser with Microsoft account) |
| API surface | REST, SDK: Python, JS/TS | — |
| Multi-tenancy | hard-isolation | hard-isolation |
| MCP | native (first-party) — Browserbase MCP | searched not found |
| A2A | searched not found | searched not found |
| OpenTelemetry | searched not found | searched not found |
| Optimised for | programmatic browser session persistence | tab-context grouping into resumable Journeys |
| Anti-fit | not for end-users; developer infrastructure only | not for non-Edge browsers |
Taxonomy
| Axis | Browserbase | Microsoft Edge Copilot Mode + Journeys |
|---|---|---|
| storage | file | kv |
| retrieval | extraction-pull | injection |
| persistence | session | cross-session |
| update | overwrite | consolidation |
| unit | episode | episode |
| governance | inspectable | user-controllable |
| conflict | none | none |
Pros & cons
Browserbase
Pros: Most developer-friendly path to remote browser agents — memory is structured around session replays, not chat history.
Cons: Infrastructure-tier product; not useful directly to end users without an agent layer on top.
Microsoft Edge Copilot Mode + Journeys
Pros: Journeys timeline memory — cross-tab, cross-session reconstruction of research arcs — is more sophisticated than competitor history features.
Cons: Edge browser lock-in; Microsoft account required to retain Journeys across devices.