Atlassian Rovo pricing in 2026. What the credits cost and what to negotiate.

Rovo now comes inside every paid Atlassian Cloud plan and is metered in pooled credits. The cost sits in the tier you choose and the usage above the pool, so size both around the minority of users who drive consumption.

Rovo pricing changed shape during 2025, and many internal budgets still describe the old model. This guide sits alongside our Atlassian Cloud pricing guide, which covers the per user tier prices underneath.

How is Atlassian Rovo priced in 2026?

Rovo is no longer bought as a separate per user line. Atlassian includes it in every Standard, Premium and Enterprise Cloud plan for Jira, Confluence, Jira Service Management and the Collections. Usage is metered through a pooled monthly allowance of Rovo credits, so you pay for AI through your tier and any usage above the pool.

Through 2024 and into 2025, Rovo was a paid per user add-on sold only on Cloud Premium and Cloud Enterprise, and the default quote layered it across every Cloud seat. At Team '25 Atlassian announced Rovo for all paid plans. Premium and Enterprise sites were switched on between April 14, 2025 and July 2025, with Standard later that year.

Allowances from every product are added into one pool for the organization. A user licensed on both Jira Premium and Confluence Premium contributes 140 credits a month. The pool resets monthly and unused credits do not roll over.

Which Rovo features consume credits?

Atlassian sorts Rovo activity into four groups. The weights matter more than the pool size, because the same user can burn 10 credits or several hundred in a day depending on which features they touch.

• No credits. Rovo Search, Definitions and Summaries, plus basic Teamwork Graph calls such as looking up a single Jira work item or updating one.
• Basic intelligence, 10 credits per event. Rovo Chat quick answers, Rovo space creation, workforce management routing and basic agents without model selection.
• Premium intelligence, variable. Think Deeper mode in Rovo Chat, Confluence slide generation, agents in Jira, the Jira coding agent, Request Resolver and Create with Rovo.
• Enriched Teamwork Graph context, typically 1 to 10 credits per call. Calls that pull context across Jira, Confluence, Bitbucket and connected tools, such as a summary of a team's recent work or a unified search.

What happens when the credit pool runs out?

From December 3, 2026, Atlassian bills extra usage at $0.01 per credit, which is $10 per 1,000 credits. Extra usage is switched on by default, so features keep working and the bill keeps running until it reaches whatever spending cap your admin has set. Switch it off and Rovo interactions pause as soon as the pool is empty.

Admins get alerts at 80 percent and 100 percent of the allowance. Atlassian also sells prepaid annual credit packs with volume discounts, and that is where most of the consumption negotiation now happens. Automation is metered the same way, in steps per user per month, with extra steps billed at $0.50 per 1,000 from the same date.

Where does Rovo Dev fit?

Rovo Dev, the coding agent behind code review in Bitbucket and GitHub and the Rovo Dev CLI, is still sold per seat. It lists at $20 per developer per month with 2,000 Rovo Dev credits each. It needs a paid Jira Cloud plan, but seats go only to the developers who use it.

Licensing a whole department of 200 developers costs $48,000 a year at list before anyone has measured use, so start with a pilot group.

What does your Cloud tier already cover, and where does the AI cost sit?

Everything the old Rovo quote sold on top of the tier now sits inside it: third party connectors, generative summaries, agent style automation and Rovo usage analytics. The AI cost has moved into the tier decision, the credit pool and the extra usage rate. Price the tier first, then any consumption above it.

The table sets out what each tier gives you on the points that come up in a Rovo conversation. The broader tier comparison sits in our Enterprise versus Premium comparison.

Is Enterprise worth it for the Rovo credits alone?

Rarely, because Enterprise more than doubles the per user allowance over Premium for every licensed user, including the ones who never open Rovo Chat. The better reasons to step up are Atlassian Guard, group level control over who can use Rovo, and the admin features in the tier. The extra credits are a secondary benefit.

