We first published this post in January 2026. It said Rovo came at no extra cost on Premium and Enterprise, with Standard coming soon, and told teams to experiment freely. That is no longer accurate. Rovo now covers Standard plans too, and Atlassian measures Rovo usage in Rovo credits under usage-based pricing, announced September 1, 2026.
What Rovo is
Atlassian names four parts of Rovo: Search, Chat, Agents, and Studio.
- Rovo Search searches across multiple tools at once, combining results from Atlassian apps and connected third party apps, and it respects each user's permissions.
- Rovo Chat answers questions from your company's data, using only content the user can access. It is available in Jira, Jira Service Management, Jira Product Discovery, and Confluence.
- Rovo Agents are virtual teammates that carry out specialized skills with the user's permission.
- Rovo Studio is a builder workspace that brings tools such as Automations, Company Hubs, and Assets into one place, including building agents and automations that use AI.
Atlassian turns AI on automatically for all apps on Standard, Premium, and Enterprise plans, including Rovo. If an organization admin deactivates AI, Search keeps working, while Rovo Chat and Agents become unavailable.
How many Rovo credits each plan includes
Allowances are set per user per month and depend on the app and plan:
- Jira: Standard 25, Premium 70, Enterprise 150
- Confluence: Standard 25, Premium 70, Enterprise 150
- Service Collection: Standard 250, Premium 700, Enterprise 1,500
- Teamwork Collection: Standard 250, Premium 700, Enterprise 1,500
Allowances combine into one shared pool at the organization level, and they add up across eligible apps. Atlassian's own example: 100 Jira Premium users and 100 Confluence Premium users give the organization 14,000 credits a month. Any user or app drawing on Rovo credits uses that same balance. The pool resets monthly on your usage billing date, and unused credits do not roll over. Atlassian lists allocation by user as coming soon.
Which Rovo features use credits
Atlassian sorts billable events into two groups: intelligence features and Teamwork Graph context. Here is how its Rovo usage limits page breaks them down.
Free
- Rovo Search in Atlassian apps, Definitions, and Summaries
- Installing the Teamwork Graph CLI and the Rovo MCP server
- Teamwork Graph write operations, such as updating a Jira work item, and single-product lookups
Basic: 10 credits per billable event
- Rovo Chat quick answers
- Rovo space creation
- Workforce Management Routing
- Basic Rovo agents without model selection
Premium: variable credits per billable event
- Advanced Rovo agents with model selection
- Rovo Chat Think Deeper
- Confluence slides and Create with Rovo
- Agents in Jira and the Jira Coding Agent
- Request Resolver, Alert Intelligence, and Self-service Agent
Enriched Teamwork Graph calls
Cross-product summaries, unified search tools, and complex Teamwork Graph API calls use variable credits, and that includes calls made through the Teamwork Graph CLI and the Rovo MCP server. Atlassian says most enriched calls cost 1 to 10 credits each.
Two more details matter. Features in beta don't currently count against the allowance unless Atlassian says otherwise, but they may count once they are generally available. And Rovo-powered steps inside an automation flow, such as "Use Agent" and "Use Rovo," draw from your Rovo credits allowance, not your Automation steps allowance. The credit costs above apply to usage from August 31, 2026.
What happens at 80%, 100%, and when credits run out
Organization admins and billing admins get in-product and email alerts at 80% and 100% of the included allowance, and of any limits they set. Credits are consumed in a fixed order: the included allowance first, then any prepaid packs, then extra usage.
What happens next depends on the extra usage setting for the Rovo credits meter:
- Extra usage enabled: Rovo features keep working, and the extra credits are charged on your next invoice at Atlassian's published rate. If you set a monthly extra usage limit and reach it, billable Rovo interactions pause until the allowance resets or you add credits.
- Extra usage disabled: Billable Rovo interactions pause as soon as the allowance is used, until it resets or you purchase more credits.
Only the exhausted meter pauses. If Rovo credits run out, other meters such as Automation steps keep working.
What changes on December 3, 2026
Extra usage billing for Rovo credits takes effect on December 3, 2026. That is also when usage-based billing takes effect for most of Atlassian's other meters, though Atlassian says timing may vary by capability and billing cadence. Atlassian calls September 1 to December 3 the setup period: the time to estimate usage, set extra usage preferences, and look at ways to increase allowances.
In practice, December 3 is when Rovo use above your pool starts being billed. That leaves about five weeks.
Check your extra usage setting before December 3
Atlassian's own pages don't agree on whether extra usage starts enabled or disabled. Don't assume either. Open the Rovo credits meter, and each of your other meters, in Atlassian Administration and confirm what the setting says today.
Who can change it
Organization admins and billing admins can enable extra usage (a payment method must be on file), set or update a monthly extra usage limit, and disable extra usage at any time. Atlassian's pages differ on whether billing admins can use the Insights route, so if it isn't available to you, use Billing.
Where to find it
- From Billing: In Atlassian Administration, select your organization, then Billing, then the meter from the Subscriptions list. Use the dropdown next to Get more usage to enable extra usage, select Update extra usage limit to set a cap, or use the dropdown next to Update extra usage limit to disable it.
- From Insights: In Atlassian Administration, select Insights, then Platform usage, then the meter. The same options appear there.
Our recommendation: decide on a monthly limit before December 3, not after the first invoice. With extra usage enabled, a limit keeps Rovo working past the allowance while capping spend.
Where admins see Rovo credit usage
Organization admins can open Atlassian Administration and select Insights, then Platform usage, then Rovo credits. The view shows the total allowance, current usage, trends by app, usage by user, and which features consume credits.
To export, download a CSV that lists feature, user, agent, timestamp, and credits consumed. Each export covers up to 3 months or the first 1 million usage events, whichever comes first. Atlassian emails the download link, and the link expires after 24 hours. For agent activity and audit records, see our guide on how to approve and audit Rovo agents.
Rovo needs a verified business domain
An organization admin turns on Rovo, and that admin must be on a verified business domain, such as your company email domain. Atlassian says Rovo can't be enabled for organizations registered with a generic email domain such as gmail.com or outlook.com. If Rovo won't switch on, check domain verification first.
A checklist for the next five weeks
- Confirm Rovo is on for the apps you expect, and that your organization admin is on a verified domain.
- Work out your pooled allowance from your plans and user counts.
- Open the Rovo credits meter and record whether extra usage is enabled.
- Set a monthly extra usage limit, or disable extra usage, on purpose.
- Export a usage CSV and see which features and agents consume the most credits.
- Decide who can build agents, since advanced agents and Agents in Jira use variable credits.
- Repeat the review for Automation steps, Assets objects, and your other meters. Our guide to Atlassian usage-based pricing before December 3 covers each one.
Next step: join the Rovo briefing on November 19
We are hosting a free live webinar, The complete Rovo briefing, on Thursday, November 19, 2026, from 1:00 PM to 2:00 PM EST, online. It covers how Rovo credits work, what changes on December 3, and how admins track and control usage. Bring your allowance numbers and your extra usage setting.
