Skip to content
back to the archive page
#DevEx

Atlassian Acquires DX for $1 Billion: Reasons and Implications (Category DevEx)

#DevEx #AI #ML #PlatformEngineering #Software #Architecture #Processes #Devops

On 18 September 2025, Atlassian officially announced its acquisition of DX (Developer Experience) for approximately $1 billion in cash and Atlassian shares, its largest acquisition to date. DX is an engineering-analytics platform that helps organizations assess development-team productivity and identify process bottlenecks. The deal interests me because DX’s creators include people behind DORA, SPACE, and DevEx, approaches I have discussed extensively.

Atlassian’s leadership describes the acquisition as a strategic move to help customers get more from AI investment and improve engineering teams’ work. More companies are investing in AI tools, it says, but they want to know whether that spending actually accelerates development. DX recently published its “Measuring AI code assistants and agents” methodology.

Customer overlap provided another rationale: around 90% of DX customers already use Atlassian products such as Jira, Confluence, and Bitbucket. Co-founder and CEO Cannon-Brooks noted that Atlassian had spent several years trying to build its own engineering-productivity analytics tool before deciding to buy an existing solution. DX itself was founded 5 years ago.

Atlassian plans to integrate DX deeply into its ecosystem. In October 2025, its CTO presented the new Atlassian Software Collection with DX as the latest component. DX complements existing tools by combining qualitative developer surveys with quantitative metrics such as pull-request turnaround time, build-failure frequency, and AI-tool adoption. DX data will be available directly in Atlassian products. Integrations with third-party tools will also remain, so customers can benefit regardless of whether they use the Atlassian stack.

The planned integration will give Atlassian users:

  • Productivity and bottleneck measurement: automatic collection of metrics such as code-review cycle time, failed-build frequency, and feature-delivery time to identify process bottlenecks.
  • AI usage analytics: tracking how actively and effectively developers use coding assistants, agents, and other AI tools, separating noise from actual returns on adoption.
  • Developer-experience assessment: regular qualitative feedback, including satisfaction surveys and Developer Experience indices. Combining metrics with developers’ views helps identify obstacles to productive work and friction between teams.

The acquisition adds a new class of engineering-analytics capabilities to Atlassian’s products, enabling developers and managers to measure and improve productivity together using evidence rather than intuition. Atlassian positions this within a broader strategy for an integrated development platform in the AI era: connecting planning through Jira and Confluence, execution through code and CI/CD, and effectiveness analysis through DX to improve software development continuously.

#AI #ML #PlatformEngineering #Software #Architecture #Processes #DevEx #Devops