The same test applies to the Teamwork Collection. It carries 10 times the per user credits of a single Jira or Confluence plan (5 times the two together). That helps only if the people on it will consume them. Ask for the Collection quote next to a product plan plus a prepaid credit pack, sized to measured use.

How many Rovo credits does a 5,000 user company need?

Size the pool from the users who will use Rovo heavily, then check whether a tier step or a credit pack covers them more cheaply. This example is hypothetical. It uses the shape that worked for a 5,000 seat organization in our per seat deals: roughly 1,000 power users, 2,500 selective knowledge workers and 1,500 light users.

Assume all 5,000 users hold Jira and Confluence on the same tier. Power users average 600 credits a month (40 Chat answers plus some Think Deeper and agent work), selective users 120 credits, and light users 10. Monthly demand is 600,000 plus 300,000 plus 15,000, or 915,000 credits.

On Premium, extra usage costs $25,800 a year at list. A step to Enterprise breaks even only if it costs less than $0.43 more per user per month ($25,800 divided by 60,000 user months). Enterprise is priced well above Premium per user, so extra usage at list covers this shortfall more cheaply.

How does the answer change at 500 users or 20,000 users?

At 500 users on Premium Jira and Confluence, the pool is 70,000 credits a month. If 50 engineers each use 1,400 credits on Think Deeper and Jira agents, they exhaust it on their own. Smaller companies reach overage sooner and should cap it on day one.

At 20,000 users the pool is large enough for light users to cover heavy ones. There the question is whether the tier price itself is justified.

What did 2024 and 2025 Rovo negotiations show?

Across the roughly 30 to 45 Atlassian AI deals we advised between 2024 and 2025, Rovo value concentrated in a small set of heavy users. Only 15 to 25 percent of licensed seats showed real Rovo use in the first two quarters after an organization wide rollout. The rest billed exactly like the seats that were used.

• The adoption gap. Engineering leads, product managers, design, program office, compliance and support managers used Rovo. Light contributors and occasional users mostly did not.
• The blanket premium. Rovo on every seat priced AI at roughly 2 times a piloted rollout that delivered the same value.
• The off ramp. A consumption review and exit clause was what turned a wrong seat count into a correctable one.

Moving from the default all seat quote to a knowledge worker first mix with a capped agent pool held savings of 20 to 32 percent. Atlassian has since changed the product model. We expect the same concentration to show up in credit consumption, and a quarter of credit exports will show whether your organization fits that shape.

Why we disagree with putting every user on the top tier for AI

In 2024 the common advice was to add Rovo across all seats to standardize the AI rollout. In 2026 it arrives as a proposal to put everyone on Enterprise or the Teamwork Collection so no one runs short of credits. We disagree, because standardizing the rollout standardizes the bill and leaves adoption where it was.

Pilot with the teams that will use Rovo and measure credits per user for a quarter. Then buy capacity for them through a credit pack, and decide the tier on its own merits.

Pay for the credits your heavy users consume, and keep everyone else on the tier they need for other reasons.

Which Rovo and Cloud terms can you negotiate?

Five items open on the wider Cloud agreement once Rovo is on the table, and they work best as a package. The broader agreement is covered in our Atlassian enterprise negotiation guide, and the annual change list in the 2026 pricing changes.

1. Right size the AI population. Keep the tier where the whole user base needs it, and buy Rovo Dev seats only for developers who use the coding agent.
2. Cap the credit pool spend and lock the top up rate. Quote the prepaid pack price up front, lock it for the term, and set the spending cap in the admin console to match the budget line.
3. Cap the per user rate for the term. The tier price now carries Rovo, so a multi year price hold on the tier and on Rovo Dev seats protects the AI cost from the annual catalog change.
4. Cap the annual escalator. We typically hold it at 5 to 7 percent against a list uplift that has been running near 8 percent. Atlassian's FY26 notice, effective October 15, 2025, raised Standard by 5 percent, Premium by 7.5 percent and Enterprise by 7.5 to 10 percent. The next change, effective October 13, 2026, adds 7 to 10 percent on Jira and Confluence Standard and Premium and 8 percent on Enterprise.
5. Reopen the Premium versus Enterprise step. The AI conversation usually shifts the tier floor, so price that step inside the same negotiation.

