Rovo Pricing: Atlassian Rovo Cost, Rovo Agents and Rovo Credits

Rovo is included at no additional cost with any paid Atlassian Cloud plan, but it is not free to use without limit and there is no free standalone tier. Atlassian began the "Rovo for all" rollout on April 9, 2025, and its billing documentation is explicit: once Rovo is enabled for your subscription you will not be invoiced separately for it, and organizations that had previously bought Rovo stopped being billed once they were moved onto the new offering.

Three qualifications matter, and all three catch people out.

The first is that Rovo does not come with Free plans. Eligibility starts at Standard on Jira, Confluence, Jira Service Management, the Service Collection or the Teamwork Collection. If your team is on the free tier of Jira, the cheapest legitimate route to Rovo is Confluence Standard at $6.70 per user per month or Jira Standard at $7.91, which is $80.40 and $94.92 per user per year respectively.

The second is the credit allowance, covered in detail below. Rovo is free the way a phone plan with an included data cap is free.

The third is an administrative requirement that is easy to miss and blocks activation outright: Atlassian will only enable Rovo for organizations registered on a verified business domain. If your Atlassian organization was set up under a gmail.com or outlook.com address, Rovo cannot be turned on until that changes.

Rovo itself costs $0. The price you actually pay is the price of the qualifying Atlassian plan underneath it, so the honest way to quote Rovo is to quote the cheapest plan that includes it. These are Atlassian's published US list prices, read from the pricing pages on August 31, 2026.

Confluence and Jira list prices are shown for the default monthly selection Atlassian displays, and the Service Collection figures are per agent at its default 75-agent monthly selection. Atlassian moves to volume-banded pricing at larger seat counts and Enterprise is annual and quote-only, so treat these as the small-to-mid-team list rather than what a 2,000-seat company pays.

The comparison that makes Rovo look cheap

The reason Rovo pricing gets attention is not the credit pool, it is the incremental cost, which is zero. Every other major enterprise AI assistant charges a per-seat fee on top of a base license. Microsoft 365 Copilot is $30 per user per month as an add-on. Google's Gemini Business seat is $21. Rovo is $0 on top of a Jira or Confluence subscription you were already buying.

That $0 column is real and it is the strongest thing about Rovo's commercial position. It is also why the credit allowance matters so much: the allowance, not the invoice, is where Atlassian sets the actual limit on how much AI you get.

Rovo credits, which Atlassian previously called AI credits, are consumption units spent when you use the more expensive Rovo features. Atlassian documents four properties that together define the budget, and the third and fourth are the ones that bite.

Credits are granted as a fixed allowance per seat per month based on your edition and the apps you subscribe to. They are pooled at the organization level, so the allowance scales with total seats rather than being locked to an individual. They reset monthly. And they do not roll over, so an unused allowance is gone at the end of the billing cycle.

Pooling is the property most worth understanding, because it cuts both ways. Atlassian's own worked example: a company with 100 users on Confluence Premium, 50 of whom are also on Jira Premium, gets (100 x 70) + (50 x 70) = 10,500 Rovo credits per month. One heavy user can draw on the whole pool, which is generous if adoption is narrow and dangerous if it is not.

What consumes Rovo credits

What does not consume Rovo credits

Several things are explicitly free, and they are the reason a lot of Rovo users never notice the meter at all. Rovo Search queries through Atlassian apps cost nothing. So do summaries across Atlassian apps, definitions, and chart insights in Atlassian Analytics. Features still in beta remain free and do not count against the allowance unless Atlassian says otherwise, and storing third-party indexed objects is not charged, appearing in the usage dashboard for visibility only.

The practical split is clean: reading is free, reasoning is metered. If your use of Rovo is enterprise search over Jira and Confluence, you will likely never touch the allowance. The moment you deploy agents, you are on the meter.

This is the arithmetic that decides whether Rovo works for your team, and Atlassian publishes both halves of it without ever putting them together. Take the allowance, divide by the 10-credit cost of an agent or Quick Answer request, and the picture changes completely.

A Jira or Confluence Standard seat earns 25 credits a month. That is two and a half agent requests per person per month. Not per day, per month. A Premium seat earns 70, which is seven requests. An Enterprise seat earns 150, which is fifteen.

Put that against a realistic rollout. A 100-person company on Jira Standard has an org-wide pool of 2,500 credits a month, which funds 250 agent requests for the entire company. If ten people adopt Rovo properly and each runs an agent twice a working day, those ten people alone need roughly 4,400 credits a month, which is nearly double the whole company's allowance. The pool empties in the second week, and it empties fastest in exactly the month your rollout is going well.

Deep Research does not fit inside a seat

The starkest number here is Deep Research at 100 credits. A Standard seat earns 25 a month, so a single seat cannot fund one Deep Research query. It takes four Standard seats pooled together to pay for a single one. Even a Premium seat at 70 credits falls short of one. Only Enterprise, at 150, funds one and a half per seat per month.

That is not a criticism of the feature, which does genuinely expensive work. It is a warning about how it gets demonstrated. Deep Research is the feature that sells Rovo in a demo, and it is the feature your plan can least afford to have people use casually.

What the allowance is worth in dollars

Atlassian does not publish a dollar value for a Rovo credit. It does publish one for a Rovo Dev credit, at $0.01, and that is the only credit price Atlassian puts a number on anywhere. The two are different currencies and Atlassian does not equate them, so what follows is a reference point rather than an official conversion.

