Atlassian Rovo AI Licensing: What It Costs and How to Negotiate

What Atlassian Rovo AI Actually Is

Atlassian Rovo is the company's generative AI platform, launched in late 2024 and now embedded across all Atlassian Cloud products. Unlike standalone AI tools, Rovo is designed to operate at the intersection of where work actually happens — within Jira issues, Confluence pages, Jira Service Management tickets, and the workflows that connect them. It does not require users to context-switch to a separate chat interface or import their data into an external AI tool. Rovo surfaces intelligence directly within the Atlassian environment, drawing on both Atlassian-hosted data and external connections across more than 100 integrated platforms.

Understanding Rovo's architecture is essential for understanding its pricing model and its negotiation dynamics. Rovo is built on Atlassian's Teamwork Graph — a unified data layer that maps relationships between work items, people, projects, documents, and external data sources across the Atlassian ecosystem and connected platforms. The Teamwork Graph is what enables Rovo Search to return genuinely contextual results rather than keyword matches, and what allows Rovo Agents to execute multi-step workflows with awareness of project context, team dependencies, and process state.

Rovo consists of four primary capability areas. Rovo Search provides a unified search interface that queries across Atlassian tools and connected external applications including Google Drive, Microsoft SharePoint, Slack, GitHub, and more than 100 additional platforms. Results are ranked by relevance and context, not just keyword matching. Rovo Chat is a conversational AI interface that uses company data — Confluence documentation, Jira project history, JSM service records — to answer questions, summarise complex information, and generate content with organisational context. Rovo Agents are customisable AI automations that execute multi-step tasks within Atlassian tools without requiring human intervention at each step. Rovo Studio is a no-code or low-code builder for creating and deploying custom Rovo Agents without requiring engineering resource.

As of April 2026, Rovo has surpassed five million monthly active users, with Rovo Agents automating more than 2.4 million workflows in the previous six months. These are not small adoption numbers — they signal that enterprise buyers need to understand Rovo's commercial structure carefully, because it is becoming a material component of Atlassian's commercial proposition.

Rovo Pricing: What You Actually Pay

Rovo's pricing model has evolved significantly since its initial launch as a standalone add-on in October 2024, when it was priced at $24 per user per month for organisations with fewer than 100 users and $20 per user per month for organisations with 375 or more users. That standalone pricing model has been substantially restructured.

As of early 2026, Rovo is bundled into Atlassian Cloud subscriptions rather than sold as a separate add-on. Standard, Premium, and Enterprise Cloud plan customers receive access to Rovo Search, Rovo Chat, Rovo Agents, and Rovo Studio as part of their Cloud subscription. Non-Atlassian-Cloud customers who want Rovo access pay $5 per user per month as a standalone subscription.

The Credit System: The Real Cost Driver

The headline "Rovo is included" requires important qualification. While Rovo access is included in Cloud plan subscriptions, the actual consumption of Rovo capabilities is metered through a credit system that determines both the scope of what is available within the base subscription and the cost of usage beyond that scope.

Under the credit system, Rovo Search queries are unlimited and do not consume credits. Every Rovo Chat or standard Rovo Agent interaction consumes 10 credits. Deep Research requests — more computationally intensive Rovo operations that synthesise information across multiple sources — consume 100 credits per request. Credit allowances are pooled at the organisational level rather than per user, which provides flexibility but also means that heavy use by a subset of users can exhaust the pool for the entire organisation.

Credit allowances differ by plan tier. Premium Teamwork Collection customers receive a monthly pooled credit allowance that Atlassian has described as providing 70 credits per user on the subscription. Enterprise Teamwork Collection customers receive 150 credits per user monthly. Exceeding these allowances triggers additional charges, though Atlassian has committed to providing 90 days' notice before enforcing overage fees — a commitment that enterprise buyers should seek to lock into their contract terms rather than relying on as a policy that can change.

Rovo Dev: Separate Consumption Pricing

