Rovo FAQs

Rovo is Atlassian's AI built for teamwork, embedded directly into Atlassian apps and collections like Jira, Confluence, Teamwork Collection, and Service Collection. Powered by the Teamwork Graph, Atlassian's rich context layer which connects work, knowledge, people, and systems across first- and third-party tools, Rovo transforms fragmented information into trusted answers and context-aware agents.

Rovo allowances (measured in “credits”) are included included in these plans:

• Jira, Confluence: 25 credits / user / month (Standard), 70 credits / user / month (Premium), 150 credits / user / month (Enterprise)
• Teamwork Collection, Service Collection: 250 credits / user / month (Standard), 700 credits / user / month (Premium), 1,500 credits / user / month (Enterprise)

Shared at org level: All of an organization's allowances are combined into a single shared pool. Power users can consume more while light users consume less, with the balance spread across the org.

Stacking across apps: The more Atlassian apps you have, the larger your pool. A customer with Jira + Confluence seats gets the combined included credits for both.

Monthly reset: Allowances refresh monthly on the usage billing date.
To learn more about Rovo credits, visit Rovo usage limits

Rovo, including Search, Chat, and Studio apps as well as agents, is available to customers with a Standard, Premium, or Enterprise Cloud plan of Jira, Confluence, Jira Service Management, or Service and Teamwork Collections.

If your organization has at least one of these paid Cloud plans, Rovo will be automatically added to eligible sites as part of the rollout, no separate Rovo purchase is required.

Once Rovo is enabled on your site, users can access it directly in Jira, Confluence, and Jira Service Management by:

• using Rovo Search and Rovo Chat in the product experience
• going directly to chat.rovo.com

For step‑by‑step instructions and screenshots, see Using Rovo.

To fully leverage all of the AI features of Rovo, including search, chat, agents, and studio, an Atlassian Cloud Standard, Premium, or Enterprise plan is required.

Rovo Data Center connectors for Confluence DC and Jira DC enable customers to centralize their organization’s knowledge using AI in the Cloud. However, a Standard, Premium, or Enterprise Cloud subscription is necessary to maximize Rovo's AI capabilities.

Rovo credits are Atlassian's unit of measurement for AI feature usage and enriched Teamwork Graph (TWG) API access.

Rovo credit usage is determined by the complexity of a user’s or agent's interaction with AI features, and enriched TWG API calls, including those accessed through Teamwork Graph command line interface (CLI)  and Atlassian Rovo Model Context Protocol (MCP) server.

Rovo credits are consumed by billable events across two categories:

• Intelligence: Credits are consumed when a user or agent invokes AI to take an intelligent action on their behalf.
  • Basic AI interactions - 10 credits per billable event.
    These are the core AI interactions that every knowledge worker needs to be successful. Basic AI interactions are largely conversational and agentic AI that provide help on demand with fast replies and light reasoning.
    Example: Quick Answers mode in Rovo Chat and basic Rovo Agents.
  • Premium AI interactions - Variable pricing per billable event. This is advanced AI for complex work that requires deeper thinking, more orchestration, and more context, using premium models. Examples include: Work mode in Rovo Chat, Rovo CLI, advanced agents, and advanced AI features like Jira Coding Agent and Confluence slides.
• Context and tool calls: Certain Teamwork Graph (TWG) API and tool calls use Rovo credits. These are calls that aggregate responses from multiple Atlassian and non-Atlassian sources, and run AI inference to generate insights. This includes enriched context that is delivered to non-Atlassian tools and agents through Teamwork Graph CLI or Extend Atlassian into any AI assistant using MCP | Atlassian.
  • Enriched Teamwork Graph API and tool calls - Variable pricing per billable event, with most ranging from 1-10 credits per TWG API call. Typical prompts consume 10-25 Rovo credits total.
    • Examples:
      • The collaborators API call provides insights about collaborators by analyzing common artifacts and interactions between users in an organization. Similarly, the context API call aggregates information across multiple Atlassian and non-Atlassian systems to deliver the best context around a work item, Confluence page, or user.

For more details regarding Rovo credit usage, visit: Rovo usage allowance | Rovo | Atlassian Support

Note: View your Rovo Dev credit usage | Rovo | Atlassian Support uses a separate pricing and credit system that is independent from Rovo credits.

Billing admins can monitor and manage Rovo credit usage in Atlassian Administration. Go to Insights → Platform usage → select Rovo credits

