Rovo Dev Pricing: Rovo Dev Cost per Developer and Credit Overage

Rovo Dev Standard costs $20 per developer per month and includes 2,000 Rovo Dev credits per developer per month. Usage beyond that allowance is billed at $0.01 per credit, and unlike the rest of Rovo, extra usage is enabled by default at a further 2,000 credits per user per month. That puts the default monthly ceiling at roughly $40 per developer, not $20. There is a 30-day free trial, no free tier, and seats can be bought for individual developers rather than a whole site.

Those are Atlassian's published figures, read from the Rovo Dev pricing page and the Rovo licensing FAQ on August 31, 2026. The rest of this article is the arithmetic around them, because the list price is the easy part and the meter is where engineering budgets actually go wrong.

What you get for $20 a developer

Rovo Dev is not the Rovo you already have. The Rovo bundled into Jira and Confluence covers search, chat and agents across your Atlassian content, and it is included free with paid plans on a small credit allowance. Rovo Dev is a separate purchase aimed at professional software engineers, with its own credit currency that is not interchangeable with ordinary Rovo credits.

The capabilities behind the seat are the Rovo Dev CLI, which reads the code in your repository and acts on plans in Jira, AI-powered code review that analyzes pull requests in Bitbucket and GitHub against common errors and the acceptance criteria on the linked Jira issue, and Rovo Dev in the IDE. Atlassian confirms it respects existing permissions, so two engineers can get different answers depending on what they can see.

The number Atlassian does not draw attention to

Divide the seat price by the included credits. Twenty dollars for 2,000 credits is exactly $0.01 per credit, which is precisely the overage rate.

That is unusual, and it is worth pausing on. In almost every metered software product, the bundled allowance is cheaper per unit than the overage, because the bundle is what the vendor wants you to buy and the overage is the penalty for going past it. Rovo Dev has no such gap. Atlassian sells the base seat at the same unit price as the marginal credit, which means there is no volume discount built into the seat at all.

Two practical consequences follow. First, the $20 is best read not as a subscription with credits attached, but as a $20 prepayment on usage. Second, an engineer who uses 4,000 credits costs exactly twice one who uses 2,000, with no bundling advantage. Your cost per developer scales linearly with actual use, which makes forecasting easier than most AI tooling but removes any incentive to over-buy seats for light users.

The overage default that catches teams out

Here is the asymmetry that matters most on a rollout, and it exists between two products from the same vendor with nearly the same name.

For ordinary Rovo, extra usage beyond your credit allowance is disabled by default, and Atlassian states you will never be billed for it unless your organization explicitly opts in. For Rovo Dev, Atlassian's licensing FAQ says the opposite: to avoid service disruptions, Rovo Dev Standard has a default extra usage of 2,000 Rovo Dev credits per user per month auto-enabled.

Read as a budget, that means a Rovo Dev seat is not a $20 line item with a hard stop. It is a $20 line item that can silently become $40 before any cap is reached, without an admin approving anything.

None of this is hidden, and Atlassian's stated reason, avoiding service disruption mid-task, is a defensible product decision. An agent that stops halfway through a refactor because a counter hit zero is worse than a small overage. But the setting deserves a deliberate decision rather than a default, and the place to make it is the per-site limits an admin can set in Atlassian Administration before the seats go out, not the invoice a quarter later.

What to do about it in the first week

Set a custom per-site limit before you distribute seats, watch the Platform usage dashboard for the first full billing cycle to learn what a real engineer on your codebase actually consumes, then set the permanent cap from measured data rather than from the default. Atlassian exposes credit usage per user, which is enough to find out whether your consumption is broad or driven by two or three heavy users.

How many credits does a developer actually use?

Atlassian does not publish a credits-per-action rate card for Rovo Dev the way it does for ordinary Rovo, where an agent request is a flat 10 credits. It says only that credit cost depends on the complexity of the interaction, and gives reviewing a pull request and interacting with the Rovo Dev CLI as examples. Beta features consume credits too, unless stated otherwise.