Rovo Dev, the coding-focused AI capability within Atlassian's developer tooling, operates on a separate consumption-based pricing model at $0.01 per credit with a default monthly limit of 2,000 credits per user. Rovo Dev supports four AI models: Claude Haiku 4.5, Claude Opus 4.5, GPT-5.2, and GPT-5.2-Codex, with credit consumption varying by model based on computational intensity. This creates a secondary cost dimension for organisations where Rovo Dev is actively used by development teams alongside standard Rovo capabilities.

Teamwork Collection Pricing

Rovo access is delivered through Atlassian's Teamwork Collection packaging rather than as a standalone product. Teamwork Collection Premium is priced at approximately $29 per user per month for 50 to 250 users and scales down to approximately $22.63 per user per month for 1,000 users on annual billing. Teamwork Collection Enterprise uses custom pricing negotiated based on user count, feature requirements, and commercial context.

Both Premium and Enterprise Teamwork Collections include Rovo access at the relevant credit tier, plus Atlassian Guard Standard for security and access management. This bundling means that organisations evaluating Rovo costs need to model the full Teamwork Collection price against their current Atlassian subscription costs rather than treating Rovo as an additive line item on top of existing spend.

What Is Included in Each Cloud Plan: Free vs Paid AI

A critical source of confusion in Rovo licensing is the distinction between AI capabilities that are included natively in Cloud plans at no additional cost, Rovo capabilities that are included within the credit quota system, and Rovo capabilities that consume credits and therefore carry usage-based costs.

Atlassian Intelligence, the umbrella term for AI features embedded directly in Atlassian products, includes a set of capabilities that are available without credit consumption for Cloud subscribers. These include AI-powered issue summarisation in Jira, AI writing assistance in Confluence, automated sprint insights, smart quick replies in JSM, and similar contextual AI features embedded within the native product interface. These features require no Rovo subscription and consume no Rovo credits — they are part of the base Cloud product experience.

Rovo Search, as noted above, is unlimited and free within the credit system. All Rovo Search queries across Atlassian tools and connected external platforms can be executed without credit consumption. This is an important point for organisations evaluating Rovo: the search functionality that most users will interact with most frequently carries no marginal cost beyond the subscription.

Rovo Chat, Rovo Agents, and Deep Research are where credit consumption begins. Standard users on a Premium subscription have access to a monthly pool of credits that translates to approximately 70 Rovo Chat or standard Agent interactions per user per month before credits are exhausted. Enterprise users have a larger pool at 150 credits per user. For many enterprise use cases, particularly knowledge work teams running relatively moderate AI interaction volumes, this credit allocation is sufficient. For power users or agentic automation-heavy environments, the credit limits become a genuine planning consideration.

Rovo vs GitHub Copilot: The Enterprise Dev Tool Question

For development teams, the most common commercial question surrounding Rovo is how it compares to GitHub Copilot and whether purchasing both is justifiable. The answer requires understanding that these tools address fundamentally different dimensions of developer productivity rather than competing on identical functionality.

GitHub Copilot specialises in code generation, completion, and optimisation within the integrated development environment. It reads repository context, understands code structure, and generates code suggestions inline with the developer's workflow. GitHub Copilot Business costs $19 per user per month. GitHub Copilot Enterprise, which adds the ability to fine-tune the model with custom repository data and provides enhanced control over enterprise deployment, costs $39 per user per month.

Rovo is not a code generation tool. It does not generate code suggestions inline with IDE workflows. What Rovo provides for developers is contextual project intelligence — surfacing the Jira ticket associated with a coding task, pulling relevant Confluence documentation for the feature being implemented, retrieving historical decisions from JSM service records, and enabling AI-driven automation of project management tasks that developers typically handle manually. Atlassian has developed a Rovo for GitHub Copilot extension that makes this contextual intelligence available within the GitHub Copilot interface, allowing developers to query Jira and Confluence data without leaving their IDE.

For most enterprise development teams, Rovo and GitHub Copilot are complementary rather than competitive. Copilot handles code generation; Rovo handles project context and knowledge management automation. The combination provides coverage across the full developer workflow in ways that neither tool covers independently. The commercial question is whether the incremental value of the Rovo layer justifies its cost for development teams who already have Atlassian Cloud subscriptions — and since Rovo is now included in Teamwork Collection rather than priced as an add-on, the marginal cost calculation has become more favourable.

