Atlassian Rovo pricing: what Rovo costs, how Rovo credits work, and Rovo Dev pricing

No, but it is included. Rovo has no separate per-seat charge for customers on a paid Standard, Premium or Enterprise Cloud plan of Jira, Confluence or Jira Service Management. The Atlassian pricing page states that Rovo, including Search, Chat, and Studio apps as well as agents, is available to those customers and that no separate Rovo purchase is required. So there is nothing extra to buy, and for a team already paying for Atlassian the marginal cost of turning Rovo on is zero.

The word doing the work is "included" rather than "unlimited". Rovo usage is governed by an allowance, and the Atlassian support documentation is explicit that Rovo usage is governed by your subscription tier and the number of users on your base subscription. The pricing page also refers to two distinct quotas of Rovo usage. In other words the price is capped, and so is the product.

Free trials do exist. You can evaluate Rovo through a trial of a Standard, Premium or Enterprise plan of Jira, Confluence or Jira Service Management, and Rovo Dev has its own 30-day trial. What does not exist is a permanent free Rovo tier for a company that is not already an Atlassian customer.

Rovo costs whatever your underlying Atlassian plan costs, and nothing on top of it. That means the honest answer to "how much does Rovo cost" is a range that depends entirely on which product and tier you are on, how many seats you have, and how heavily you use the AI features. There is no Rovo line item to quote.

Worked through at Standard tier using the widely reported allowance of 25 credits per seat per month, a 50-person organization has a shared pool of 1,250 credits. Reported credit consumption puts a Rovo Chat question or an agent run at roughly 10 credits and a Deep Research job at roughly 100. That works out to about 125 chat or agent requests per month for the entire company, or twelve Deep Research jobs. Spread across 50 people, that is around two and a half questions each per month.

That is the number worth sitting with before you plan a rollout, and it is why the honest framing here is not "Rovo is free" but "Rovo is included and rationed". Reported allowances of 70 credits on Premium and 150 on Enterprise change the arithmetic considerably, which is why teams that adopt Rovo seriously tend to end up upgrading tiers. Price the upgrade, not the add-on, because the upgrade is the actual cost of using Rovo properly.

One important caveat in the other direction, and it is a genuine point in favor of Atlassian: as reported in mid-2026, Atlassian is not currently billing for usage above the included allowance, requests over the pool still go through, and Atlassian has said it will give at least 90 days notice and require an explicit opt-in before overage becomes billable. That is a customer-friendly position. It is also a temporary one by its own terms, so do not build a three-year budget on it.

This is the question the entire Rovo pricing decision turns on, and it is the one Atlassian does not answer on its pricing page. We checked the Rovo pricing page and the Rovo billing documentation on August 16, 2026. Both describe the mechanism, that usage is governed by subscription tier and user count, and that there are two distinct quotas, without publishing the per-tier numbers.

The figures in circulation are 25 credits per seat per month on Standard, 70 on Premium and 150 on Enterprise, for Jira, Confluence and Jira Service Management subscriptions. Those numbers appear consistently across third-party pricing write-ups and appear to be accurate, but every trail leads back to secondary coverage rather than to an Atlassian page. This site does not state competitor figures as fact when it cannot source them, so treat 25, 70 and 150 as a planning estimate and get your own allowance confirmed in writing.

The mechanics are better documented and matter as much as the number. Credits pool across the whole organization rather than being allocated per person, which cuts both ways: a few heavy users can consume the pool that a hundred light users were meant to share, but occasional users cost you nothing. Credits reset at the end of each billing cycle and do not roll over, so an unused allowance is simply lost.

Practically, that makes Rovo capacity planning an exercise in forecasting your heaviest users, not your headcount. If three analysts start running Deep Research jobs daily, they can exhaust a mid-sized Standard pool on their own. This is the opposite of how per-seat software behaves, and it catches teams out.

As of the most recent reporting in 2026, nothing breaks. Requests above the included monthly allowance still go through, and Atlassian is not billing for that overage. Atlassian has committed to at least 90 days notice before any overage becomes billable and has said it will require an explicit opt-in rather than switching customers into paid overage automatically.