The Rovo credits dashboard breaks usage down by app and user, so you can see trends as well as exactly what’s driving them, and take action.

You can even export your data for the most granular view of all your usage events.

Admins receive alerts at 80% and 100% of usage limits, giving you ample time to respond before features are affected.

In-flight work for users is never interrupted. If a Chat conversation or Agent task is already in progress when the limit is reached, it will complete. Only new credit-consuming requests are paused.

Once your organization exhausts its Rovo credit allowance:

• If extra usage is on (default setting): billable usage continues at the current purchase price until an admin-defined spending cap is reached. You can turn off extra usage and set spending limits in your Atlassian Administration dashboard.
• If extra usage is off: new credit-consuming AI features and enriched Teamwork Graph API and tool calls are paused until the allowance resets next month.
• What continues working: included no-cost AI features such as Rovo Search in Atlassian apps, summaries, chart insights, and definitions continue to work normally.

Options to restore access immediately:

• Enable extra usage, if it's been disabled
• Purchase prepaid Rovo credit packs
• Add seats or upgrade to a higher edition plan or Teamwork Collection to increase your organization’s Rovo credit allowance.

The number of Rovo credits used is determined by the feature type, not the surface it's triggered from. There's no "app tax" or "channel tax." A Rovo Chat question in Confluence costs the same as one in Jira, and the same as one triggered from Slack or Microsoft Teams.

The same is true for Rovo capabilities triggered from Atlassian Marketplace apps (e.g. the app encourages a user to interact with Rovo Chat, or makes a Rovo MCP call at the user’s direction). The customer uses Rovo credits based on the work that Rovo performed on their behalf, not the surface the action was triggered from.

What might differ is the allowance contribution of each app. Each paid Atlassian plan (Jira, Confluence, Service Collection, Teamwork Collection, etc.) contributes a monthly Rovo credit allowance to the customer's shared org pool based on the app, edition, and seat count.

Example: A Premium customer with 100 users on both Jira and Confluence receives 7,000 (Jira) + 7,000 (Confluence) = 14,000 Rovo credits/month in their shared pool. Those credits can be used in Jira, Confluence, Slack, Teams, or any other supported surface.

Learn more about Rovo credit usage here.

Installing and connecting to Rovo MCP Server and Teamwork Graph (TWG) CLI are free.

However, enriched API calls into TWG (including through Rovo MCP Server and TWG CLI) consume Rovo credits when they externalize Teamwork Graph context to an agentic, CLI, MCP, API, or other 3P product path.

• Example: A developer tool, external AI agent, or automation uses the TWG API to retrieve knowledge from across Jira, Confluence, and other connected sources.

Credit usage: Varies, depending on complexity. Simple cross-product lookups can be low, while complex graph traversals or cross-product context aggregation are higher. A single external AI task or agent can trigger multiple API calls, so the total credits for a prompt may be more than 10 credits.

The vast majority of enriched TWG API calls are 1-10 Rovo credits per call. 

Rovo credits are completely independent from other Atlassian meters.

Each meter tracks a different type of usage, has its own allowance, and is billed separately. They do not share a pool, and consuming one does not affect the others.

Key principles:

• No shared pool across meters: Rovo credits, Automation steps, Assets objects, Bitbucket meters, and CSM agent resolutions are each tracked in their own pool. Using more of one does not reduce your allowance for another.
• Exhausting one meter doesn't affect the others: If your org runs out of Rovo credits, your Automation flows, Assets, Bitbucket meters, and AI agent resolutions continue working normally (and vice versa).
• Each meter has its own admin controls: You can set usage limits, enable/disable extra usage, and receive notifications independently per UBP meter.
• All UBP meters are visible in one place: Admins can monitor usage across all meters in Atlassian Administration.

One important overlap: As workflows transform to bring agents into automations, you may see AI steps in automation flows.

Within an automation rule:

• AI-powered steps (e.g. assigning work to a Rovo Agent) consume Rovo credits, not Automation steps.
• The non-AI components of the same rule (triggers, conditions, standard actions) consume Automation steps
• Rovo capabilities use the same number of Rovo credits regardless of where they’re invoked from, including from within Automation flows.

No, storing indexed objects does not use Rovo credits. Indexing data via Teamwork Graph connectors expands Rovo’s searchable knowledge to return more comprehensive and accurate responses for you, but it does not cost you any Rovo credits. Rovo credits are only consumed if you take an AI action such as invoking Rovo Chat, Rovo Agents, or enriched API calls to TWG and Rovo Search via Teamwork Graph CLI or Atlassian Rovo MCP.

