Dia (Atlassian) vs Microsoft Edge Copilot Mode + Journeys

Dia (Atlassian) 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.

Dia (Atlassian) · Microsoft Edge Copilot Mode + Journeys

Cost & capability

Dia (Atlassian)Microsoft Edge Copilot Mode + Journeys
Capability bandcompetentcompetent
Capability composite5560
Cost tierfree
$/Mtok input0
$/Mtok output0
Use casesScoped Agentic, Offline Capable, Memory Augmented ChatScoped 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.

Dia (Atlassian)Microsoft Edge Copilot Mode + Journeys
Capability composite5560
Use casesScoped Agentic, Offline Capable, Memory Augmented ChatScoped Agentic, Memory Augmented Chat, Long Running Session
TypeLocal-first browser-history + @history queriesTab-context + Journeys session-grouping
Created2024-12 (announced); 2025-06 (beta); 2025-10 (public macOS launch); acquired by Atlassian Sept 4 20252025-07-28 (Copilot Mode announced); 2025-10 (rolled out all Copilot markets)
PricingFree + paidFree with Edge + Microsoft account; M365 Copilot features require M365 subscription
Funding$128M total $610M val Acquisition · 2025-09Microsoft public (MSFT); ~$3T market cap
Backend storagecustomcustom (Microsoft-managed)
DeploymentManaged-onlyManaged-only (Edge browser with Microsoft account)
MCPSkills can wrap MCP servers via Atlassian Forge bridge; not nativesearched not found
Optimised forlocal-first browser-history memory + @history queriestab-context grouping into resumable Journeys
Anti-fitnot for non-Atlassian enterprisenot for non-Edge browsers

At a glance

Dia (Atlassian)Microsoft Edge Copilot Mode + Journeys
SectionBrowser-agent memory Browser-agent memory
TierT1 T1
TypeLocal-first browser-history + @history queries Tab-context + Journeys session-grouping
Created2024-12 (announced); 2025-06 (beta); 2025-10 (public macOS launch); acquired by Atlassian Sept 4 2025 2025-07-28 (Copilot Mode announced); 2025-10 (rolled out all Copilot markets)
PricingFree + paid Free with Edge + Microsoft account; M365 Copilot features require M365 subscription
Funding$128M total $610M val Acquisition · 2025-09 Microsoft public (MSFT); ~$3T market cap
Backend storagecustom custom (Microsoft-managed)
DeploymentManaged-only Managed-only (Edge browser with Microsoft account)
API surfacesearched not found
Embeddinglocked
Multi-tenancyhard-isolation hard-isolation
MCPSkills can wrap MCP servers via Atlassian Forge bridge; not native searched not found
A2Asearched not found searched not found
OpenTelemetrysearched not found searched not found
Optimised forlocal-first browser-history memory + @history queries tab-context grouping into resumable Journeys
Anti-fitnot for non-Atlassian enterprise not for non-Edge browsers

Taxonomy

AxisDia (Atlassian)Microsoft Edge Copilot Mode + Journeys
storagefilekv
retrievalextraction-pullinjection
persistencelong-termcross-session
updateappend-onlyconsolidation
unitepisodeepisode
governanceuser-controllableuser-controllable
conflictnonenone

Pros & cons

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.

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.

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