Browserbase vs Dia (Atlassian)
Browserbase vs Dia (Atlassian): side-by-side comparison of two browser-agent memory systems — architecture, taxonomy, license, pricing, MCP/A2A support, and direct edges.
Cost & capability
| Browserbase | Dia (Atlassian) | |
|---|---|---|
| Capability band | competent | competent |
| Capability composite | 50 | 55 |
| Cost tier | free | free |
| $/Mtok input | 0 | 0 |
| $/Mtok output | 0 | 0 |
| Use cases | Scoped Agentic, Long Running Session | Scoped Agentic, Offline Capable, Memory Augmented Chat |
Where they differ (9)
Rows where both sides have data and the values disagree — the shortlist of dimensions that actually distinguish these two systems.
| Browserbase | Dia (Atlassian) | |
|---|---|---|
| Capability composite | 50 | 55 |
| Use cases | Scoped Agentic, Long Running Session | Scoped Agentic, Offline Capable, Memory Augmented Chat |
| Type | Programmatic session persistence (dev infra) | Local-first browser-history + @history queries |
| Created | 2024-06 | 2024-12 (announced); 2025-06 (beta); 2025-10 (public macOS launch); acquired by Atlassian Sept 4 2025 |
| Funding | $40M total $300M val Series B · 2025-04 | $128M total $610M val Acquisition · 2025-09 |
| API surface | REST, SDK: Python, JS/TS | searched not found |
| MCP | native (first-party) — Browserbase MCP | Skills can wrap MCP servers via Atlassian Forge bridge; not native |
| Optimised for | programmatic browser session persistence | local-first browser-history memory + @history queries |
| Anti-fit | not for end-users; developer infrastructure only | not for non-Atlassian enterprise |
At a glance
| Browserbase | Dia (Atlassian) | |
|---|---|---|
| Section | Browser-agent memory | Browser-agent memory |
| Tier | T1 | T1 |
| Type | Programmatic session persistence (dev infra) | Local-first browser-history + @history queries |
| Created | 2024-06 | 2024-12 (announced); 2025-06 (beta); 2025-10 (public macOS launch); acquired by Atlassian Sept 4 2025 |
| Pricing | Free + paid | Free + paid |
| Funding | $40M total $300M val Series B · 2025-04 | $128M total $610M val Acquisition · 2025-09 |
| Backend storage | custom | custom |
| Deployment | Managed-only | Managed-only |
| API surface | REST, SDK: Python, JS/TS | searched not found |
| Embedding | — | locked |
| Multi-tenancy | hard-isolation | hard-isolation |
| MCP | native (first-party) — Browserbase MCP | Skills can wrap MCP servers via Atlassian Forge bridge; not native |
| A2A | searched not found | searched not found |
| OpenTelemetry | searched not found | searched not found |
| Optimised for | programmatic browser session persistence | local-first browser-history memory + @history queries |
| Anti-fit | not for end-users; developer infrastructure only | not for non-Atlassian enterprise |
Taxonomy
| Axis | Browserbase | Dia (Atlassian) |
|---|---|---|
| storage | file | file |
| retrieval | extraction-pull | extraction-pull |
| persistence | session | long-term |
| update | overwrite | append-only |
| 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.
Dia (Atlassian)
Pros: Skills + memory architecture explicitly modeled on how a knowledge worker re-uses repeated workflows.
Cons: Atlassian-tied product positioning narrows reach; skills require setup before memory is useful.