Rovo Dev pricing today is $20 per developer a month for Rovo Dev Standard, with 2,000 Rovo Dev credits and $0.01 for each extra credit, and Atlassian has said Rovo Dev will reach end of life as a standalone product. On 27 October I wanted to count how many of those credits a normal coding task eats. So we logged the Rovo Dev CLI into our test org and gave it a one-line job. It answered "Rovo Dev CLI is not enabled for this organization." The site's own Rovo Dev page offered a free 30-day trial of Rovo Dev Standard, and the button behind it said "Rovo Dev sign-up is no longer available." So at the end of October 2026 you can still pay for Rovo Dev, and you can't start it.
The reason is on Atlassian's licensing page: "Rovo Dev as a standalone product will reach end of life." There's no date yet, only "at least 60 days' notice". If you run engineering or pay the Atlassian bill, you're holding seats at $20 per developer a month for a product whose replacement has no price. Ten developers cost $200 a month, 50 cost $1,000 and 200 cost $4,000.
The $20 seat was always a prepaid bucket of 2,000 credits at exactly one cent each, which is the same list price Atlassian charges for an extra Rovo credit. If that one-to-one holds when the CLI moves into Rovo credits, the developers who barely use Rovo Dev get much cheaper and the heavy users cost about what they cost today. If it doesn't hold, nobody can tell you the after-price yet, including us.
Three separate events are coming, and I'll keep their names straight: the Code Reviewer switch on 3 December 2026, the CLI migration to the Rovo CLI (no date), and the final end of life (no date). If you only want the checklist for your seats, it's the last section.
Six things we found: $20 seats, no end date, no exchange rate
- Standard costs $20 per developer a month. The pricing page says "$20 per developer / month" with "2,000 Rovo Dev credits per developer" and "$0.01 per credit" after that (we read it on 27 October 2026). Rovo Dev Free gives 350 credits per user, per month, per site with no extra usage.
- The end of life has no date. The Rovo Dev FAQ lists the Rovo CLI migration, the IDE retirement and the final end-of-life date under "Upcoming (Dates TBA)". The only firm date is 3 December 2026, for Code Reviewer.
- Two Atlassian pages disagree. The pricing page carries an end-of-life banner. The support page "How billing works for Rovo Dev" still sells Standard and mentions no transition at all (we searched it for "end of life", "transition" and "retire" and got zero hits).
- There's no exchange rate. Atlassian says Rovo Dev credits and Rovo credits are "different and separate" meters and has published no rate between them, and no price for the Rovo CLI.
- At list price the seat and the credit cost the same. $20 for 2,000 credits is $0.01 a credit, and an extra Rovo credit is "$0.01 per credit over your allowance". At one-to-one, 200 developers who each use 350 credits would cost about $650 a month instead of $4,000.
-
New sign-ups are closed in practice. On our org the trial button ended at "Rovo Dev sign-up is no longer available", Add app doesn't list Rovo Dev, and the CLI's credit check came back
FEATURE_DISABLED_ORG_LEVEL.
Rovo Dev pricing today: Free, Standard at $20 and $0.01 per extra credit
These are the numbers on Atlassian's pages on 27 October 2026. I'm quoting them because two of the pages say slightly different things.
| Rovo Dev Free | Rovo Dev Standard | |
|---|---|---|
| Price | "Free with Jira paid plans" | $20 per developer per month |
| Credits | 350 per user, per month, per Jira site | 2,000 per developer per month |
| Extra usage | "Not available" | $0.01 per credit |
| When credits run out | stops "until your usage resets in the next billing cycle" | keeps working if paid extra usage is enabled, up to any limit an org admin set |
| CLI and IDE | the usage doc says 350 credits cover "1 to 10 tasks in Rovo Dev CLI" | yes, on a paid subscription (not during the trial) |
The billing page even has a worked example. 100 users on Standard, with 50 of them using 500 extra credits each, comes to $2,000 plus $250, so $2,250 for the month.
Atlassian's pricing page shows no Free tier at all, while the billing doc lists one, and I think that's why some people never realise Free exists. The billing doc also says 2,000 credits "per user", while the usage doc and four other support pages say the 2,000 sit "at the organization level". The billing doc's own example treats them as per user, so that's how I've done the sums.
How far do 2,000 credits go? Atlassian's own estimate is "20 to 75 code reviews, or 5 to 50 tasks in Rovo Dev CLI. More complex tasks require more credits." That works out to roughly 40 to 400 credits for one CLI task. We wanted our own number for this and couldn't get one.
Can you move light users to Free today? Atlassian's rollout page says that "Starting in mid-October, Rovo Dev is gradually rolling out to sites with Jira Standard or Premium plans at no extra cost", with the 350-credit allowance. None of the pages we read describes moving a paying Standard user back to Free, and our org has no Rovo Dev to test it on. So ask Atlassian Support before you count on it.
Rovo Dev end of life: what Atlassian has announced and what it hasn't dated
Everything firm sits on one page, the Rovo Dev FAQ. I read it in full on 27 October.
The product first. "Rovo Dev as a standalone product will reach end of life," with "at least 60 days' notice", and "No immediate action is required."
Code Reviewer moves into paid Jira: "Code Reviewer will transition to Rovo Credits on December 3, 2026." Before that date, once it shows up in your Jira, "you can use it without Rovo Credits metering during the transition window". Atlassian adds that 3 December "is not the Rovo Dev end-of-life date."
For the CLI, "Rovo Dev CLI is evolving into the unified Atlassian Rovo CLI experience, which will operate under Atlassian's Usage-Based Pricing model after the transition." Meanwhile: "Continue using Rovo Dev CLI until migration instructions are shared." Bitbucket Pipelines keeps Rovo Dev CLI until the Rovo CLI exists, and ordinary builds are "completely unaffected". The IDE goes: "Standalone Rovo Dev IDE capabilities will be retired." AtlasCode, the VS Code extension for Jira and Bitbucket, stays.
And your subscription? "Atlassian will not automatically cancel your Rovo Dev subscription." Code-Reviewer-only customers get a notice when it's live in Jira so they can cancel. CLI and IDE users are asked to "keep your Rovo Dev subscription active until the transition paths and instructions for those capabilities are released." Annual customers are told "Your investment and prepaid term are fully protected" and that Atlassian is "working to ensure a fair commercial transition". Anyone with an annual or recently renewed subscription is asked to contact Atlassian Support. I don't know whether that means a refund, a credit or running to the end of the term, and the page doesn't say.
The page gives no date for the CLI migration, the IDE retirement or the final end of life. They're all "Dates TBA", and I didn't find a Rovo CLI price on any Atlassian page we read. The one place "Rovo CLI" sits next to money is the Rovo licensing page, where it's listed among "Premium AI interactions" with "Variable pricing per billable event".
A few of the support docs haven't caught up yet. The pricing page, the product page and the FAQ all carry the end-of-life message, while the billing page, the trial page and the "Add Rovo Dev Standard" page still describe buying and trialling Standard as if nothing changed. One trial page still says, from an earlier change, that after 22 June "Rovo Dev CLI, IDE and AI code review, will continue to be available through a Rovo Dev Standard subscription." Both versions are live today. When pages conflict, I go by the one that is newest and most specific about the change, which is the FAQ.
Rovo Dev CLI becomes the Rovo CLI: is Rovo CLI free, and what will it cost?
Not as a free product of its own, and there's no price yet. Atlassian says the Rovo CLI will "operate under Atlassian's Usage-Based Pricing model", which means it draws from your org's Rovo credits once billing applies to it. Your org's Rovo credits come from your seats. Jira or Confluence Standard gives 25 per user a month, Premium 70 and Enterprise 150, and Teamwork Collection or Service Collection gives 250, 700 and 1,500. They all go into one shared pool, and extra credits are $0.01 each (that's $10 per 1,000).
So is the Rovo CLI free? A small slice of it is probably covered by the credits you already have. How small depends on a number Atlassian hasn't published: how many Rovo credits one CLI task costs. Atlassian already lists the Rovo CLI as a "premium" interaction with variable pricing, so I wouldn't expect it to sit at the cheap end of the scale.
While we tested, the CLI binary that acli downloaded on 27 October reports itself as "Rovo Dev CLI: 202610.27.1", and its own doctor command already describes itself as "Run Rovo CLI diagnostics". The rename has started inside the tool before Atlassian has published a date or a migration guide, so please don't plan on it yet.
"Rovo Dev CLI is not enabled for this organization" and the other messages we hit
Here's our first CLI task on our test org (acli 1.3.39, 27 October 2026), with our cloud ID replaced by a placeholder:
$ BILLING_CLOUD_ID=<wolfaenpak cloud id> acli rovodev legacy "Reply with the single word OK."
Working in /private/tmp/lz-rovo-dev-pricing/sandbox
─── Rovo Dev CLI is not enabled for this organization. ─────────────────────────
To use Rovo Dev CLI on this organization, enable it in Rovo Dev settings. Rovo
Dev settings
────────────────────────────────────────────────────────────────────────────────
────────────────────────────────────────────────────────────────────────────────
Run without an interactive terminal, so the billing site could not be
selected. Pin the billing cloud ID for headless runs by setting the
BILLING_CLOUD_ID environment variable before invoking the CLI, e.g.
BILLING_CLOUD_ID=<cloud-id>.
You can find a site's cloud ID at
https://<your-site>.atlassian.net/_edge/tenant_info.
────────────────────────────────────────────────────────────────────────────────
────────────────────────────────────────────────────────────────────────────────
To resume your session, restart Rovo Dev CLI with the --restore flag.
────────────────────────────────────────────────────────────────────────────────
✗ Error: failed to execute the command
exit=1
Login had succeeded. The refusal comes from the credit check, which the CLI's log shows returning FEATURE_DISABLED_ORG_LEVEL.
We hit five messages that stopped us on 27 October, in the order a new user meets them. Before login, acli rovodev says "to get started, authenticate your Atlassian account: 1. Create a Rovo Dev scoped API token" (our classic API token logged in fine anyway). A headless run then stops at "Billing site not set", and setting BILLING_CLOUD_ID gets the run past it to the credit check (the billing-site notice still prints). Next comes "Rovo Dev CLI is not enabled for this organization." The CLI links you to "Rovo Dev settings", and on our org that link redirected to the Rovo access page, which has no Rovo Dev control on it. On the site itself, /rovodev says "Rovo Dev is not activated on this site", and its trial button leads to "Rovo Dev sign-up is no longer available".
Rovo Dev credits vs Rovo credits: two meters, no published exchange rate
Atlassian is clear that these are two meters. The usage doc says "Rovo Dev credits are different and separate from Rovo credits", with Rovo Dev credits for the CLI and code reviews and Rovo credits for Rovo Chat, agents and Deep Research. The usage-based pricing FAQ lists Rovo credits, Automation steps, Assets objects, Bitbucket meters and AI agent resolutions, and doesn't mention Rovo Dev at all.
What nobody has published is a rate between the two. Our Code Reviewer article ran into the same gap last week. Both meters charge $0.01 for an extra credit. Equal prices for an extra credit still don't tell you that one Rovo credit buys as much as one Rovo Dev credit. A CLI task could cost 100 Rovo Dev credits today and 150 Rovo credits after the migration, and the price tag on both credits would still read one cent.
My after-costs all assume a one-to-one rate: one Rovo credit buys what one Rovo Dev credit buys today. Treat it as the optimistic case. If the real rate turns out different, the after-costs change with it, roughly in proportion.
Rovo Dev cost for a 10, 50 or 200 developer team, now and after the move
Today's cost is just seats. 10 developers on Standard cost $200 a month, 50 cost $1,000 and 200 cost $4,000, whether each developer uses 50 credits or all 2,000.
After the CLI migration there's no seat. Each developer's own Jira seat adds credits to the shared pool, and anything above the pool is billed at $0.01. The table uses the one-to-one rate. It counts only the 25 credits a month that each developer's own Jira Standard seat adds. I've priced three levels of use.
| Team | Today, Standard | After, 350 credits each | After, 1,000 each | After, 2,000 each |
|---|---|---|---|---|
| 10 developers | $200 | $32.50 | $97.50 | $197.50 |
| 50 developers | $1,000 | $162.50 | $487.50 | $987.50 |
| 200 developers | $4,000 | $650 | $1,950 | $3,950 |
I picked 350 because it's Atlassian's Free allowance, which Atlassian says covers "1 to 10 tasks in Rovo Dev CLI". 2,000 is a full Standard allowance. On Jira Premium (70 a seat) the full-use row drops only a little, to $193, $965 and $3,860. Teamwork Collection is where it moves: Premium (700 a seat) gives $130, $650 and $2,600, and Enterprise (1,500) gives $50, $250 and $1,000.
Keep in mind the pool is shared. Those 25 credits per seat also pay for Rovo Chat and agents, and from 3 December for Code Reviewer, across the whole company. Every seat in the org feeds it, developers or not. To use your own numbers, open Atlassian Administration, then Usage, Meters, and read the Rovo credits row. Use your spare credits in place of the 25-per-seat line, so the after-cost is roughly (developers x credits each, minus spare) x $0.01. Our test org's allowance is 3,920 and its monthly average is 1,189, so we'd have about 2,700 spare. A 200-seat company that already uses Rovo Chat heavily might have none.
The rate might not be one, either. Atlassian already lists the Rovo CLI as a premium interaction, and if that means more Rovo credits per task, every "after" column grows roughly by that ratio. At 1.5 Rovo credits per Rovo Dev credit, the 200-developer full-use row would be about $5,950, more than today.
And nobody knows the timing. Atlassian has said "at least 60 days' notice". If notice came tomorrow, the earliest switch would be in late December. Whether you'd pay for a Standard seat and Rovo credits for the same work in that month isn't covered on any page we read.
"You've reached your Rovo Dev credit limit": what it means and what the admin can do
One Community thread called "rovodev standard trial not working, You've reached your Rovo Dev credit limit" has 1,994 views, and another with the bare error as its title has 1,383. One asker wrote, "I have 0 usage of rovodev credits and still I'm getting You've reached your Rovo Dev credit limit!!!" An Atlassian team member replied on the first thread that they'd "uncovered a bug while rolling out new changes".
When the limit is real, the fix depends on the plan. On Free, Rovo Dev "will stop working until your usage resets in the next billing cycle", and there's no extra usage to buy. On Standard, an org admin can raise or switch on the extra usage limit (the billing doc puts it under Insights, Platform usage, Rovo Dev credits, then the Credit settings tab). Once a user runs through their credits and any extra usage, "Rovo Dev functionality will be disabled for them until the next billing cycle". For code reviews, the credits come from "the pull request author's allocation", so a developer who's out of credits also stops getting reviews.
On our org, though, the Insights menu now only has Analytics and Audit log, and the old Platform usage address doesn't open any more (usage lives under Usage, Meters). We can't tell you whether the Rovo Dev page moved with it, because we have no Rovo Dev to look at.
We couldn't measure one Rovo Dev credit: sign-up goes to sales
We meant to run three fixed tasks of known size through the CLI (explain a file, fix a failing test, a multi-file refactor) and read the credits each one used. We updated acli from 1.3.23 to 1.3.39 and logged in. The credit check refused us. Our org's Add app page offers three collections and six single apps, and Rovo Dev isn't one of them. Atlassian's trial doc still says "Under Rovo Dev, select Try it now". The site's trial button sends you to sales, and we weren't going to ask sales for a product that's being retired just to count credits.
So we don't have our own credits-per-task number, sorry. Atlassian's 5 to 50 tasks per 2,000 credits is the best figure out there. Our org's Rovo credits export from 20 October has 39 rows and not one of them is Rovo Dev, as you'd expect on an org that never had it.
Should you cancel your Rovo Dev subscription? Cancel unused seats, keep the CLI ones
If I were holding Rovo Dev seats this month, I'd go through them like this.
- Don't sign anything annual. Atlassian protects existing annual terms, but a new annual commitment to a product with an announced end of life buys you nothing. The pricing page only offers annual through sales anyway.
- Sort your seats into three groups. Code Reviewer only, CLI or IDE users, and people who never use it. The billing doc puts per-user numbers under the Rovo Dev credits Users tab, and each developer can see their own breakdown by feature on the Rovo Dev "Your usage" page.
- Cancel the seats nobody uses. A seat that used 50 credits last month still cost $20. Atlassian bills "any user who has write access to Rovo Dev features". So an org admin removes those people from the rovo-dev-agents-users- group (and any other group with the Rovo Dev User or App Admin role). Cancelling the whole subscription is "Contact us" on the billing doc, and the credits last until the end of the billing cycle. If you're not sure the next invoice will drop, one line to support settles it: "We've removed these users from the Rovo Dev Standard group. Please confirm they won't be billed from the next cycle, and whether they stay on Rovo Dev Free."
- Hold the Code-Reviewer-only seats until Atlassian's notice. When Code Reviewer appears in your Jira it runs without Rovo credit metering until 3 December, and Atlassian says it'll tell you when you can cancel. Our Code Reviewer setup guide covers what each review costs after that.
- Keep the CLI and IDE seats active. Atlassian asks you to, and there's no Rovo CLI to move to yet.
- Set a Rovo credits limit before 3 December. Code Reviewer will draw from the same pool as Rovo Chat, and the Rovo licensing page lists extra usage as "on (default setting)". Our guide to the Rovo usage limit walks through the screens, and the 2027 budget for 50 to 500 seats shows where Rovo sits next to the other meters.
If I had to bet, most teams will pay less after the CLI migration. An Atlassian team member wrote in October 2025 that 2,000 credits a month "suits most users", so most seats probably aren't using all of it. If most of yours sit under 500 credits a month, the one-to-one table says you'd pay about a quarter of today's bill or less. That bet depends on a rate Atlassian hasn't published, so I'll come back and update this page when the Rovo CLI price or the end-of-life date appears.
How many of your Rovo Dev seats used their 2,000 credits last month? If you've looked at the per-user numbers, I'd love to hear what share of your developers are heavy users, in the comments or at office@leanzero.net.
Originally published on leanzero.net. More Atlassian, Forge and local-AI write-ups at leanzero.net/blog, and if you're planning a migration or a Forge app, that's what we do: leanzero.net/services.
Top comments (0)