Rovo isn’t a product you buy — it’s a meter on products you already pay for. There’s no separate Rovo SKU for most teams: it’s bundled into paid Jira and Confluence Cloud editions, and instead of a per-seat fee you get a pooled monthly allowance of credits that agent runs and AI chat draw down. The number that matters is your allowance — 25, 70, or 150 credits per user per month on Standard, Premium, and Enterprise — and understanding what actually burns it. Get the credit model wrong and you’ll either over-budget for something you already own or under-budget the one piece that’s genuinely a separate bill.
Is Rovo a separate purchase?
No. For standard Rovo — agents, Rovo Chat, cross-product search inside Jira and Confluence — there’s nothing to buy on top of a paid Cloud plan. Atlassian ships it with paid editions and meters usage rather than charging per seat. That’s the mental shift: the question isn’t “should we license Rovo,” it’s “how much of our included allowance will we burn, and what happens when we hit the limit.”
The one real exception is Rovo Dev, the coding-agent product, which is a paid subscription with its own pricing and its own credit pool. More on that below, because keeping it separate in your head is the whole game.
What is a Rovo credit?
A credit is Atlassian’s unit for metering AI work. Not every action costs one. Per Atlassian’s Rovo usage allowance docs, the costs break down like this:
| Action | Credit cost |
|---|---|
| Rovo Agent run | 10 credits |
| Chat Quick Answer | 10 credits |
| Deep Research request | 100 credits |
| Search, summaries, definitions | Free |
So the expensive things are the ones that do work — running an agent, getting a synthesized answer, or kicking off deep research. The lightweight retrieval features — search, quick summaries — don’t touch your allowance at all.
How much allowance do you get?
Credits come as a monthly allowance that scales with your plan tier, pooled at the organization level and reset each month with no rollover. For the Jira, Confluence, and Service collections:
| Plan | Credits per user / month |
|---|---|
| Standard | 25 |
| Premium | 70 |
| Enterprise | 150 |
Two details change how those numbers feel in practice. First, they’re pooled org-wide: a 50-seat Standard org has 1,250 credits a month to share, so a few heavy users can lean on colleagues who never touch Rovo. Second, do the arithmetic on a single Standard seat — 25 credits at 10 per agent run is about two and a half agent runs per user per month. That’s fine for occasional, high-value calls and completely wrong for a task you’d run dozens of times a day. (Atlassian’s Teamwork Collection carries much higher allowances — 250/700/1,500 — but the Jira-side numbers most teams care about are 25/70/150.)
What happens when you run out of credits?
This is where a lot of the internet is wrong, so be precise: as of now, nothing punitive happens. Atlassian’s usage docs state it is not currently billing for usage above your Rovo credit allowance, and that it will give at least 90 days’ notice before credit limits take effect.
That means today Rovo does not hard-stop, throttle, or degrade features once the pool is empty. Features don’t “pause” or “slow down” past the allowance — the meter simply keeps running and stays visible in your org’s usage view. There’s no surprise invoice and no forced downgrade. This is a genuine grace period, not a trap that springs the moment you cross the line. It will change eventually — overage will become billable — which is exactly why it’s worth watching org-level consumption now, while the stakes are only informational.
Rovo vs Rovo Dev: don’t conflate the two bills
The single most common Rovo sizing mistake is treating Rovo Dev as part of the standard allowance. It isn’t.
Rovo Dev is Atlassian’s coding agent, and it’s a separate product at $20 per developer per month (Rovo Dev pricing). That subscription comes with its own allocation of 2,000 Rovo Dev credits per developer per month, and overage there is billed — at $0.01 per credit beyond the allowance (how billing works for Rovo Dev). Critically, Rovo Dev credits only work for Rovo Dev functionality and are tracked entirely separately from the 25/70/150 standard allowance.
So the two live in different columns of your budget:
| Standard Rovo | Rovo Dev | |
|---|---|---|
| How it’s sold | Included with paid Jira/Confluence Cloud | Separate $20 / developer / month |
| Monthly credits | 25 / 70 / 150 per user (plan tier) | 2,000 per developer |
| Overage today | Not billed (90 days’ notice promised) | Billed at $0.01 / credit |
| Credit pool | Shared org-wide for Rovo agents & chat | Separate, Rovo Dev only |
Model developer-agent spend on the Rovo Dev line, and your knowledge-worker spend on the standard allowance. Adding them together — or assuming the $20 buys you more standard Rovo credits — is how teams end up with a number that’s wildly off.
Where this leaves a Jira team
If you’re on a paid Jira Cloud plan, you already have Rovo; the practical work is deciding what to spend a metered, org-pooled 25/70/150 allowance on. Spend it on the broad, occasional, high-value calls agents are built for — work breakdown, research, cross-product questions — and don’t burn it on a repetitive writing job you do all day, because at 10 credits a run the meter isn’t priced for that. To size your own team’s monthly draw against that pool before you commit to a plan tier, run the numbers through our Rovo credit cost estimator. For how Rovo stacks up against the other AI many teams evaluate alongside it, see Rovo vs Copilot for Jira teams; if your interest is the developer side specifically, Rovo’s DevOps integration covers what the coding agent actually plugs into. And before you enable it org-wide, the pre-rollout security checklist covers the admin decisions the credit math doesn’t — connector blocklists, data residency, disconnect behavior, audit scope.
And if what you actually need is Rovo working for you rather than another dashboard to read, Crosstown’s Rovo tooling is built to get more out of the agent allowance you’re already paying nothing extra for — so the credits you do spend go to the work that’s worth 10 of them.
And if the agent you want doesn’t exist yet, we build them.