Sep 5, 2026·medium
Rovo Dev Free is a site-level eligibility path, not a universal free tier.
Current Atlassian billing and usage documentation describes Rovo Dev Free as 350 credits per user per month per activated paid-Jira site, with no paid extra usage and a pause at the limit. The public Rovo Dev pricing FAQ says free availability is limited and may be offered gradually to selected qualifying sites.
Use the 350-credit path only after confirming site activation and eligibility. It can lower the cost of a tightly scoped pilot, but it is not a safe baseline for a company-wide Rovo Dev budget; otherwise model Standard at $20 per developer per month plus approved extra usage.
Open tool change historySep 5, 2026·medium
Rovo Dev's trial cannot validate CLI or IDE use, and Jira work is moving to Jira Coding Agent.
Atlassian's current trial documentation says the 30-day Rovo Dev Standard trial excludes Rovo Dev CLI and Rovo Dev in the IDE, while other generally available features including Bitbucket and GitHub code reviews remain available. It also says Rovo Dev in Jira is transitioning to Jira Coding Agent starting June 22, 2026; CLI, IDE, and AI code review remain Rovo Dev Standard capabilities.
Use the trial to test code-review workflow, credit allocation, and billing setup, not to assume terminal or IDE fit. Budget a paid Standard validation if those surfaces are decisive, and evaluate Jira Coding Agent as a separate product path.
Open tool change historyJul 3, 2026·medium
Atlassian documents Rovo Dev default extra-usage headroom and admin limits
Atlassian's current Rovo Dev pricing and billing docs keep Rovo Dev Standard at $20 per developer per month with 2,000 included credits, but clarify that extra usage is $0.01 per credit with a default monthly extra-usage limit of 2,000 Rovo Dev credits per user and organization-admin controls for custom limits.
Engineering teams should model Rovo Dev as more than a flat $20 developer seat. The default extra-usage headroom can protect continuity but also creates a paid overage path unless admins review and cap site-level limits before broad rollout.
Open tool change historyMay 7, 2026·medium
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.
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.
Open tool change historyApr 9, 2025·medium
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.
For Atlassian-centric teams, Rovo shifted from a separate AI experiment to a bundle-native option worth evaluating before buying another standalone knowledge assistant.
Open tool change history