Rovo Credits Per User (2026): How Many Does Your Team Need
Written by
Nisha BhartiThe right number of Rovo credits per user is whatever your team's measured usage consumes, not the plan allowance divided by 10. A Jira Premium seat's 70 credits covers about 7 Basic chat messages a month. On Atlassian's current rate card, Search and Summaries are free, every Basic chat message (Quick Answers) costs 10 credits, and Think deeper, advanced agents and the Jira Coding Agent cost a variable amount.
To size your Rovo credit pool reliably, export your organization's usage since August 31, 2026, group users into light, regular and heavy profiles, and compare that demand with the allowance your seats provide. With extra usage billing starting on December 3, 2026, now is the time to do it.
What's new in this update (November 2026)
- Loom now has a Rovo credit allowance: 25, 70 or 150 credits per user per month, depending on the Loom plan.
- Extra usage is on by default, Atlassian now confirms. Check your setting and set a spending cap before December 3.
- Code Reviewer moves into the Rovo credit pool on December 3, 2026. If your developers use AI code reviews, they now count.
- Team '26 Europe added new ways to use credits, including Rovo Work, scheduled chats and the Rovo desktop and mobile apps.
Key takeaways
- Rovo credits per user range from 25 to 1,500 a month, depending on product and plan. All of them pool at the organization level and reset monthly.
- Each Basic chat message costs 10 credits, so conversational use burns credits far faster than "10 per chat" estimates suggest.
- Agents in automation rules, help-center agents, enriched Teamwork Graph calls and, from December 3, Code Reviewer all draw on the same pool without adding a single seat.
- Extra usage billing for Rovo credits starts on December 3, 2026, at $0.01 per credit beyond your allowance. Extra usage is on by default.
- Size your Rovo credits per user budget on expected demand, and your spending cap on peak demand plus headroom.
Why trust this guide:
Empyra is an Atlassian Platinum Solution Partner with 15+ years of Atlassian experience, 80+ certified consultants and 1,000+ customers, including Rakuten, Victoria's Secret, Houston Community College, Sally Beauty and UC Office of the President. This is the sizing method our Atlassian license management services team uses ahead of the December 3, 2026 billing change. Every rule in this guide is checked against Atlassian's How Rovo credits work page, last updated by Atlassian on October 22, 2026.
For the fundamentals of what credits are and how overage works, read our Atlassian Rovo pricing guide. This post turns those rules into a number for your organization.
What changes on December 3, 2026
December 3, 2026 is the day usage-based pricing starts to cost money. From that date, Atlassian bills extra usage for Rovo credits: any usage beyond your organization's pooled monthly allowance is charged at $0.01 per credit. Atlassian states that extra usage is on by default, so work keeps running and billing continues up to any spending cap you set. If extra usage is off, billable features pause until the allowance resets.
Two other changes land on the same day:
- Automation steps. Usage billing starts for automation steps in Jira and Confluence cloud, so most teams face two meters at once. Our guide to Jira automation pricing covers that side.
- Code Reviewer. Rovo Dev's AI code reviews move from Rovo Dev credits to your Rovo credit pool, as part of your Jira or Teamwork Collection subscription (Atlassian Rovo Dev FAQ).
Before December 3, do four things:
- Export your Rovo usage since August 31, 2026 and size your pool with the method below.
- Check your extra usage setting in Atlassian Administration. Atlassian says it is on by default, but confirm it for your organization, then set a spending cap.
- Make sure organization and billing admins receive the 80% and 100% usage alerts.
- If your developers use Code Reviewer, add a line for code reviews to your forecast (see Step 3).
Rovo credit allowance by plan
Every paid Jira, Confluence, Service Collection and Teamwork Collection cloud subscription includes a per-user monthly allowance of Atlassian Rovo credits.
|
Offering |
Standard |
Premium |
Enterprise |
|
Jira |
25 |
70 |
150 |
|
Confluence |
25 |
70 |
150 |
|
Loom (new) |
25 (Business) |
70 (Business + AI) |
150 |
|
Service Collection |
250 |
700 |
1,500 |
|
Teamwork Collection |
250 |
700 |
1,500 |
Rovo credits per user per month. Source: Atlassian, How Rovo credits work.
How many credits your organization gets: monthly pool by size
|
Users |
Jira or Confluence Standard (25) |
Jira or Confluence Premium (70) |
Jira or Confluence Enterprise (150) |
Teamwork Collection Premium (700) |
|
50 |
1,250 |
3,500 |
7,500 |
35,000 |
|
200 |
5,000 |
14,000 |
30,000 |
140,000 |
|
500 |
12,500 |
35,000 |
75,000 |
350,000 |
|
2,000 |
50,000 |
140,000 |
300,000 |
1,400,000 |
Rovo credits per month for one product. Add each product your users hold, because allowances stack in one pool. At 10 credits per Quick Answers message, a Jira Premium user's share covers 7 messages a month.
Three rules decide how these allowances behave in practice:
- They pool across the organization. A person with Jira, Confluence and Loom seats adds all three allowances to one shared pool. Atlassian lists per-user allocation as "coming soon".
- They reset monthly. Allowances refresh on your usage billing date, and unused credits don't roll over. Always size against a single month.
- Rovo Dev is changing. Today, Rovo Dev uses its own credits. From December 3, 2026, Code Reviewer draws on the Rovo credit pool instead, and Atlassian says standalone Rovo Dev will reach end of life (date to be confirmed, with at least 60 days' notice). The Rovo Dev CLI is moving to the Atlassian Rovo CLI under usage-based pricing later. Keep a separate line for code reviews in your model.
Why "seats × allowance ÷ 10" no longer works
Most published estimates of Rovo credits per user divide the allowance by a flat 10 credits per interaction. On Jira Premium, that gives 70 ÷ 10 = 7 interactions per person per month. On the current rate card, this shortcut fails in four ways.
It counts free usage as paid.
Rovo Search, Definitions and Summaries cost nothing. A user who mostly searches and summarizes may barely touch their share.
It counts conversations, not messages.
Atlassian bills each user message in chat as a separate event. A five-message thread in Basic chat, which Atlassian's credits page bills as Quick Answers, costs 50 credits, not 10.
It ignores variable Premium work
Several features are billed at variable rates:
-
Think deeper mode in Rovo Chat
-
Deep research mode, which can run for up to 15 minutes on a single request. Atlassian's credits page doesn't list it by name, so check its line in your usage export and treat it as one of your most expensive features.
-
advanced agents with model selection
-
Agents in Jira and the Jira Coding Agent
-
Confluence slides and Create with Rovo
-
Request Resolver, Alert Intelligence and the Self-service Agent
Each one's cost depends on reasoning steps, search volume, tools invoked and model power. Atlassian's rate card groups Premium work into three estimated ranges:
|
Task type |
What it involves |
Estimated Rovo credits per task |
|
Light |
Few sources, light reasoning, one output (e.g. AI-generated Confluence slides) |
10–200 |
|
Medium |
Many sources across time, structured reasoning, two or more outputs (e.g. release notes plus stakeholder updates) |
201–500 |
|
Heavy |
Broad aggregation, deep reasoning, multiple outputs (e.g. cross-team agents tracking roadmap risk) |
500+ |
Source: Atlassian's Rovo credits task-type rate card on How Rovo credits work, as of 22nd Oct, 2026.
Put that next to the allowance table. A single light Premium task can use more than a Jira Premium user's entire 70-credit monthly share. These are estimates, which is why your own usage export is the only reliable way to price Premium work for your team.
It ignores demand that isn't tied to a seat.
Several sources draw on the same pool without adding a licensed user:
- Rovo agents triggered by automation rules ("Use Agent" actions) consume Rovo credits for each agent invocation. The rule's own triggers, conditions and actions run on automation steps.
- Customer-facing agents in a JSM help center.
- Third-party AI tools such as Claude or ChatGPT that pull context from the Teamwork Graph through the Atlassian Rovo MCP server or the Teamwork Graph CLI. Atlassian now bills this as a separate "Teamwork Graph context" category: installing the tools, write operations and single-product lookups are free, while enriched calls such as cross-product search are mostly 1 to 10 credits each.
- From December 3, 2026, Code Reviewer reviews on pull requests.
One more catch: Atlassian applies the new rate card only to usage from August 31, 2026 onward. Averages built on earlier usage, including your own, measure the old model.
New Rovo credit drivers from Team '26 Europe
At Team '26 Europe in October 2026, Atlassian announced several features that make Rovo easier to use, and easier usage means more Rovo credits per user. Atlassian hasn't published per-feature rates for most of them yet, so plan for them as their own lines and watch the Features tab in your usage dashboard.
|
Feature |
Status |
How it uses Rovo credits |
What to do |
|
Code Reviewer (Rovo Dev) |
Moves to Rovo credits on Dec 3, 2026 |
Metered in Rovo credits; no per-review rate published yet |
Add a code review line to your forecast (see Step 3). Keep reviews on "when a PR is created", not on every commit |
|
Rovo Work |
Announced |
Longer, multi-step tasks that can run for minutes to hours and run with the starting user's permissions. Rate not published |
Treat it as heavy Premium work until Atlassian publishes a rate |
|
Scheduled chats |
Announced |
Recurring chats run without anyone sending the message. Rate not published |
Review who schedules what, and treat each scheduled run as at least one chat message |
|
Rovo desktop and mobile apps |
Desktop shipped, mobile rolling out |
Same chat modes as the web, so the same rates apply |
Expect chat volume to rise as access gets easier |
|
Agents in Jira (Rovo, Claude, Cursor, Copilot) |
Available in Jira Cloud |
Agents in Jira and the Jira Coding Agent are variable Premium. Third-party agents are billed by their own vendors, but their Teamwork Graph calls can use Rovo credits |
Track agent rows separately in your export |
|
Planner |
Early access |
Beta features don't count against your allowance unless Atlassian says otherwise |
Keep it as a "watch" line for when it reaches general availability |
If you want visibility across all of this, Atlassian also announced AI spend tracking in the Strategy Collection (open beta) and Model Fit in DX, which flags agent runs that could use a cheaper model. To see where your credits go feature by feature, read our guide to Atlassian AI costs [link the anchor 'Atlassian AI costs' to the AI Costs blog URL]. For the bigger picture of how agents now work across Atlassian, read our guide to Atlassian AI agents and AMP.
How many Rovo credits per user do you need? A 5-step sizing method

Step 1: Measure a baseline from your own usage
Organization admins can see usage in Atlassian Administration → Insights → Platform usage → Rovo credits. The dashboard shows:
- total allowance and current usage
- app-level trends
- user-level usage
- Which features consume credits
For sizing, you need the raw data, so select Export data. The CSV records feature, user, agent, timestamp and credits consumed per event. It covers up to three months or one million events, whichever comes first, and the download link expires after 24 hours.
Filter the export to events dated August 31, 2026 or later. Then build three summaries:
- Credits per user per month, sorted high to low. This feeds Step 2.
- Credits by feature. This shows whether demand comes from Basic chat, Premium reasoning or agents.
- Credits with no human user, such as automation agents, help-center agents and MCP/Teamwork Graph calls. These scale with ticket volume and integrations, not headcount, so they get their own line.
If Rovo is new to your organization and you have no usage data yet, start with our calculator to estimate Rovo credit usage by team size, then run a short pilot with a representative group to replace that range with real numbers.
Step 2: Group users into usage profiles
Rovo credits per user vary too much from person to person to model one by one. Profiles let you forecast the pool as a whole.
Split the per-user list from Step 1 at clear breaks in the data, then record each group's median credits per month. Medians stop one experimental power user from inflating a whole group. The worked examples below assume a median of 40 credits for light users, 420 for regular users, and 420 Basic credits plus Premium usage for heavy users. These are planning assumptions, not Atlassian benchmarks; replace them with your measured values. Because these examples count Basic usage only, they sit well below the planning bands in our Rovo credits calculator, which also include Think deeper, research and agent usage.
Step 3: Model your Rovo credit pool
Now compare supply (your seats' allowances) with demand (your profiles plus non-seat usage).
Rovo credit sizing worksheet
|
Line |
How to calculate |
Example: 60-user dev team on Jira Premium |
|
|
A. Monthly supply |
Σ (licensed users per product × plan allowance) |
60 × 70 = 4,200 |
|
|
B. Light demand |
light users × median credits |
20 × 40 = 800 |
|
|
C. Regular demand |
regular users × median credits |
30 × 420 = 12,600 |
|
|
D. Heavy demand |
heavy users × median credits (Basic + Premium) |
10 × 420 = 4,200 + Premium |
|
|
E. Non-seat demand |
automation agents + help-center agents + enriched Teamwork Graph / MCP calls |
0 in this example |
|
|
F. Monthly demand |
B + C + D + E |
17,600 + Premium |
|
|
G. Expected gap |
F − A (a negative number means spare allowance) |
13,400 + Premium |
|
|
H. Expected overage cost |
G × $0.01 per credit |
about $134/month + Premium |
|
Line H uses Atlassian's current list price for extra usage: $0.01 per credit, or $10 per 1,000 credits.
Don't have a full export yet? The Rovo credits calculator gives a monthly planning range by team size and usage profile. Use it for a first estimate, then refine it with this worksheet. It covers Rovo credits only, so size automation steps separately.
Step 4: Add headroom before you set a cap
A pool sized for this month's demand will usually be short within a quarter. Plan for three kinds of growth:
- Beta features going GA. Beta AI features don't count against your allowance today, but Atlassian notes they may once generally available. Model every beta feature your teams use as if it were billed at its closest tier.
- New Team '26 Europe features. Rovo Work, scheduled chats and the desktop and mobile apps make Rovo easier to use every day. Expect usage to rise as they roll out.
- Adoption growth. Usage in the weeks after rollout rarely reflects steady state. If your export shows month-over-month growth, carry the trend forward.
- Monthly variance. Size against your busiest month, not the average. Release cycles, quarter-end reporting and incident spikes push usage up at predictable times.
Pick a headroom percentage that matches the variance you actually saw, and apply it to line F. Use this padded figure for your spending cap. Keep line H unpadded, so finance sees expected spend while the cap sets the ceiling.
Step 5: Decide how to cover the gap
If line G is positive, you have three options.
Keep extra usage on, with a spending cap. Atlassian's documentation is inconsistent on whether extra usage is enabled by default, so confirm the setting in Atlassian Administration first. Set the cap at (padded demand − supply) × $0.01 in Atlassian's extra usage settings. This suits small or uncertain gaps. Admins get alerts at 80% and 100% of the allowance either way.
Buy prepaid usage packs. If the gap is steady, packs make the budget predictable, and Atlassian offers volume discounts on annual packs. Pack sizes and discounts depend on your agreement, so ask your Atlassian partner for a quote.
Move to a higher-allowance collection. Service Collection and Teamwork Collection include 10× the Rovo allowance of standalone Jira or Confluence on the same plan. Compare the license price difference against twelve months of line H. Note that list prices change on October 13, 2026, as covered in our Atlassian cloud price increase 2026 breakdown, so quote the collection at the rate you'll actually renew on.
One caution when you clean up licenses at the same time: reclaiming inactive seats lowers license cost but also shrinks your pool, because every seat carries its allowance. Run your Atlassian license optimization and your Rovo sizing as one exercise, not two.
Want a second pair of eyes on your usage export? Empyra's license management team will read your export, build the worksheet with you and recommend a spending cap before December 3.
Worked scenarios
These scenarios show how Rovo credits per user play out in three common setups. They use Atlassian's published allowances and the $0.01 overage rate. The usage figures are illustrative assumptions chosen to show how the method behaves. They are not benchmarks or client data. Premium usage is left as a line to fill from your own export.
Rovo credits for Jira Service Management: ITSM team on Service Collection Premium
-
- Supply: 40 agents × 700 = 28,000 credits
- Regular demand: 40 agents × 3 Quick Answers messages × 21 days × 10 = 25,200
- Non-seat demand: 3,000 requests per month routed by Workforce Management Routing × 10 = 30,000. Atlassian bills routing as a Basic event (10 credits) and counts each invocation as one event; this example assumes one invocation per routed request.
- Premium demand: Request Resolver, Alert Intelligence and the help-center Self-service Agent [from your export]
- Demand before Premium: 55,200 · Gap: 27,200 · Expected overage: about $272/month
700 Rovo credits per user looks generous, but it can be outrun by ticket volume rather than headcount. Model routing and customer-facing agents from your request forecast. Our Jira Service Management consulting team often starts here, because these are the AI features ITSM teams switch on first.
Development team on Jira Premium
- Supply: 60 users × 70 = 4,200 credits
- Light: 20 users × 40 = 800
- Regular: 30 users × 420 = 12,600
- Heavy (Basic portion only): 10 users × 420 = 4,200, plus Jira Coding Agent and Think Deeper usage [from your export]
- Demand before Premium: 17,600 · Gap: 13,400 · Expected overage: about $134/month
Add code reviews from December 3. Say 40 developers open 8 pull requests each a month, so 320 reviews. Atlassian hasn't published a Rovo credit rate per review yet. Its Rovo Dev documentation says 2,000 Rovo Dev credits typically cover 20 to 75 reviews, or about 27 to 100 credits per review. If one review costs the same in Rovo credits (our assumption, not Atlassian's), 320 reviews add 8,500 to 32,000 credits, or about $85 to $320/month more.
At 70 Rovo credits per user, two Quick Answers messages a day already use six times the allowance. Premium work and code reviews widen the gap fast. This is where flat-rate estimates mislead most.
Mixed organization on Jira and Confluence Premium, plus Loom
This example has 250 people holding 200 Jira Premium seats and 150 Confluence Premium seats.
- Supply: (200 × 70) + (150 × 70) = 24,500 credits
- Light: 150 × 40 = 6,000
- Regular: 80 × 420 = 33,600
- Heavy (Basic portion only): 20 × 420 = 8,400, plus Premium [from your export]
- Demand before Premium: 48,000 · Gap: 23,500 · Expected overage: about $235/month
New with Loom: if 100 of these people also have Loom Business + AI seats, they add 100 × 70 = 7,000 credits to the pool. Supply rises to 31,500, the gap falls to 16,500 and expected overage to about $165/month. Count every Loom seat in line A.
The real decision here is a cap plus usage packs versus a move to Teamwork Collection, which raises the Premium allowance to 700 per user. You can only make that comparison with a real license quote placed next to twelve months of projected overage.
Mixed organization on Jira and Confluence Premium
This example has 250 people holding 200 Jira Premium seats and 150 Confluence Premium seats.
- Supply: (200 × 70) + (150 × 70) = 24,500 credits
- Light: 150 × 40 = 6,000
- Regular: 80 × 420 = 33,600
- Heavy (Basic portion only): 20 × 420 = 8,400, plus Premium [from your export]
- Demand before Premium: 48,000 · Gap: 23,500 · Expected overage: about $235/month
The real decision here is a cap plus usage packs versus a move to Teamwork Collection, which raises the Premium allowance to 700 per user. You can only make that comparison with a real license quote placed next to twelve months of projected overage.
How Empyra helps you size and control Rovo credits
As an Atlassian Platinum partner, Empyra covers the full picture:
-
Sizing and cap strategy. Our license management team builds your worksheet from your real export, sets spending caps and weighs usage packs against a collection upgrade.
-
Reducing consumption. Our Atlassian consulting services team reworks automation rules and agent configurations that consume credits without adding value.
-
AI rollout and governance. Our Atlassian AI consulting practice helps teams choose between Quick Answers and Think Deeper, set usage ownership, and roll out agents with governance in place.
Frequently Asked Questions
Jira, Confluence and Loom include 25, 70 or 150 credits per user per month on their Standard, Premium and Enterprise tiers (for Loom: Business, Business + AI and Enterprise). Service Collection and Teamwork Collection include 250, 700 or 1,500. All allowances pool across the organization and reset monthly.
Rovo usage limits are the monthly Rovo credit allowances included with each plan: 25, 70 or 150 credits per user for Jira, Confluence and Loom, and 250, 700 or 1,500 for Service Collection and Teamwork Collection. Once your organization uses its pooled allowance, extra usage is billed at $0.01 per credit from December 3, 2026, unless an admin caps it or turns it off.
Only in Quick Answers mode, and only per message. Each message in Rovo Chat is a separate billable event, so a five-message conversation costs 50 credits. Think deeper messages are billed at variable Premium rates.
Rovo credits. A "Use Agent" action inside an automation rule draws on your Rovo credit pool, not your automation step allowance.
Set your spending cap on your peak month plus headroom, and forecast your budget on expected demand. That keeps work running during spikes without overstating typical spend.
Atlassian says beta features don't currently count against your allowance unless stated otherwise, but they may once generally available. Keep them as a separate line in your model.
The right number of Rovo credits per user depends on your measured monthly demand: light, regular and heavy users, plus usage that isn't tied to a seat, such as automation agents, Teamwork Graph calls and, from December 3, code reviews. Build it from your own usage export since August 31, 2026, then add headroom for growth and peak months.
Sometimes. Single-product lookups and write operations through the Atlassian Rovo MCP server or the Teamwork Graph CLI are free. Enriched calls, such as searching across products, use Rovo credits, mostly 1 to 10 per call. For setup and how the MCP server is billed, see our Atlassian Rovo MCP Server guide.
From December 3, 2026, yes. Code Reviewer moves from Rovo Dev credits to Rovo credits as part of your Jira or Teamwork Collection subscription. Atlassian hasn't published a per-review rate yet, so plan a range and watch your usage dashboard. For the rest of Rovo Dev and how it is priced today, see our Rovo Dev page.
Yes, according to Atlassian. Once you pass your allowance, Rovo keeps working and you're billed $0.01 per credit from December 3, 2026, up to any spending cap you set. Admins can lower the cap or turn extra usage off at any time in Atlassian Administration.
Get a Rovo credit number you can take to finance
The flat "allowance ÷ 10" estimate is simple, but it undercounts conversational chat and overcounts free usage. A sizing built on your own export, split into user profiles plus non-seat demand, gives you a number you can defend before December 3, 2026.
The fastest next step: Book a Rovo usage audit with Empyra's Atlassian team.