Anthropic Software / SaaS Australia

Atlassian

Enterprise Knowledge Search · IT Operations Automation

Atlassian wanted agents to do consequential work inside Jira, Confluence, and related products, but enterprise customers would only trust long-running automation if the models could follow complex instructions, use internal tools safely, and reason across huge contextual graphs.

5 million+ agents executed in customer business workflows each month
Millions of users on Rovo Chat

Reported impact

Business outcome

Atlassian now runs more than 5 million agents in customer business workflows every month, serves millions of users on Rovo Chat, and uses Claude to automate increasingly complex work while keeping context and trust at the center of the platform.

  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

Atlassian deploys Claude on Google Cloud behind the parts of its Rovo platform where the cost of a wrong answer is highest. Rovo Chat uses Claude as one of its base models to choose tools and skills across Jira, Confluence, and the rest of the suite, while Rovo Max takes a goal, pulls context from Teamwork Graph's billions of objects, and works in a managed environment where admins control packages and network access. The same Claude foundation powers Rovo CLI plus code review and generation flows that can read large repositories or pick up Jira tickets directly. Inside Atlassian, engineering runs heavily on Claude Code and recent pilots brought it to product managers and designers for small code changes and prototypes. This architecture lets Atlassian combine broad enterprise context, tool orchestration, and governed execution in one agent stack.

Data flow

A user goal or Jira/Confluence task enters Rovo Chat or Rovo Max, Claude selects tools and context from Teamwork Graph, works through the task in an admin-controlled environment, and returns actions, code, or artifacts back into Atlassian workflows where humans can keep collaborating.

Solution architecture

5 components · 4 layers
  1. Compute
    • Claude Code Supports internal engineering plus code-review and code-generation experiences for software teams.
  2. Storage
    • Teamwork Graph Provides the connected context map of customer data that Rovo Max reasons over.
  3. Serving
    • Claude Platform Supplies the enterprise model layer behind Atlassian's hardest agent workloads.
    • Rovo Chat Acts as the in-product assistant that chooses tools and skills across Atlassian's suite.
  4. Orchestration
    • Rovo Max Takes a goal rather than a single task and works until it reaches it under managed controls.

Architecture clues

  • Rovo Max runs inside a managed environment where admins control packages and network access.
  • Some customers hand a Jira ticket straight to a Claude-powered agent that picks up the work and carries it out.
  • Teamwork Graph maps billions of objects across customer apps.

Evidence from the source

5 million+ agents executed in customer business workflows each month
Many of Atlassian's customers are also software and IT teams, and Claude handles their code review and code generation
Rovo Max draws on Teamwork Graph, Atlassian's connected map of the billions of objects that span a customer's apps
Someone handed the agent a Jira board and asked it to "create me an Instagram reel"
The Claude models are better at following complex instructions consistently and handling larger amounts of context without losing important details
Transparency Evidence & methodology 71/100 reference value · 77% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value71/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence77%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Anthropic

    Atlassian customer story

    First-party
    https://claude.com/customers/atlassian
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Aug 30, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.