What contract wording should you ask for?

• A fixed credit rate card. The credit weight for each existing feature, such as 10 credits per basic event, held for the term, with advance written notice before any reweighting. The unit of consumption is what you are buying.
• Locked extra usage and pack pricing. The $0.01 list rate and your pack discount written into the order form, so a price change on consumption cannot reach you mid term.
• Roll over on prepaid credits. The included allowance resets monthly by design, and Atlassian publishes no roll over terms for its annual packs. Ask for unused prepaid credits to carry forward at least quarterly, because a pack sized on a forecast will rarely match actual use month by month.
• A reduction right at each anniversary. The right to step down a tier or cut Rovo Dev seats if measured use stays low. This is the off ramp that made the difference in earlier deals.
• Usage reporting to your own admin. A monthly usage statement, with the 80 percent and 100 percent alerts also going to a named finance contact.

What will the Atlassian account team say, and how should you reply?

• "Rovo is included now, so there is nothing to negotiate." Reply that the tier price, the pack price, the extra usage rate and the credit weights are all commercial terms, and ask for each on the order form.
• "Your users will run out of credits on Premium." Reply with your credit export and ask for a pack quote sized to it next to the Enterprise quote.
• "The Teamwork Collection gives you 10 times the credits." Ask for the Collection price against your product plans plus a pack, at your measured consumption.
• "Keep extra usage on so no one is blocked." Agree, with a spending cap set to the approved budget, raised by purchase order when the data supports it.

What should the Rovo data and AI terms say?

Rovo is governed by the Atlassian Customer Agreement and its related policies, and enterprise buyers negotiate an addendum or order form on top. That paper holds the money and the risk. Read it the way Microsoft buyers read the Azure OpenAI addendum or Salesforce buyers the Einstein addendum, and mark it up before anyone discusses tiers.

• Training. Written confirmation that customer content is not used to train models.
• Models. Disclosure of which models sit behind Search, Chat and Agents, and notice when they change.
• Region. The data center region for content Rovo processes.
• Retention. A defined window for prompts, agent context and responses.

Each of those is a clause that either exists in your paper or does not, and the missing ones default to the seller. Data Center customers face the same AI question from the other direction, because Rovo's pricing is built into the Cloud plans. That is covered in our Data Center end of life guide.

How do you check your own Rovo usage?

Atlassian gives admins the data needed for a credit case. Pull it before the account team sends a proposal.

• Credit report. Atlassian Administration, then Insights, then Platform usage, then Rovo credits. It shows total allowance, current usage, app trends, user level consumption and a feature breakdown.
• CSV export. Up to 3 months or 1 million events, with feature, user, agent, timestamp and credits for each event.
• Access settings. Atlassian Administration, then Rovo, then Rovo access. Standard and Premium admins can block Rovo by app for everyone. Only Enterprise can allow or block Rovo by user group, which is the control you need to keep heavy features with the teams you funded.

When should you start the Rovo and Cloud renewal work?

Open the file 9 months before the Cloud anniversary, and earlier for multi entity organizations. This year the extra usage start date adds a deadline that applies whatever your renewal date is.

What to do next

1. This month. Set a spending cap on Rovo extra usage before December 3, 2026, and route the alerts to IT and finance.
2. Build the baseline. Pull the Cloud seat count by legal entity, team and product, and export three months of Rovo credit data.
3. Find the heavy users. Identify the teams driving consumption and size the credit pool and any Rovo Dev seats around them.
4. Price both routes. Ask for a tier step quote and a prepaid pack quote on your current tier, and compare them against measured demand.
5. Write the terms. Put the credit rate card, pack price, prepaid roll over, reduction right and data terms into the order form.
6. Close as one package. Lock the escalator cap and multi year price hold 60 days before the anniversary. Our Atlassian practice can run the assessment and the negotiation with you.

Frequently asked questions