What the Atlassian Teamwork Graph Actually Is
The Atlassian Teamwork Graph is the underlying data infrastructure that connects all work data across the Atlassian Cloud platform and enables the AI capabilities that Rovo delivers. It is not a product that users interact with directly — it is the foundational layer that makes cross-product, cross-platform intelligence possible within Atlassian's Cloud environment. Understanding what the Teamwork Graph is clarifies why Rovo's capabilities differ from standard search and AI tools, and why the pricing model for Rovo access is structured through Teamwork Collections rather than as a standalone product.
The Teamwork Graph creates a unified data model that maps relationships between the core entities in enterprise work: work items such as Jira issues and JSM tickets, documents such as Confluence pages and external files, people including team members, assignees, and stakeholders, projects and their states, and the relationships between all of these entities. By maintaining this relational model across the full Atlassian ecosystem and connected external platforms, the Teamwork Graph enables Rovo to return contextually relevant results that understand the relationships between things, not just their individual attributes.
When a user searches for information about a specific feature using Rovo Search, the Teamwork Graph enables Rovo to return not just the Confluence page that mentions the feature name, but also the Jira epic where the feature is being tracked, the JSM tickets from customers who have raised related requests, the team members working on it, and the related documents from connected external systems. This relational awareness is what separates Rovo Search from keyword search across individual Atlassian products. It is the Teamwork Graph that makes this possible, and it is included in all Atlassian Cloud plans at no additional cost — it is the infrastructure on which both native Atlassian Intelligence and Rovo operate.
How the Teamwork Graph Connects to Rovo Pricing
The Teamwork Graph is not sold separately and carries no direct pricing. It is the foundational infrastructure of Atlassian Cloud that underpins all AI capabilities, and accessing it is implicit in every Atlassian Cloud subscription. The pricing conversation around the Teamwork Graph therefore occurs through the Teamwork Collection packaging — the product bundles through which Atlassian delivers Rovo access alongside the Teamwork Graph infrastructure.
Atlassian structures its Cloud offerings through three Teamwork Collection tiers. Standard Teamwork Collection is the entry-level Cloud offering, including Jira Software, Confluence, and Jira Service Management at Standard plan levels with native Atlassian Intelligence features. Premium Teamwork Collection, priced at approximately $29 per user per month for 50 to 250 users scaling to approximately $22.63 per user per month for 1,000 users on annual billing, adds Premium-tier capabilities including Rovo access at the 70-credits-per-user monthly pool, Atlassian Guard Standard for security governance, and advanced features within each included product. Enterprise Teamwork Collection uses custom negotiated pricing and provides Enterprise-tier capabilities with Rovo access at the 150-credits-per-user monthly pool, Atlassian Guard Premium, and unlimited instances for the included products.
The pricing architecture is important to understand for two reasons. First, it means that accessing the full Teamwork Graph capability through Rovo requires a Teamwork Collection subscription rather than just a Cloud subscription for individual products. Second, it means that organisations currently purchasing Jira Software, Confluence, and JSM as separate product subscriptions should model whether migrating to Teamwork Collection pricing produces a net cost increase or decrease — particularly when the value of included Rovo access and Atlassian Guard is factored into the comparison.
The External Connector Layer: What It Costs
The Teamwork Graph's value extends beyond Atlassian's own products through an extensive connector ecosystem that allows the graph to ingest and index data from external platforms. With more than 100 connectors available, organisations can extend Rovo Search across Google Drive, Microsoft SharePoint, Slack, GitHub, Salesforce, ServiceNow, Zendesk, and many other enterprise platforms — making the Teamwork Graph a unified intelligence layer across the full enterprise data estate, not just the Atlassian portion of it.
The native connectors for major platforms are included in Teamwork Collection subscriptions at no additional cost. Organisations do not pay per connector or per external platform indexed. The economic model is that the Teamwork Collection subscription grants access to the Teamwork Graph infrastructure and the Rovo capabilities that operate on it, including the cross-platform connectors. This is a notable commercial advantage compared to alternative enterprise AI platforms that charge per integration or per data source.
The connector ecosystem does require configuration work — each external platform needs appropriate authentication, permission scoping, and data access governance before Rovo can search across it. For regulated industries where data governance is a compliance requirement, this configuration must address data residency, access control alignment, and audit trail requirements before connectors are activated. The technical effort is non-trivial for complex environments, but the incremental licensing cost is zero beyond the Teamwork Collection subscription.
Teamwork Collection Pricing: What Enterprises Actually Pay
The published Teamwork Collection pricing provides a starting point, but enterprise negotiations routinely produce outcomes that differ materially from list prices. The published pricing for Teamwork Collection Premium at $29 per user per month (50 to 250 users) scaling to $22.63 for 1,000 users is on an annual billing cycle. Monthly billing carries a premium. Large enterprise deals at 2,000 or more users are negotiated as Teamwork Collection Enterprise with custom pricing that reflects both user scale and the commercial relationship context.
Organisations currently on individual Atlassian Cloud product subscriptions for Jira Software, Confluence, and JSM should model the full cost comparison carefully. The Teamwork Collection bundle is not always more expensive than the sum of individual product subscriptions at Premium tier — in some user count configurations, the bundle pricing is comparable or lower when Atlassian Guard Standard and Rovo access are valued at their standalone equivalents. This comparison requires detailed modelling against current subscription costs and is the starting point for any Teamwork Collection procurement conversation.
The Atlassian pricing changes introduced in 2025 and 2026 have already increased base Cloud subscription costs for many customers. Organisations renewing at these higher base prices should treat the renewal as an opportunity to negotiate Teamwork Collection terms that provide better total value — including Rovo access, Guard Standard, and credit pool terms — rather than simply accepting the price increase on individual product subscriptions.
Want to model Teamwork Collection costs against your current Atlassian spend?
Our Atlassian specialists model the full commercial comparison and identify negotiation opportunities in Teamwork Collection contracts.Negotiating Teamwork Collection Contracts: Key Levers
Teamwork Collection contracts at Enterprise tier have meaningful negotiating surface. The primary levers are user count and scaling, contract duration, credit pool commitments, and the treatment of price escalation at renewal. Each deserves explicit attention in the negotiation rather than acceptance of Atlassian's initial commercial position.
User count and scaling terms govern how the contract handles growth in the licensed user count during the term. Atlassian's standard approach is to bill any users above the contracted user count at the then-current list price. Negotiating a defined growth price — either a fixed rate or a cap on the percentage premium above the contracted rate — protects against cost spikes as the organisation scales during the term. This is particularly important for organisations in growth phases where user count is expected to increase materially.
Credit pool commitments, as discussed in the Rovo AI licensing guide, should be specified numerically in the contract rather than by reference to the plan-level policy. The standard credit allocation per user at Premium and Enterprise tiers should be a contractual term, along with the overage pricing structure and the conditions under which Atlassian can change these parameters.
The Cloud contract negotiation framework also applies to Teamwork Collection — price escalation caps at renewal, governance for what Atlassian can include in or exclude from the bundle, and data processing terms for the Teamwork Graph's external connector infrastructure are all legitimate contract negotiation topics. Atlassian's fiscal year ends July 31, making June and July the optimal months to close Teamwork Collection Enterprise negotiations when Atlassian's commercial teams are most motivated to reach targets.
Teamwork Graph and the DC Migration Decision
For organisations on Data Center evaluating Cloud migration, the Teamwork Graph and Rovo access are capabilities that exist only in Cloud. DC end-of-life by March 2029 makes Cloud migration mandatory, but the Teamwork Graph provides an affirmative case for accelerating that migration beyond the EOL compliance requirement. Organisations that delay migration are operating without access to the unified intelligence layer that Cloud provides — a gap that becomes more significant as competitors invest in AI-assisted knowledge management and process automation on Cloud platforms.
The Cloud migration planning process should explicitly include Teamwork Graph and Rovo adoption planning — which connectors to configure, which external platforms to integrate, what credit usage patterns to expect, and which Teamwork Collection tier is appropriate for the organisation's AI ambitions. Getting this planning right from the start of the Cloud deployment prevents the common outcome of migrating to Cloud and discovering that the subscription tier does not support the AI use cases that the organisation wants to pursue.
Atlassian Licensing Intelligence — Monthly
Teamwork Collection pricing updates, Rovo credit model changes, and negotiation benchmarks for enterprise Atlassian buyers.
Our team of Atlassian commercial and contract specialists models Teamwork Collection pricing, benchmarks it against current subscription costs, and negotiates the contract terms that protect enterprise AI investments in the Rovo and Teamwork Graph platform. Contact us to assess whether Teamwork Collection is the right commercial structure for your Atlassian estate and to get benchmarks on what enterprise buyers are actually paying.