Understanding Rovo AI credit usage and why transparent pricing matters

TL;DR

Rovo AI credit usage works like this: every paid Atlassian seat adds 25, 70 or 150 credits a month on Jira and Confluence Standard, Premium and Enterprise (250, 700 or 1,500 on Service and Teamwork Collection), pooled across the organization and reset monthly. Rovo Search, definitions and summaries are free. A Rovo Chat quick answer or a basic agent run costs 10 credits, while Think deeper, advanced agents and agents in Jira use a variable number.

From December 3, 2026, credits past the pool cost $0.01 each ($10 per 1,000), and extra usage is on by default with admin caps and alerts at 80% and 100%. The price is now published; the hard part is predicting how many credits each Premium request will use. For the full plan-by-plan view, see my Rovo pricing breakdown.

What is Atlassian Rovo?

Atlassian Rovo is the company's own AI tool, built to work as a smart layer across all their products. It can sift through your Jira tickets and pull insights from Confluence docs. Think of it as an assistant that's already familiar with your company's internal data. It's not just one feature, but a few different things working together:

• Rovo Search: This is a single search bar that can find information across all your Atlassian tools (Jira, Confluence, you name it) and even connects to outside apps like Google Drive or Slack.

• Rovo Chat: A chatbot you can ask questions to. It can give you the gist of a long Confluence page, tell you the status of a project, or handle simple tasks like creating a Jira ticket for you.

• Rovo Agents: These are the real powerhouses. They are AI-driven automations that can manage more complicated, multi-step jobs. You could use them to sort support tickets, draft release notes, or organize your project backlog, all based on rules you set.

Atlassian's big idea with Rovo is to connect all your team's scattered information and help everyone work smarter. It's a great vision, but whether it's actually useful depends entirely on how much it costs to run day-to-day.

How does the Rovo AI credit usage system work?

Rovo's pricing model is built on quotas and credits. Since September 2026 it also has a published dollar figure: $0.01 per credit past your allowance, billed from December 3, 2026. Let's dig into the details, straight from Atlassian's own Rovo usage quota documentation.

What are the two quotas behind Rovo AI credit usage?

Rovo measures how much you use it in two main ways:

• Indexed Objects: This is all about how much outside data Rovo can see. Basically, it's the size of the library the AI is allowed to read. This includes your documents from SharePoint, Google Drive, and any other apps you connect. The limit is calculated per user and then added to a shared pool for the whole company. Storing indexed objects uses no credits.

• AI Credits: This is the currency you spend when you use Rovo's actual AI features. You get a monthly allowance that resets on your usage billing date. And here's the catch: any credits you don't use disappear. They don't roll over to the next month.

Here's a look at how many AI credits you get per user, based on your Atlassian plan:

These credits get used up by different Rovo actions. Under the rate card that applies from August 31, 2026, each tier has its own cost:

In chat, each message you send is one billable event. For agents and AI features, each invocation is one.

What does Rovo AI credit usage look like in the real world?

Let's do some quick math. If your team is on the Confluence Premium plan, every user adds 70 AI credits a month to the pool. A Basic question to Rovo Chat or a basic agent costs 10 credits. That means each person averages seven Basic questions a month before the pool runs dry, and fewer if they use Think deeper or advanced agents.

Seven is a tight number if AI is meant to be a regular part of how people work. Because credits pool, light users leave room for heavy ones, but the total is the same: a 50-person Confluence Premium team has 3,500 credits (50 x 70), or 350 Basic questions.

From December 3, 2026, the overflow has a price. If that 50-person team averages 20 Basic questions per person in a month, it uses 10,000 credits (50 x 20 x 10). That is 6,500 over the pool (10,000 - 3,500), which costs 6,500 x $0.01 = $65 for the month.

The bigger issue is the variable tier. Atlassian says the credits used in Think deeper mode vary with reasoning steps, search volume, tools invoked and model power (How Rovo credits work), and Rovo can switch to Think deeper on its own for open-ended prompts. A Community Champion put it this way in March 2026, before the current rate card:

"Each Agent invocation will cost you at least 10 credits. Rovo now chooses the level of "thinking" automatically if not selected otherwise - so you may unknowingly trigger Deep Researches, costing you 100 credits."

Rebekka Heilmann, Atlassian Community

This kind of change makes users nervous. Admins remember Jira Automation moving from generous limits to metered steps, and Automation steps are now one of the meters billed from December 3, 2026 too. One r/atlassian admin said that is exactly why their team held back:

"This is exactly why we did not adopt any Rovo actions in our automation. It could have been a boon, but I knew they were just waiting for some threshold adoption level to update their pricing model."

u/Hefty-Possibility625, Reddit

Why are credit systems hard to budget for?

This isn't just a Rovo problem. Credit-based pricing models are common in the AI space, and they cause some real issues for businesses.

• It makes budgeting harder. With Rovo you now know the price of a credit, but not how many credits a Premium request will use. Your finance and operations teams need numbers they can count on. Atlassian's Platform usage dashboard shows a forecast range for the current billing cycle, which helps, but it is based on past usage.

• It holds back adoption and new ideas. When your employees are constantly worried about "using up" their monthly credits, they stop experimenting. They'll think twice before asking a question or trying out a new workflow because no one wants to be the person who triggers an extra charge. That fear keeps your team from discovering all the ways AI could actually make their jobs easier.

• You're not in control. With a model like this, the vendor sets the rate card. Atlassian replaced its credit rate card on August 31, 2026, and its docs say new or enhanced AI features may consume Rovo credits as they evolve. Once your team has Rovo built into its daily habits, the main levers you have are spending caps and switching extra usage off.

Where does Rovo fall short, and when should you use eesel instead?

Rovo does a lot well. It is built into Jira and Confluence, its search is permission-aware, Search, definitions and summaries cost no credits, and every paid seat brings an allowance.

The limits are in the metering. From December 3, 2026, credits past the pool cost $0.01 each with extra usage on by default, and Premium features such as Think deeper, advanced agents and the JSM self-service agent use a variable number of credits per request (How Rovo credits work). One admin found "a much bigger chunk of credits (2,000+) showing up under a category called "Jira Administration" with no clear feature label" (Atlassian Community).

eesel is an AI teammate that works inside Jira Service Management and Confluence, and across Slack, Microsoft Teams, email and helpdesks like Zendesk and Freshdesk. It acts on tickets: it replies to customers, adds internal notes, assigns, labels and transitions issues, and reads Confluence live for answers. One credit is one ticket or chat, however long, so a long conversation costs the same as a short one:

Every integration and seat is included, and the people asking need no Atlassian seat (Rovo's Slack and Teams apps need an Atlassian account for every asker). eesel reads Confluence read only, through one Atlassian API token, so it sees what that account can see. If you run out, agents pause, or you turn on overage at $0.80 per credit with a cap. See the Jira integration, the Confluence integration, or my list of Rovo alternatives.

eesel also answers from sources like Google Docs and Slack.

Rovo is still the better pick if your team lives entirely in Atlassian and mostly wants search and summaries it already pays for.

Choose AI with confidence, not confusion

Atlassian Rovo has useful features, and its credit model now has a clear price: $0.01 per credit past a pooled allowance from December 3, 2026. What stays hard to predict is how many credits Premium features use per request, and that extra usage is on unless an admin sets a cap.

As AI becomes a bigger part of how we work, picking a partner with a clear, predictable, and transparent pricing model is essential. You need a tool that encourages your team to experiment and find better ways of working, not one that makes them second-guess every single click.

For teams that want AI that acts on tickets without counting credits per question, eesel AI is worth a look. It puts you back in control of your workflows, your knowledge, and your costs.

Ready to try it? Start eesel AI for free with 100 credits and no card.