The comparison to Microsoft 365 Copilot is also worth noting for organisations with significant Microsoft investment. Microsoft 365 Copilot operates within the Microsoft 365 ecosystem — Teams, Word, Excel, Outlook — and is priced at $30 per user per month. For organisations whose knowledge work happens primarily in Atlassian tools rather than Microsoft Office applications, Rovo's contextual relevance within the Atlassian environment gives it a structural advantage that Microsoft Copilot cannot replicate without Atlassian data integration.

How to Negotiate Rovo Licensing

Atlassian has a commercial reputation for being a difficult vendor to negotiate with, and that reputation has a basis in reality. Standard list pricing is published and Atlassian historically maintains it for smaller accounts. However, at the enterprise spend levels where Rovo pricing becomes a material consideration, commercial flexibility exists — if approached correctly.

Enterprise Tier Negotiation Levers

The primary negotiation levers for Rovo and Teamwork Collection pricing at Enterprise tier are user scale, contract duration, and total Atlassian relationship value. Organisations purchasing Teamwork Collection Enterprise for 1,000 or more users are in a position to negotiate custom pricing that reflects both the volume and the strategic nature of the relationship. Atlassian's fiscal year ends July 31, which creates a recurring window each June and July when Atlassian's sales teams are most motivated to close deals and most willing to offer commercial accommodations to reach targets.

Credit allowance is a negotiating dimension that many buyers do not address explicitly. Rather than accepting the standard credit tier per plan level, enterprise buyers should negotiate for higher credit pools — or for overage pricing caps — as a contractual term rather than relying on Atlassian's policy-level commitment to 90 days' notice before enforcing overages. Locking in overage pricing thresholds and rates in the contract protects against future policy changes that increase costs for high-usage organisations.

Rovo Dev pricing is a separate consumption model that should be modelled and negotiated alongside the Teamwork Collection contract for organisations with significant development teams. Negotiating a custom credit rate or a committed consumption discount for Rovo Dev is worth pursuing at scale, particularly for organisations with 500 or more active developers using the tooling.

Bundling Strategy

Atlassian's commercial model increasingly pushes towards Teamwork Collections as the packaging mechanism rather than individual product licences. Organisations that currently hold individual Jira Software, Confluence, and Jira Service Management licences should model the cost of transitioning to Teamwork Collection pricing versus continuing with individual product licences. In many cases, the Teamwork Collection includes Rovo and Atlassian Guard at a price that is comparable to or lower than the sum of individual product licences plus the cost of equivalent security tooling purchased separately.

The bundling conversation with Atlassian's account team is most productive when brought to the table at renewal rather than mid-term. At renewal, both the base platform pricing and the Rovo credit structure can be addressed in a single commercial conversation with clear leverage around the renewal decision itself.

Competitive Context as Leverage

Atlassian responds to competitive commercial pressure more than its public positioning suggests. Demonstrating awareness of GitHub Copilot, Microsoft 365 Copilot, and alternative agentic AI platforms during the Rovo pricing conversation creates negotiating context that can shift the commercial terms. This does not require a genuine intention to switch platforms — it requires demonstrating that the procurement team has evaluated alternatives and understands the market pricing, which changes the vendor's assessment of price sensitivity.

The pricing changes Atlassian has implemented across 2025 and 2026 have increased the base cost of Cloud subscriptions materially. Using these changes as a discussion point — specifically asking for commercial stability commitments or pricing caps as part of the Rovo negotiation — is a legitimate approach that reflects the real cost impact on enterprise budgets.

The Rovo Negotiation Playbook: Step by Step

Based on experience across 500+ enterprise Atlassian engagements, the negotiation sequence that produces the best Rovo commercial outcomes follows a structured approach. The first step is establishing the baseline: model the full Teamwork Collection cost at the applicable user tier and compare it against the current sum of individual Atlassian product licences. Understand whether the transition to Teamwork Collection increases or decreases total spend before the negotiation begins.

