Atlassian Rovo Pricing, Rovo Dev Pricing and What Rovo Credits Cost

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. Companies without Jira or Confluence can now use Rovo Standard, which Atlassian describes as "standalone access to Rovo": free during its beta and $5 per user per month after an opt-in, with 400 credits per user. Organizations that do not opt in move to Rovo Free, with at least 90 days to decide.

Rovo costs whatever your underlying Atlassian plan costs, plus, from December 3, 2026, $0.01 for every credit used above the included allowance. 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 published allowance of 25 credits per seat per month, a 50-person organization has a shared pool of 1,250 credits. Atlassian prices a basic AI interaction, a Quick answers question in Rovo Chat for example, at 10 credits, and says typical prompts consume 10 to 25 credits once enriched Teamwork Graph calls are counted. That works out to somewhere between 50 and 125 questions per month for the entire company. Spread across 50 people, that is one to 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". 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 caveat in Atlassian's favor: until December 3, 2026, requests over the pool still go through unbilled. From that date extra usage is billed at $0.01 per credit and is enabled by default, with alerts at 80 and 100 percent and an admin-defined spending cap, so set the cap before the date rather than after the first invoice. For a 100 person team on Jira and Confluence Premium, the cost at different usage levels is worked through in Atlassian Rovo vs Glean pricing.

Atlassian now publishes the allowance. Jira and Confluence include 25 Rovo credits per user per month on Standard, 70 on Premium and 150 on Enterprise. The Teamwork Collection and Service Collection include 250, 700 and 1,500. Both the Rovo pricing page and the Rovo credits documentation carried these figures on September 21, 2026; until recently they appeared only in third-party write-ups, and this page labeled them as reported. They are now quoted from Atlassian.

The mechanics matter as much as the number. Credits are shared at the organization level and stack across apps, so Atlassian's own example of 100 Jira Premium users plus 100 Confluence Premium users is 7,000 plus 7,000, or 14,000 credits a month in one pool. That 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. Allowances reset monthly on the usage billing date and unused credits do not roll over.

What consumes them is also now on a rate card, effective August 31, 2026. Embedded features such as Rovo Search in Atlassian apps, definitions and summaries are free. Basic AI interactions, including Rovo Chat quick answers, cost 10 credits per billable event. Premium interactions, such as Think Deeper mode in Rovo Chat and advanced agents with model selection, are variable. Enriched Teamwork Graph API and tool calls, which include unified search through the Rovo MCP server and CLI from tools like Claude or ChatGPT, are variable too, with the vast majority at 1 to 10 credits per call, and Atlassian says a typical prompt lands at 10 to 25 credits in total. Features in beta do not count against the allowance unless stated.

Practically, that means a Standard seat funds one or two real questions a month and an Enterprise seat perhaps ten. Teams that adopt Rovo seriously end up on the Teamwork Collection or paying the overage, which is the next section.

From December 3, 2026, you pay for it. Atlassian's Rovo credits documentation states that on that date "extra usage billing takes effect for Rovo credits", that extra usage "is enabled by default", and that the list price is "$0.01 per Rovo credit, or $10 per 1,000 credits." Admins are notified at 80 and 100 percent of the allowance and can set a spending cap in Atlassian Administration; when the cap is reached, billable interactions pause until the allowance resets or more credits are bought. With extra usage switched off, billable features pause at 100 percent instead. In-flight chats and agent runs always complete.

This is a real change and it is worth recording what it replaced. Through the summer of 2026 Atlassian was not billing for usage above the allowance and had committed to at least 90 days notice and an explicit opt-in before it did. The notice was given; the opt-in became a default-on setting with an admin-defined cap. If your organization adopted Rovo on the strength of free overage, the budget assumption expires on December 3, 2026, and the default is that you keep consuming and start paying.

What keeps working when the pool is empty is the free tier of features: Rovo Search inside Atlassian apps, summaries, chart insights and definitions. What pauses is the metered tier: Rovo Chat, agents, Think Deeper, and enriched Teamwork Graph calls from external tools. The three documented ways back are to enable extra usage, to buy prepaid usage packs at volume discounts Atlassian does not publish, or to add seats or move up an edition, and Atlassian is explicit that the Teamwork Collection is the intended upgrade path, with up to ten times the standalone allowance.

Rovo Dev already worked this way, which is why this page used it as the preview of where the rest would land. It includes 2,000 credits per developer per month and charges $0.01 per credit beyond that. The same $0.01 now applies across the Rovo family, so a Standard seat's 25 credits are worth 25 cents a month at list and an Enterprise seat's 150 credits are worth $1.50, which is the number to compare against a per-seat search product before assuming "included" means cheap at scale.

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 was the first part of the Rovo family where Atlassian published an allowance, an overage rate and a price together, and the rest of the family now follows the same model, so 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.