Priced at that rate, a Standard seat's 25 credits are worth about $0.25 a month, a Premium seat's 70 about $0.70, and an Enterprise seat's 150 about $1.50. Now look at the upgrade. Moving Jira from Standard to Premium costs $6.63 per user per month and adds 45 credits, worth roughly $0.45 at Atlassian's own credit rate. On Confluence the same upgrade costs $6.50 for the same 45 credits.

To be fair to Atlassian, nobody buys Premium for the credits. Premium also brings advanced roadmaps, sandbox environments, release tracks, IP allowlisting, unlimited storage and 24/7 support, and those are the reasons the upgrade exists. But if a vendor tells you to upgrade the edition to solve a Rovo credit shortage, this is the number to have in front of you: the AI allowance is a rounding error inside that upgrade, and there are cheaper ways to buy request volume.

Buried in Atlassian's allowance table is the single largest pricing lever in the whole Rovo model, and it is easy to walk straight past because it looks like a formatting quirk.

Every individual app grants the same allowance: Jira Standard 25, Confluence Standard 25, Jira Service Management Standard 25. The Teamwork Collection grants 250. The pattern holds at every edition, with the Collection at 700 against Premium's 70, and 1,500 against Enterprise's 150. The Teamwork Collection carries exactly ten times the Rovo credit allowance of any single app on the same edition.

The consequence is worth stating plainly. A Teamwork Collection Standard seat gets 25 agent requests a month, which is more than an Enterprise seat on a single app gets at 15. If credit volume is what you are short of, moving to the Collection is a far more direct fix than climbing the edition ladder, and it usually consolidates products you were buying separately anyway.

Check the Collection's own list price against what you currently pay for the individual apps before you act on this, because the Collection bundles several products and the comparison depends on which of them you already own. But if two teams are arguing about whether to go Premium for AI reasons, this is the row that should end the argument.

As of August 31, 2026, nothing is charged. Atlassian's usage-allowance documentation states that it is not currently billing for usage above your Rovo credit allowance, that it will give at least 90 days notice before credit limits take effect, and that you will never be billed for extra usage unless you explicitly opt in for your organization.

That is an unusually generous position and it is the most important date-sensitive fact on this page. It is also, by Atlassian's own framing, temporary. The company is telling you the meter exists, that it is watching consumption, and that enforcement is coming with notice. Atlassian also said Rovo credits and variable rates would appear in the Atlassian Administration dashboard from August 2026, which is what you would build before you start charging.

The practical reading for a US buyer: do not build a business case on unmetered Rovo. Build it on the published allowance, treat today's non-enforcement as a grace period, and check the allowance page again before your next renewal. If you are relying on Rovo doing more than your allowance covers, you are relying on a policy Atlassian has explicitly reserved the right to change.

Two controls exist in the meantime. Organization admins get proactive email and in-product notifications as usage approaches 80% and 100% of the monthly allowance, and admins can set limits capping additional credit usage if they ever choose to enable it. Extra usage for Rovo is disabled by default, which is the safe setting and worth confirming rather than assuming.

Atlassian's naming causes real confusion on procurement calls, because "Standard" means two different things depending on which noun it follows.

Jira Standard, Confluence Standard are editions of an Atlassian app. They are what grants you the 25-credit Rovo allowance.

Rovo Standard is something else entirely: a way to give people in your organization standalone access to key Rovo features even when they have no paid subscription to an Atlassian app. It is currently in beta. Atlassian's documentation says that after the beta ends you will automatically return to Rovo Free unless you opt in to the paid Standard plan, with at least 90 days to decide. If you are counting on standalone Rovo seats for non-Jira staff, that is a beta you are planning around, not a shipped product.

Rovo Dev is a separate purchase with its own price, its own credit currency and its own overage rules. It is $20 per developer per month, includes 2,000 Rovo Dev credits, charges $0.01 per credit beyond that, and has no free tier. Rovo Dev credits and Rovo credits are not interchangeable. We break the developer seat down in full in our guide to Rovo Dev pricing and its credit overage.

One more distinction that saves money: Rovo Dev seats are bought per developer, not per site. Atlassian states it does not require upgrading your entire site to Rovo Dev Standard, so you can license the six engineers who will use the CLI and code review rather than everyone with a Bitbucket login.

Rovo is the obvious choice, and close to unbeatable on price, when your knowledge already lives in Jira and Confluence and what you want is search, summaries and definitions across it. Those features cost no credits at all, they are included with a subscription you already hold, and no competing product will beat $0 incremental.

Rovo gets harder to justify in three situations, all of them about volume rather than quality.

The first is broad agent adoption. If the plan is for most of a department to use an agent most days, the allowance is the constraint, and 2.5 requests per Standard seat per month is not a rollout budget. Either the edition changes, the Collection gets bought, or a flat-rate agent handles the high-frequency work.

The second is heavy research use. Deep Research at 100 credits a request is priced for occasional, high-value questions, not for a team that wants a cited analysis every morning.

The third is work that lives outside Atlassian. Rovo's advantage is the Teamwork Graph, and that advantage shrinks the further your process sits from Jira, Confluence and Bitbucket. If the job is triaging a shared inbox, chasing invoices or working a CRM, a purpose-built agent connected to those systems will do more for less.

The pragmatic answer for most teams is not either-or. Keep Rovo for the free tier of work, which is search and summarization across Atlassian content, and put the high-frequency, high-volume jobs on a flat-rate agent where a busy month does not empty a shared pool. You can browse ready-made AI agents that connect to Jira and run at a fixed monthly price, alongside Rovo rather than instead of it.