That is a real gap in disclosure and you should treat it as one. It is the same partial-disclosure pattern we found in UiPath's Platform Unit pricing, where the unit rate is public but the thing that would let you forecast is not. What you can price precisely is the boundary: 2,000 credits included, $0.01 each after that. What you cannot price in advance is how many credits your team's pull requests will cost. Only a trial answers that, which is the strongest argument for using the full 30 days rather than a week of it.

The useful framing for a US engineering budget is a comparison against loaded cost rather than against other tools. At a fully loaded cost well above $100 an hour for a mid-level US engineer, a $40 monthly ceiling per developer is recovered if the tooling saves roughly twenty minutes a month. That is a low bar, and it is the reason the interesting question about Rovo Dev is adoption rather than price. Seats that go unused are the expensive outcome here, not seats that go over.

Is there a free tier for Rovo Dev?

No. Atlassian states plainly that there is no free tier for Rovo Dev. There is a 30-day free trial, and there is one partial exception worth knowing: Atlassian says limited monthly Rovo Dev credits per developer may be gradually offered to selected customers on a Standard, Premium or Enterprise Cloud plan of Jira, starting with sites that already use Rovo. Admins are notified 30 days before their rollout and can opt out.

That is a rollout program, not a plan you can buy or rely on. If you are budgeting, budget for $20 a seat and treat any free credits that appear as a bonus.

Is there an annual plan for Rovo Dev?

Yes. Atlassian offers Rovo Dev on an annual plan aimed at larger organizations that want centralized billing and management with more predictable budgets. The important detail for anyone modeling it: on the annual plan, credits are still allocated and reset monthly per user while billing happens annually. You do not get a year's credits up front to spend as you like, so a quiet quarter does not bank capacity for a busy one. Atlassian does not publish an annual price and routes it through a sales conversation.

Who should buy Rovo Dev, and who should not

Rovo Dev makes obvious sense when your work already runs through Jira and Bitbucket or GitHub, when acceptance criteria genuinely live on the Jira issue, and when code review is a real bottleneck. The product's advantage is context: it reads the repository and the linked issue together, which is exactly what a general-purpose coding assistant cannot do without being told.

It makes less sense in three cases. If your issues are thin and your acceptance criteria live in someone's head, the Jira integration has nothing to work with and you are paying for a plain coding assistant. If your team is small enough that pull request volume is low, a seat may go mostly unused, and unused seats are the worst value in this model because the $20 buys credits rather than access. And if a large share of your delivery runs through contractors who rotate on and off the project, per-developer seats are the wrong shape entirely, since you would be provisioning and deprovisioning licenses against people whose engagement ends before the annual plan does.

One structural advantage does deserve credit. Because Atlassian does not require a site-wide upgrade, you can license six engineers rather than sixty. Very few enterprise AI products let you buy that narrowly, and it makes an honest pilot cheap: six seats for one month is $120, plus whatever overage the default allows.

How Rovo Dev fits with the rest of Rovo

Keep the two budgets separate, because the credit currencies are separate. Ordinary Rovo comes free with your Jira, Confluence and Jira Service Management subscriptions on an allowance of 25 credits per seat per month on Standard, 70 on Premium and 150 on Enterprise, where an agent request costs 10 credits. That allowance is small enough that most teams hit its limits well before they hit a bill, and we work through the full model in our breakdown of Atlassian Rovo pricing, credits and agents.

Rovo Dev sits alongside that with 2,000 credits of its own per developer and a real per-seat price. A team can run both: ordinary Rovo for search and summarization across Atlassian content, Rovo Dev for the engineers who live in the CLI and in code review. If the constraint you keep hitting is on the ordinary Rovo side, upgrading Rovo Dev will not help, and the fix is usually the credit allowance rather than the developer product. For work that sits outside the Atlassian graph altogether, a flat-rate agent connected to Jira through the API avoids the credit question for that workload entirely.

The short version

Rovo Dev is priced honestly and simply: $20 per developer per month, 2,000 credits, $0.01 per credit after that, and no pretense that the bundle is discounted, because it is not. The two things to check before you roll it out are the extra-usage default, which is on and doubles your worst case, and your own consumption rate, which Atlassian does not publish and only a trial will tell you. Do both in the 30-day trial and the seat price stops being a guess.