The second step is credit modelling. Estimate realistic Rovo Chat and Rovo Agent usage patterns for the user population — not theoretical maximums, but usage levels consistent with comparable AI tool adoption patterns in the organisation. Determine whether the standard credit allowance at the applicable tier is likely to be sufficient, or whether overage costs will be material. This modelling drives the negotiation focus: if credit overages are likely to be significant, locking in overage pricing is more valuable than headline licence price reductions.

The third step is timing. Bring the Atlassian renewal conversation forward by 60 to 90 days to create negotiating room. Atlassian's July 31 fiscal year end means that Q3 conversations — May, June, July — are conducted when Atlassian's commercial teams are most motivated. The Cloud contract negotiation process for Rovo should be integrated with the broader platform renewal rather than treated as a separate AI add-on discussion.

The fourth step is documenting competitive context. Prepare a brief summary of alternative AI tooling being evaluated — GitHub Copilot pricing, Microsoft 365 Copilot terms, standalone AI tools — and share this context with Atlassian's account team as part of the commercial conversation. This does not need to be a formal competitive review; it simply needs to signal that the procurement team is market-aware.

The fifth step is contract term specificity. Every commercial commitment that Atlassian's sales team makes verbally should be captured as a contract term. Credit pool sizes, overage pricing structures, price escalation caps for subsequent renewal periods, and migration support commitments should all be in the signed agreement rather than in email correspondence or verbal assurances.

Rovo and the Atlassian DC Migration: Timing Considerations

For organisations currently on Data Center who are evaluating the move to Cloud, Rovo access is one of the capabilities that only exists on Cloud. Rovo is not available on Data Center — it is a Cloud-only feature tied to the Teamwork Graph infrastructure that requires Atlassian's Cloud environment to operate. The DC end-of-life timeline with a hard deadline of March 2029 means that DC customers who delay migration are also delaying access to Rovo and the AI capabilities it provides.

This creates an interesting commercial dynamic in DC renewal negotiations. Organisations renewing DC licences for 2027 or 2028 should be aware that every year of DC operation is a year without Rovo access. Building the value of Rovo access — specifically the productivity benefits of the capabilities that Rovo delivers — into the DC migration business case strengthens the argument for accelerated migration timelines. It also creates leverage in the DC renewal conversation: an organisation that can plausibly accelerate its Cloud migration in exchange for better DC renewal terms is in a stronger negotiating position than one simply renewing DC on autopilot.

The Cloud migration planning process should explicitly include Rovo adoption planning — which teams will use which Rovo capabilities, what the credit usage modelling shows, and what Teamwork Collection tier is appropriate for the migrated Cloud environment. Integrating this analysis into the migration project prevents the all-too-common outcome of organisations migrating to Cloud and then discovering that the Rovo licensing model they signed up for does not match their actual usage patterns.

Contract Terms Every Rovo Buyer Must Negotiate

Based on experience reviewing Atlassian Cloud contracts that include Rovo, several contract terms are consistently under-negotiated and worth specific attention. The first is credit pool visibility: the contract should specify the monthly credit pool size numerically rather than by reference to a plan-level policy that can be changed. If Atlassian states that Premium users receive 70 credits per user monthly, that number should be in the contract.

The second is overage pricing: the contract should specify the per-credit price for usage above the included pool, rather than leaving overage pricing to Atlassian's discretion at the time the overage is billed. The third is price escalation caps for renewal: Atlassian has increased Cloud prices materially in recent years, and the contract should cap the percentage increase that Atlassian can apply at each annual renewal.

The fourth is model access: Rovo Dev uses multiple AI models, and the contract should specify the models included in the deployment and the credit multipliers that apply to each. As Atlassian adds new models, the credit cost of those models should be bounded rather than open-ended. The fifth is data residency: Rovo processes organisational data through Atlassian's AI infrastructure, and the contract should specify data residency commitments, retention policies, and the conditions under which Atlassian can use interaction data for model training — a point that regulated industries must address explicitly.

Our Atlassian contract advisory specialists review Rovo and Teamwork Collection contracts at Enterprise tier, identify gaps in commercial protection, and negotiate the specific terms described above. Contact us to review your Rovo commercial terms before the next renewal cycle.