That is unusually generous, and it deserves to be said plainly rather than buried. It also means the practical experience of hitting the cap today is mild, which is exactly why so few teams have noticed the cap exists.

The risk is in the planning horizon rather than in this month. A commitment that can be withdrawn with 90 days notice is a good reason to adopt Rovo and a poor reason to assume its economics three years out. If Rovo becomes load-bearing for your support or engineering workflow and the overage policy changes, you are renegotiating from a position where the tool is already embedded. The sensible posture is to use it, measure your actual credit consumption from the admin billing view, and know what that consumption would cost if it were billed at the Rovo Dev rate of $0.01 per credit.

Rovo Dev already works that way, which makes it the best available preview of where the rest may land. It includes 2,000 credits per developer per month and charges $0.01 per credit beyond that, with extra usage auto-enabled by default specifically so that hitting the limit does not interrupt work.

Rovo Dev Standard is $20 per developer per month, quoted directly from the Atlassian Rovo Dev pricing page, and it includes 2,000 Rovo Dev credits per developer each month. Usage beyond that allowance is charged at $0.01 per credit. New Standard customers get a 30-day free trial, and there is no permanent free tier, although Atlassian has indicated it may gradually extend limited monthly Rovo Dev credits to some customers on qualifying Jira Cloud plans.

Worth being clear about what this is, because the name causes confusion in evaluations. Rovo Dev is a coding assistant for developers, not the workplace search and chat product that the rest of this page is about. If you are comparing Rovo against enterprise search tools, Rovo Dev is not the thing you are comparing, and its $20 price is not the price of Rovo.

It is still useful as a signal. Rovo Dev is the only part of the Rovo family where Atlassian publishes an allowance, an overage rate and a price together, and the fact that the model is 2,000 credits at $0.01 apiece gives you a defensible way to put a dollar value on the credits in the rest of the family. At that rate the reported 25-credit Standard allowance is worth about 25 cents per seat per month, and the 150-credit Enterprise allowance about $1.50. Whether those are the right internal transfer prices is arguable, but it is the only published rate that exists.

Start with where Rovo wins, because on its home ground it is not close. If your company runs on Atlassian and the answers you need are in Jira tickets, Confluence pages and Jira Service Management queues, Rovo is included in a plan you already pay for, it understands Atlassian object models natively, and the marginal cost of switching it on is zero. No third-party tool beats included-and-already-paid-for. If that describes you, use Rovo, and this page has done its job by telling you to.

The comparison only gets interesting when your answers are not in Atlassian. Most companies keep the decision in a Slack thread, the customer commitment in Salesforce or Gmail, the spec in Google Drive or Notion, and only the ticket in Jira. A tool that indexes the ticket returns a quarter of the answer confidently, which is worse than returning nothing, because nobody knows what is missing. InSearch connects Drive, Slack, Notion, Confluence, Gmail, Jira and Salesforce in one query and writes an answer with inline citations back to the exact source documents.

The second difference is the cost model rather than the cost. Rovo rations by credits from an org-wide pool that resets monthly and does not roll over, so the more useful your team finds it, the sooner it runs out, and heavy users consume the allowance meant for everyone. Per-seat pricing behaves the opposite way: adoption is the thing you want, and nothing punishes you for it. Which model is better depends genuinely on your usage shape, and for light, occasional use the credit pool is cheaper.

The third is permissions timing. InSearch inherits item-level permissions from each connected source and re-checks them at query time for whoever is asking, so a revoked permission takes effect immediately rather than at the next sync. That matters most when you point search at HR, finance and legal content rather than only at the engineering wiki.

The fair thing to weigh against us: Atlassian is a large public company with a support organization to match, and we are a smaller independent vendor. If vendor scale is your primary risk control, that is a legitimate reason to choose differently, and we would rather say so than pretend otherwise. The console at the top of this page runs against real content if you would rather test it than read about it.