Skip to main content

Buyer guide

Rovo Credits & Spend Controls Checklist

Separate free Rovo features from those that spend pooled credits. Set extra-usage limits before billing starts December 3, 2026.

Reading time
3 min read
Sources
10 cited
In this piece
Confluence+8 Mixed

Cap Rovo's extra usage before December 3, 2026. From that date, use beyond the pooled allowance bills at US$10 per 1,000 credits unless an admin caps it. Each paid Confluence seat adds 25, 70, or 150 credits a month to one shared pool, search and summaries are free, and deeper modes and agents spend credits fastest.

When you need this

  • Finance asks what Rovo adds to the Atlassian bill after December 3, 2026.
  • Teams use Think deeper, Deep Research, Confluence slides, or agents with model selection every day.
  • Claude, ChatGPT, or other tools reach Confluence through the Atlassian MCP server or the Teamwork Graph CLI.

Evaluation criteria

  1. What the pool holds

    How many credits does the organization get each month?

    Look forCount 25 monthly credits per Standard seat, 70 per Premium seat, or 150 per Enterprise seat in Jira and Confluence. Teamwork Collection and Service Collection seats add 250, 700, or 1,500. Credits pool across apps and reset monthly without rollover.

  2. What is free

    Which everyday features spend nothing?

    Look forLeave free features out of the credit budget. Rovo Search in Atlassian apps, definitions, and summaries use no credits. Neither do connector indexing or single-product lookups and writes through the MCP server and CLI.

  3. What spends credits

    Which features draw on the pool, and how much?

    Look forBudget 10 credits per Quick answers message or basic agent run. Think deeper, Deep Research, model-selected agents, Confluence slides, and Create with Rovo use variable credits. On one test org, Think deeper messages cost 65 and 86 credits. Most enriched Teamwork Graph calls from outside tools cost 1 to 10 credits each, and Atlassian puts a typical prompt at 10 to 25.

  4. Limits and alerts

    What stops a month of heavy use from becoming a surprise invoice?

    Look forSet a spending cap, or turn extra usage off, since it defaults to on. With extra usage off, new requests that spend credits pause until the monthly reset, and work in progress finishes. Admins get alerts at 80% and 100% of the allowance.

  5. Visibility

    Can you see which apps, users, and agents drive usage?

    Look forReview credits by app and user in Atlassian Administration under Insights, Platform usage, Rovo credits. Export up to 3 months or 1 million events as CSV. One admin of a 123-user Jira Standard site found more than 2,000 credits listed under an unlabeled Jira Administration category, spread across dozens of users. Ask Atlassian what drives any category you cannot trace.

  6. Cheaper ways to more credits

    Would a different purchase cost less than extra usage?

    Look forCompare prepaid credit packs and their volume discounts with a higher plan or Teamwork Collection. Atlassian says Teamwork Collection includes up to ten times a standalone app's allowance on the same plan.

Questions to ask vendors

  1. How many credits did each app and team use in the last full month on the Platform usage dashboard?
  2. Which agents run on schedules or from automation, and how many credits does each run use?
  3. What volume discount applies to a prepaid credit pack at our size?
  4. Does Teamwork Collection cost less than our current seats plus expected extra usage?

Red flags

  • Budgeting Rovo at zero because the allowance looks large on a Standard plan.
  • No spending cap set when extra usage billing starts on December 3, 2026.
  • Outside AI tools making enriched Teamwork Graph calls with nobody tracking them.
  • Agents with model selection published company-wide before anyone has measured a run.
  • Automation rules that call a Rovo agent on every new work item, at 10 credits a call, whether or not anyone reads the result.

Products in this piece

Sources

Official documentation
6
Public source
4
  1. Atlassian Support: How Rovo credits workOfficial documentationsupport.atlassian.com
  2. Atlassian: Rovo plans and trialOfficial documentationatlassian.com
  3. Confluence pricingOfficial documentationatlassian.com
  4. Atlassian Support: Compare Rovo Chat reasoning modesOfficial documentationsupport.atlassian.com
  5. Atlassian Support: Get started with the Atlassian MCP serverOfficial documentationsupport.atlassian.com
  6. Atlassian blog: Atlassian's usage-based pricing (Sep 1, 2026)Official documentationatlassian.com
  7. Hacker News comment on writing an MCP server to avoid paying for Rovo (Sep 4, 2026)Public sourcenews.ycombinator.com
  8. DEV Community: Rovo Credits per User: Cost and Usage per Action, Measured (Mihai Perdum, Oct 15, 2026)Public sourcedev.to
  9. DEV Community: Rovo Agent Pricing in Jira Automation: Cost per Agent Call (Mihai Perdum, Oct 24, 2026)Public sourcedev.to
  10. Atlassian Community: New proposed pricing changes, trying to understand what actually counts as Rovo credits (Mahanth Prudhvi P, Sep 2, 2026)Public sourcecommunity.atlassian.com

Keep reading

  1. Buyer guideConfluence With Rovo Rollout PlaybookSettle Confluence's data settings and clean its content before Rovo answers across spaces, then set connector scope, agent rules, and a cap on credit spend.
  2. Buyer guideConfluence & Rovo Data Handling ChecklistReview contribution defaults and LLM retention before security signs off. Check Atlassian-hosted models and residency, then connector scope and agent risks.
  3. Buyer guideConfluence Content & Search Readiness ChecklistClean Confluence spaces and check permissions so Rovo Search and Chat answer from current pages. Remove duplicates and drafts from the answers teams rely on.
Read the research