Key findings
- At 300 users billed monthly, Confluence lists Standard at US$5.78 and Premium at US$11.16 per user per month. Free covers up to 10 users, and Enterprise is quoted from 801 users.
- Each paid seat adds 25 (Standard), 70 (Premium), or 150 (Enterprise) Rovo credits a month to one organization pool, and Jira seats add the same amounts.
- Quick answers and basic agents cost 10 credits per message or run. Think deeper, Deep Research, agents with model selection, and Confluence slides cost a variable amount.
- Extra usage is on by default and bills at US$0.01 per credit, up to any spending cap an admin sets. Prepaid packs carry volume discounts.
- Admins who measured their spend report deep reasoning and agents running through credits fastest. One test org measured Think deeper messages at 65 and 86 credits each, and an automation rule that calls a Rovo agent spends credits on every run.
From December 3, 2026, Rovo use beyond the seat allowance bills as extra usage, and the allowance is small. It covers about 2.5 Quick answers per Standard user a month, or 7 per Premium user. Search and summaries stay free, while Chat, deeper reasoning, agents, and outside tools that pull Teamwork Graph context spend credits.
What a seat buys
At the listed 300-user monthly price, Standard costs US$1,734 a month and adds 7,500 Rovo credits. Premium costs US$3,348 and adds 21,000. Credits pool across the organization, so the same people on Premium seats in both Confluence and Jira bring 42,000 credits a month.
At 10 credits per Quick answers message, Standard's allowance buys 750 messages a month, about 2.5 per user. Premium's buys 2,100, about 7 per user. An Atlassian Community member who checked the same math on Premium got the same answer, about seven chats a month.
What stays free
Rovo Search inside Atlassian apps, definitions, and page summaries cost nothing, and indexing connector content uses no credits. The everyday search improvement comes inside the seat price.
Single-product lookups and writes through the Atlassian MCP server, such as reading one Confluence page or updating one Jira work item, are also free.
Where the bill grows
Credit use climbs when Chat becomes the default way to ask questions, and again with deeper reasoning modes and agents with model selection. Outside AI tools spend credits when they pull enriched Teamwork Graph context. Most of those calls cost 1 to 10 credits, and Atlassian puts a typical prompt at 10 to 25.
- Example: 300 Standard users each sending ten Quick answers messages a month use 30,000 credits. The 22,500 past the allowance cost US$225 that month at list price.
- The same use on Premium leaves 9,000 credits past the allowance, or US$90.
- Atlassian says Teamwork Collection carries up to ten times the allowance of a standalone app on the same plan.
What admins report
Admins who measured their spend found credits going faster than the per-seat math suggests. On his own test org, Marketplace app developer Mihai Perdum measured a Quick answers message at exactly 10 credits and Think deeper messages at 65 and 86. One Think deeper message spends more than three months of a Jira Standard seat's allowance. Rovo asks for no confirmation before a costly mode. An admin whose Rovo use was growing quickly warned that the organization would exhaust its credits before the billing cycle ended.
Agents and outside tools spend credits nobody typed. Perdum measured a Rovo agent called from a Jira automation rule at 10 credits per call, 13 when switched to Claude Sonnet 4.6. It measured 30 for one rule run that branched over three sub-tasks. An admin of a 123-user Jira Cloud Standard site found that Claude's calls through the Rovo MCP server cost 7 to 10 credits each when they returned linked data. More than 2,000 credits sat under an unlabeled Jira Administration category spread across dozens of users. Another admin found that Atlassian Assist, the Slack and Teams chat integration the team used with Virtual Service Agent, had spent 100 credits in what looked like a single event.
Some teams route around Rovo. One Hacker News team wrote its own MCP server for Jira and Confluence because Atlassian's route required Rovo and extra payment. A PeerSpot reviewer lists extra purchases for projects and staff as a cost factor.
Methodology
GILD analysis of Atlassian's Confluence pricing page, Rovo licensing FAQ, and Rovo usage limits documentation, checked October 12, 2026, with worked examples at the listed 300-user monthly price. 5 of the 101 public accounts in GILD's Confluence review, published from January 26, 2025 to October 20, 2026, mention seat prices or Rovo credits. GILD added measured spend reports from Atlassian Community threads and DEV Community posts, read October 25, 2026. All prices are list prices, and an Atlassian quote for your seat count sets the real figure.
Products in this piece
Sources
- Official documentation
- 6
- Public source
- 7
- Confluence pricing
- Atlassian: Rovo plans and trial
- Atlassian Support: How Rovo credits work
- Atlassian Support: Compare Rovo Chat reasoning modes
- Atlassian Support: Get started with the Atlassian MCP server
- Atlassian blog: Atlassian's usage-based pricing (Sep 1, 2026)
- Hacker News comment on writing an MCP server to avoid paying for Rovo (Sep 4, 2026)
- DEV Community: Rovo Credits per User: Cost and Usage per Action, Measured (Mihai Perdum, Oct 15, 2026)
- DEV Community: Rovo Agent Pricing in Jira Automation: Cost per Agent Call (Mihai Perdum, Oct 24, 2026)
- Atlassian Community: New proposed pricing changes, trying to understand what actually counts as Rovo credits (Mahanth Prudhvi P, Sep 2, 2026)
- Atlassian Community: Why Is Rovo Usage Showing Jira Administration? (Dr Valeri Colon, Mar 23, 2026)
- Atlassian Community: Atlassian assist rovo credits usage (CIS JSM01, Aug 26, 2026)
- Atlassian Community: 70 credits, 10 per chat? So, only 7 chats per month on a paid plan? (Andrew Fleig, Jun 9, 2026)