Atlassian provides multiple tools to help you understand your Rovo credits allowance, monitor current usage, and estimate potential costs.

Step 1: Monitor your current usage

1. Admins can view real-time Rovo credit usage in Atlassian Administration: Go to admin.atlassian.com → Insights → Platform usage → select Rovo credits

2. View your total allowance vs. current usage

• Check the Apps tab to see where usage is concentrated within individual apps
• Check the Users tab to see per-user consumption
• Click Export Data for the most granular view of all your usage events
   

Step 2: Forecast future usage
Atlassian provides forecasting tools to help you estimate usage:

• In-product forecasting: The Platform usage dashboard shows a forecasted range of extra usage for your current billing cycle, based on your org's historical usage trends.
   

Step 3: Estimate extra usage costs
If your org exceeds its included allowance, you have the following options:

• Upgrade to Teamwork Collection for 10x the allowances per tier compared to standalone app subscriptions.
• Pay as you go: Pay at the list price of $0.01 per credit over your allowance ($10.00 per 1,000 credits)
  • If your org uses 35,000 Rovo credits in a month with a 28,000 Rovo credits allowance, your cost for the month is:
    • Extra usage = 7,000 credits
    • Extra usage cost = 7,000 × $0.01 = $70 for that month
• Pre-pay: Volume discounts are offered for prepaid credit packs, depending on commitment level at time of purchase.
• Turn off extra usage: New credit-consuming AI features and enriched Teamwork Graph API and tool calls are paused until the allowance resets next month.

Learn more about managing your usage and billing: General Purchasing and Licensing FAQs

Atlassian provides multiple resources to help you understand Rovo credits, manage your usage, and get support when you need it.

For help understanding Rovo credits:

Customers can trial Rovo through a trial of our Standard, Premium, or Enterprise plan of Jira, Confluence, and Jira Service Management.

Rovo Dev is an AI agent that expands on Rovo's capabilities, specifically designed for professional software engineers. It handles code planning, code generation, code reviews, and automates repetitive work at scale. Rovo Dev has separate pricing and packaging from Rovo.

Rovo Dev is ideal for software development teams, engineers, and technical leads who want to streamline their work, reduce manual tasks, and improve access to knowledge across their tools and projects.

Rovo Dev Standard is priced at $20 per developer per month, which includes 2,000 Rovo Dev credits per developer per month. If you need more credits, extra usage is billed at $0.01 per credit.

Rovo Dev has separate pricing and packaging from Rovo. To learn more about Rovo Dev pricing, please visit this page.

To get started, sign up for a 30-day free trial here: Sign up - Try Atlassian Cloud | Atlassian

Rovo enables teams with AI capabilities such as search, chat, and studio apps. To learn more about what's available with Rovo, please visit this page.

Rovo Dev is an AI agent that expands on Rovo capabilities, specifically designed for professional software engineers. It handles code planning, code generation, code reviews, and automates repetitive work at scale. To learn more about what's available with Rovo Dev, please visit this page.

You can find support resources here: Work with Rovo Dev

Interactions with specific Rovo Dev AI features are metered using Rovo Dev credits

Rovo Dev Standard comes with an allowance of 2000 Rovo Dev credits per user. Each user has a default of 2,000 Rovo Dev credits each month to use or lose.

When a user's credit quota limit is reached, additional usage incurs charges of $0.01 per credit. To avoid service disruptions, Rovo Dev Standard will have a default extra usage of 2,000 Rovo Dev credits per user per month auto-enabled.

Admins can set custom limits and controls on a per-site basis. Customers can monitor their Rovo Dev credit usage with the Platform usage dashboard in Atlassian Administration.

We don't require upgrading your entire site to Rovo Dev Standard. Seats can be purchased for individual developers.

The Atlassian Customer Agreement covers both Atlassian Intelligence and Rovo. Additionally, the policies and terms incorporated by reference in the Atlassian Customer Agreement, including the Privacy Policy, Acceptable Use Policy, Data Processing Addendum, Product-Specific Terms, govern your use of Atlassian Intelligence and Rovo.

Loom AI is governed by separate terms located on the Product-Specific Terms page.

AI is available and automatically activated for all apps on Standard, Premium, and Enterprise plans. If you’re not ready for AI, organization admins can deactivate it.

If you deactivate AI, Rovo's core apps like search and studio will still work, but AI-powered search and chat features will be unavailable.