Tracked changes
2
Tool change history
Atlassian Rovo changes and buying impact
Atlassian-centric buyers should model Jira, Confluence, JSM, and Teamwork Collection allowances separately instead of treating Rovo as one flat quota. The near-term risk of core Rovo overage billing is lower than a simple quota warning implies, but engineering teams still need a separate Rovo Dev budget and overage control.
Latest detected
May 7, 2026
High-priority
2
Affected comparisons
1
Quick answer
Atlassian-centric buyers should model Jira, Confluence, JSM, and Teamwork Collection allowances separately instead of treating Rovo as one flat quota. The near-term risk of core Rovo overage billing is lower than a simple quota warning implies, but engineering teams still need a separate Rovo Dev budget and overage control.
Buyer next step
Check whether pricing assumptions and affected comparisons still hold, then save the tool to a watchlist.
Evidence status
Each change includes the detected date, severity, buyer impact, and affected comparisons.
Last verified: May 7, 2026Visit official siteAtlassian Rovo pricing and licensingRovo usage allowanceMethodology
Watchlist
Track changes for this shortlist
Save the stack, monitor buying-impact changes, and turn the result into a decision memo.
Check change impact
See how this change affects your comparisons and costs
Open the affected comparison pages or check team-size costs in the calculator.
Timeline
Changes that can affect the buying call
Pricing, feature, limit, and policy changes are interpreted for rollout, renewal, and shortlist decisions.
May 7, 2026mediumlimit changeUpdate
Atlassian clarified Rovo allowance pools and the separate Rovo Dev overage model
Atlassian's current Rovo usage and billing docs separate core Rovo credits from Rovo Dev credits, show higher Teamwork Collection allowances than the Jira, Confluence, and JSM rows, state that core Rovo over-allowance usage is not currently billed, and keep Rovo Dev Standard at $20 per developer per month with $0.01 per-credit extra usage.
Buyer impact: Atlassian-centric buyers should model Jira, Confluence, JSM, and Teamwork Collection allowances separately instead of treating Rovo as one flat quota. The near-term risk of core Rovo overage billing is lower than a simple quota warning implies, but engineering teams still need a separate Rovo Dev budget and overage control.
Apr 9, 2025mediumplan changeUpdate
Atlassian began rolling Rovo into paid Jira, Confluence, and JSM Cloud subscriptions
Atlassian support states that, starting April 9, 2025, Rovo is rolling out at no additional upfront cost to paid Jira, Confluence, and Jira Service Management Cloud plans, with included quotas and future usage-based charging to watch.
Buyer impact: For Atlassian-centric teams, Rovo shifted from a separate AI experiment to a bundle-native option worth evaluating before buying another standalone knowledge assistant.
Next reads
Comparisons connected to this tool
Use these routes when this tool is already on the shortlist and you need a side-by-side call.
Pricing
Atlassian Rovo pricing guide
Rovo Search, Chat, and Agents start at $0 incremental cost inside eligible paid Atlassian Cloud plans. Jira, Confluence, and Service Collection / JSM include 25, 70, and 150 Rovo credits per user per month on Standard, Premium, and Enterprise; Teamwork Collection includes 250, 700, and 1,500. Rovo Dev adds $20 per developer per month for 2,000 Rovo Dev credits with $0.01 per credit overage.
Compare
Glean vs Atlassian Rovo
Glean's MCP and open-agent push make it more compelling as a horizontal enterprise context layer. Atlassian's current Rovo model is now clearer: core Rovo rides paid Jira, Confluence, Service Collection / JSM, and Teamwork Collection plans with pooled credit and indexed-object allowances, core Rovo over-allowance usage is not currently billed, and Rovo Dev remains a separate $20/developer coding seat with its own paid overage. The split is openness and governance versus bundle fit, allowance math, and Atlassian-native rollout.
Best
Best AI meeting assistants by suite and follow-through
Use this list to choose an AI meeting assistant around the system your team already uses. It weighs suite alignment, capture quality, and whether action items stay in the same workflow after the call.
Best
Best AI tools for team knowledge workflows
Use this list when the team knowledge problem is practical: where documents live, how easily people retrieve context, and whether that knowledge turns into day-to-day follow-through. The ranking favors tools that make that loop easier, not just general assistants.