How Rovo credits work
Rovo credits are Atlassian's unit of measurement for usage of AI capabilities and access to enriched context via the Teamwork Graph (TWG).
Rovo credit usage depends on the complexity of a user’s or an agent’s interactions with AI features and the Teamwork Graph API. This includes calls made via the Teamwork Graph command-line interface (CLI) and the Atlassian Rovo Model Context Protocol (MCP) server. Your organization receives Rovo credit allowances based on your Atlassian app and plan, pooled at the organization level. See How usage-based pricing works
Please note:
On December 3, 2026, extra usage billing takes effect for Rovo credits. In Atlassian Administration, you can track your organization's Rovo credit usage and plan ahead.
Organization and billing admins will get proactive notifications as you approach 80% and 100% of included Rovo credit allowances.
Extra usage is enabled by default, and admins can set spending limits to ensure teams experience no interruptions when working with AI. Organization and billing admins can disable extra usage at any time in Atlassian Administration.
AI features in beta don't currently count against your Rovo credit allowance unless stated otherwise. They may count toward your allowance once they are generally available.
When using our services, customers must comply with the Atlassian Acceptable Use Policy.
Included Rovo credit allowances
Rovo credits are included in all paid Jira, Confluence, Service Collection and Teamwork Collection cloud subscriptions.
To turn on Rovo, your organization admin must be on a verified business domain (for example, @yourcompany.com). We can’t enable Rovo on sites where the organization is registered with a generic email domain such as gmail.com or outlook.com.
Each eligible cloud subscription includes a per‑user, per‑month Rovo credit allowance:
Offering | Standard Rovo credits (per user per month) | Premium Rovo credits (per user per month) | Enterprise Rovo credits (per user per month) |
|---|---|---|---|
Jira | 25 | 70 | 150 |
Confluence | 25 | 70 | 150 |
Service Collection | 250 | 700 | 1,500 |
Teamwork Collection | 250 | 700 | 1,500 |
Rovo credits are:
Shared at the organization level: All of your organization’s Rovo credit allowances are combined into a single shared pool of Rovo credits. Power users can consume more credits while light users can consume less, with the balance spread across the org. Coming soon: you’ll be able to allocate Rovo credits by user.
Aggregated across apps and collections: The more eligible Atlassian offerings you have, the more Rovo credits you receive. A customer with Jira + Confluence seats gets the combined Rovo credits included for both apps within their editions.
For example, if you have 100 Confluence Premium users and 100 Jira Premium users, your organization receives (100 users x 70 credits) + (100 users x 70 credits) = 14,000 Rovo credits per month.
Reset monthly: Allowances refresh monthly on your usage billing date. Unused credits do not roll over.
What consumes Rovo credits
Rovo credits are consumed by billable events. A billable event depends on the action performed.
For example,
In chat, each user message is a billable event.
For Atlassian agents and AI features, each invocation is a billable event.
Rovo credits are consumed by billable events across two categories:
Intelligence: Credits are consumed when a user or agent invokes AI to perform intelligent actions. Credit allowances are determined by the complexity of the request and the computational effort required to process it.
For example, an engineering team uses Rovo to streamline their sprint planning. When a developer asks Rovo Chat to "Summarize the blockers from the last three sprints," this triggers a billable event.
Context: Rovo credits are consumed when enriched context is returned from Teamwork Graph via TWG API and tool calls, such as when using tools like Claude or ChatGPT with the Teamwork Graph CLI or Atlassian Rovo MCP server.
Why this exists: When a third-party AI tool uses Atlassian context to do work, Teamwork Graph is supplying an input. Rovo credits provide a shared way to account for TWG’s input alongside advanced AI features.
The pricing in the table below applies to all usage and forecasts starting August 31, 2026. Usage before August 31 uses the previous pricing.
As our capabilities evolve, new or enhanced AI and Teamwork Graph features may consume Rovo credits. We will communicate any changes to billable events with transparency by updating applicable documentation.
Category of interactions | What it is | Example features | Pricing |
|---|---|---|---|
Intelligence | |||
Free | Embedded AI woven across product surfaces that enhances what you're already doing. |
| Free |
Basic | Conversational and agentic AI that provides help on demand with fast replies and light reasoning. |
| 10 Rovo credits per billable event |
Premium | Advanced AI for complex work that requires deeper thinking, more orchestration, and more context, using premium models. |
| Variable credits per billable event
|
Teamwork Graph Context | |||
Free | The Teamwork Graph (TWG) is the intelligence layer that processes context from your Atlassian and external applications. Free TWG API calls include installing the Teamwork Graph CLI and Rovo MCP or running commands to look up or update context in any single Atlassian product. |
| Free |
Enriched | Enriched TWG API and tool calls deliver deeper context from across your Atlassian and external applications to your users and agents. These calls involve complex queries, cross-product traversals, and enriched context lookups. They also encompass unified search through the Teamwork Graph CLI and Rovo MCP |
| Variable credits Vast majority of enriched TWG API and tool calls are 1-10 Rovo credits per call
|
Teamwork Graph can save you tokens
Teamwork Graph (TWG) delivers structured, relationship-aware context from your Atlassian apps and connected third-party tools, so your external AI tools can reason more efficiently and use fewer tokens to deliver a better answer.
Instead of returning raw data, Teamwork Graph traverses all your Atlassian applications and third-party tools to deliver structured context that is mapped and pre-joined before reasoning begins, including connections inferred through machine learning.
Each enriched TWG API and tool call consumes a variable amount of credits, depending on the depth of intelligence required and the operation type.
What are variable credits?
Some AI work is simple. Others are complex tasks that require deeper reasoning, more tools, more context, or longer, multi-step orchestration. Variable pricing reflects that complexity and the value delivered.
Simply put, if Rovo is doing deeper, broader, or more agentic orchestration work for you, it will generally use more credits. This model ensures the credits you use are tied to the actual computational effort required by your question.
For example, a basic chat in Quick Answer mode runs a single inference pass. Think Deeper mode dynamically plans, searches, reasons, and iterates to return a thorough answer, with built-in quality validation that automatically retries if it doesn't meet the quality bar.
Because of that difference, the number of Rovo credits used in Think Deeper mode varies based on the computational effort and complexity of your request, including:
Reasoning steps: The number of logic layers the system navigates to find an answer.
Search volume: The amount of content and data the system needs to scan and synthesize.
Tools invoked: The number of external tools and data sources invoked during the process.
Model power: The specific models applied at each stage of the reasoning process.
A look at variable credit ranges with day-to-day usage examples:
What to expect if you go over your credit allowance
Admins receive notifications when their organization’s usage reaches 80% and 100% of the included allowance.
Once you’ve hit your allowance limit:
If extra usage is on (by default): Metered features continue to work without interruption. Billing continues up to an admin-defined spending cap, at which point billable interactions pause until the allowance resets or more credits are purchased. See Manage extra usage.
If extra usage is off: billable interactions pause until the credit allowance resets or more credits are purchased.
For organizations that opt for extra usage beyond their allowance, the list price at this time is $0.01 per Rovo credit, or $10 per 1,000 credits. Prepaid usage packs are available, with volume discounts for annual credit packs.
Tip: Teamwork Collection offers the best value for Rovo usage, providing up to 10x higher Rovo allowances compared to standalone apps like Jira or Confluence on the same plan.
If you are unsure which option best fits your expected usage, contact your Atlassian account team or contact us to review your needs.
View your Rovo credit usage
Organization admins can track Rovo credit usage in Atlassian Administration. From here, you can view your total credit allowance, current usage, app-level trends, user-level usage, and which features are consuming credits.
To view your usage:
Go to Atlassian Administration. Select your organization if you have more than one.
Select Insights, then Platform usage.
Select Rovo credits.
Export usage data
For the most granular view of usage, including details like feature, user, agent, timestamp, and number of credits consumed, you can export a CSV file of usage data for Rovo credits. The export includes data starting from the earliest available date and covers up to 3 months of usage or the first 1 million usage events, whichever limit is reached first.
To export usage data:
Go to Atlassian Administration. Select your organization if you have more than one.
Select Insights, then Platform usage.
In the table, select Rovo credits.
Select Export data.
You’ll receive an email when the exported CSV file is ready to download. In the email, select Download CSV file. This link expires after 24 hours.
We will continue to add more usage visibility and management capabilities to Atlassian Administration in the coming months.
Recommended actions for using Rovo
If you are, | Recommended action |
|---|---|
Getting started with Rovo | Activate Rovo, review your included credit allowance, and set spending limits on extra usage, and monitor usage in Atlassian Administration to inform future purchasing decisions. |
Below your allowance | There’s room to experiment with more AI. Jira, Confluence, Teamwork Collection, and Service Collection come with Rovo credit allowances for you to use. Start by encouraging your team to explore Think Deeper mode in Rovo Chat to help them solve more complex problems, or try the Jira Coding Agent and Confluence Slides to go from idea to delivery in a seconds. |
Near your allowance | Review your usage dashboard to understand how your employees are using Rovo credits. Check your extra usage settings (“on” by default) in Atlassian Administration. You have the option to set spending caps on extra usage so your teams can continue to experiment while staying within your budget. Monitor over the next few months. If you are getting close to your allowance, consider whether Teamwork Collection offering 10x the Rovo credits of standalone Jira or Confluence is a better fit. |
Over your allowance | Choose one of three paths:
|
Was this helpful?