Pricing guide
Rovo Dev Standard costs $20 per developer monthly for 2,000 credits. See the default $20 overage cap, eligible 350-credit Free path, and core Rovo allowances.
Rovo Dev Standard costs $20 per developer per month for 2,000 credits that reset monthly. Extra usage is $0.01 per credit; Atlassian's published default extra-usage limit is another 2,000 credits, so the ordinary pre-tax planning range is $20–$40 per developer per month unless an admin changes that cap. A separate, eligibility-dependent Rovo Dev Free path gives an activated paid-Jira site 350 credits per user per month and has no paid extra usage. Do not confuse either Rovo Dev offer with core Rovo: Rovo Search, Chat, and Agents start at $0 incremental cost inside eligible paid Atlassian Cloud plans, with their own pooled allowances.
AgentHub review: Sep 5, 2026
Use the included core Rovo allowance as a capability decision, not a zero-cost deployment decision. Rovo Dev Free can lower a qualifying site's initial experiment to 350 credits per user per month, but verify activation and eligibility before budgeting it. Rovo Dev Standard's included credits reset monthly. Its published default extra-usage cap turns a $20 seat into a $20–$40 monthly planning range per developer before tax, and Atlassian estimates that the 2,000 included credits typically cover 20–75 reviews or 5–50 CLI tasks. Set a team-specific cap from a small pilot rather than the seat price alone. The 30-day trial cannot validate CLI or IDE use, so test its code-review workflow there and budget a separate paid Standard validation for terminal or IDE fit. Set core Rovo spending controls before December 3, 2026, and model Rovo Dev Standard separately before a broad engineering rollout.
Review methods: Official sources · Cost calculations · Change history
Sources checked: Sep 5, 2026 · 5 official sources
Atlassian Rovo pricing is easiest to justify when the team already pays for Jira, Confluence, Service Collection, or Teamwork Collection, because Rovo Search, Chat, and Agents ship inside eligible paid Cloud plans with pooled Rovo credit allowances. For activated eligible Jira sites, the current support documentation also describes Rovo Dev Free: 350 credits per user per month, per site, with no paid extra usage. Its public pricing FAQ says that availability is limited, so treat that path as an entitlement to confirm, not a universal free plan. Extra-usage billing for core Rovo is scheduled to begin on December 3, 2026. Rovo Dev Standard is a separate $20-per-developer engineering line: its 2,000 included credits reset monthly, and the published default 2,000-credit extra-usage cap makes its ordinary planned range $20–$40 per user per month before tax unless an admin changes that cap.
Atlassian-centric teams that want bundled AI inside Jira and Confluence instead of another standalone workspace AI contract, and engineering orgs that would also buy Rovo Dev for terminal AI and code review on top of the same Teamwork Graph.
Your buying case depends on broad cross-stack enterprise search beyond Atlassian, a simple unlimited per-seat AI model without credit quotas, or a standalone coding cockpit outside the Atlassian environment.
Check which features are available in a trial or paid plan.
The 30-day Rovo Dev Standard trial can validate the review workflow, repository setup, pull-request author credit allocation, and the review frequency that controls credit use. Use a representative pull request rather than only a demo repository.
CLI is not available during the Standard trial. If terminal work is a buying requirement, fund a tightly scoped paid Standard validation and set the site-level credit cap before expanding seats.
Rovo Dev in the IDE is also excluded from the Standard trial. Treat it as a separate paid validation, because a successful code-review trial does not prove editor workflow fit.
Atlassian says Rovo Dev in Jira is transitioning to Jira Coding Agent, which is available with paid Jira editions. Evaluate that Jira path separately from a Rovo Dev Standard CLI or IDE rollout.
| Product or plan | Availability | What to check |
|---|---|---|
| Bitbucket and GitHub code reviews | Available | The 30-day Rovo Dev Standard trial can validate the review workflow, repository setup, pull-request author credit allocation, and the review frequency that controls credit use. Use a representative pull request rather than only a demo repository. |
| Rovo Dev CLI in the terminal | Paid plan required | CLI is not available during the Standard trial. If terminal work is a buying requirement, fund a tightly scoped paid Standard validation and set the site-level credit cap before expanding seats. |
| Rovo Dev in the IDE | Paid plan required | Rovo Dev in the IDE is also excluded from the Standard trial. Treat it as a separate paid validation, because a successful code-review trial does not prove editor workflow fit. |
| Coding work inside Jira | Separate product | Atlassian says Rovo Dev in Jira is transitioning to Jira Coding Agent, which is available with paid Jira editions. Evaluate that Jira path separately from a Rovo Dev Standard CLI or IDE rollout. |
Excludes taxes, negotiated discounts, and unstated overages. Check the assumptions and sources for each example.
Included in an existing paid plan
Rovo Dev Free has been activated for a qualifying paid-Jira site. It includes 350 Rovo Dev credits per user per month, per site, stops at the limit, and has no paid extra usage. The public pricing FAQ calls availability limited, so this excludes the underlying Jira subscription and is not a default entitlement to assume.
$100–$200/month
Five developers on Rovo Dev Standard. The $100 lower bound is five $20 seats with only included credits. The $200 upper bound adds Atlassian's published default 2,000-credit extra-usage cap per user at $0.01 per credit; admins can change that cap.
$500–$1,000/month
Twenty-five developers on Rovo Dev Standard. The $500 lower bound is 25 $20 seats with only included credits. The $1,000 upper bound adds the published default 2,000-credit extra-usage cap per user at $0.01 per credit; customize the cap before broad rollout.
Change the developer count and monthly extra-credit cap to calculate a monthly and annual planning ceiling from the published seat price and credit rate.
Excludes tax, the underlying Jira subscription, negotiated discounts, and admin-customized caps. Do not apply this model to the eligibility-dependent Rovo Dev Free path.
Plan details
Confirm features and limits against the supplier's current source before buying.
Free plan available · Paid from $20/mo
$0 / month
$0 per seat / month on annual billing
$0 / month
$0 per seat / month on annual billing
$0 / month
$0 per seat / month on annual billing
$20 / month
No annual price published
$0 / month
No annual price published
$0 / month
No annual price published
Pricing questions
Next decision
Pair the price model with a fit review, alternatives, and the change record.
