Yes, Rovo is included in Standard, Premium, and Enterprise Cloud plans of Jira, Confluence, Service Collection, and Teamwork Collection, and each paid plan comes with a monthly Rovo credit allowance per user that pools across your organization. From December 3, 2026, Rovo use beyond that allowance is billed as extra usage at Atlassian's published rate, or it pauses until the allowance resets, depending on your extra usage settings.
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.
Atlassian names four parts of Rovo: Search, Chat, Agents, and Studio.
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.
Allowances are set per user per month and depend on the app and plan:
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.
Atlassian sorts billable events into two groups: intelligence features and Teamwork Graph context. Here is how its Rovo usage limits page breaks them down.
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.
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:
Only the exhausted meter pauses. If Rovo credits run out, other meters such as Automation steps keep working.
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.
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.
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.
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.
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.
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.
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.