Atlassian Rovo credits from 3 December: what Jira and Confluence teams will pay

From 3 December 2026, Atlassian Cloud charges for Rovo AI and automation use beyond each organisation's monthly allowance: US$10 per 1,000 Rovo credits and US$0.50 per 1,000 automation steps, on top of your seat licences. Extra usage is switched on by default, so unless an admin sets a limit, a team that leans on Rovo Chat and agents will see a new usage line on its next invoice. For most Jira and Confluence customers the Rovo meter is the one to watch; automation steps cost little but stop your rules if you cap them too tightly.

A man reviewing figures on a tablet at a wooden desk

Atlassian announced usage-based pricing on 1 September 2026 (Inside Atlassian). The credit rates already apply to usage recorded since 31 August, so your admin console holds more than two months of real data. This guide explains what each meter counts, what your plan includes, a worked AUD example for a 300-person organisation, and the settings to check before the first billed month. For list prices, GST and the October price rise, see our guide to Atlassian Cloud pricing in AUD.

What exactly starts on 3 December?

Atlassian now meters five things on top of seat-based subscriptions (usage-based pricing): Rovo credits, automation steps, Assets objects, Bitbucket build minutes and storage, and AI agent resolutions in Customer Service Management. Seat prices don't change. What changes on 3 December is that allowances become limits, and use above them is billed.

For Jira and Confluence teams, two meters matter:

  • Rovo credits cover Rovo Chat, Rovo agents, Confluence AI slides, the Jira coding agent and enriched Teamwork Graph queries.
  • Automation steps cover every trigger, condition, action, branch and loop that runs in an automation rule.

Rovo Search, definitions and in-line summaries stay free (Rovo usage limits).

How many Rovo credits does your plan include?

Every paid Jira, Confluence, Teamwork Collection and Service Collection subscription includes a monthly allowance per licensed user (Rovo usage limits):

Product Standard Premium Enterprise
Jira 25 70 150
Confluence 25 70 150
Teamwork Collection 250 700 1,500
Service Collection 250 700 1,500

Credits per user per month. Source: Atlassian, as of 4 November 2026.

Three rules decide what that means in practice:

  1. Allowances pool across the organisation. Atlassian adds up every user on every app into one pool. Its own example: 100 Jira Premium users plus 100 Confluence Premium users give 14,000 credits a month. Per-user allocation is listed as "coming soon".
  2. They reset monthly and don't roll over. Annual subscribers get a fresh monthly allowance, not a yearly lump sum.
  3. Sandbox use counts. Rovo credits and automation steps used in a sandbox draw on the same production allowance (usage-based pricing). Test agents in a sandbox and you are spending real credits.

What does one Rovo credit buy?

Atlassian prices Rovo by the "billable event": each message a user sends in Rovo Chat, and each time an agent is invoked, is one event (Rovo usage limits).

  • Basic features cost 10 credits per event: Rovo Chat quick answers, Rovo space creation, workforce management routing, and basic agents without model selection.
  • Premium features cost a variable number of credits: agents with model selection, Think Deeper, Confluence slides, agents in Jira, the Jira coding agent, Request Resolver, Alert Intelligence, the self-service agent and Create with Rovo. The cost depends on reasoning steps, searches, tools used and the model.
  • Enriched Teamwork Graph calls usually cost 1 to 10 credits each. These are cross-product lookups such as searchAtlassian. Installing the Rovo MCP server, write operations and single-product lookups are free.

At list price, 1,000 credits cost US$10, which is about A$14.33 at the Reserve Bank's 3 November rate of US$0.6976 (RBA). So one basic chat message beyond your allowance costs about 14 cents in AUD. Premium features cost more per event, and Atlassian doesn't publish a fixed figure for them, which is why your own usage data matters more than any rate card.

How are automation steps counted?

A step is any single part of a rule that runs (how automation usage is calculated):

  • The trigger counts once per run.
  • Each condition that runs counts, even when it evaluates to false. A rule that fires on every issue update and then filters most of them out still pays for the trigger and the condition every time.
  • Each action counts each time it runs.
  • A branch counts once, plus the steps on the path that runs.
  • A loop counts once, plus every step inside it for every item.

Some steps are free: log actions, creating variables and lookup tables, re-fetching work item data and looking up work items. Aborted or throttled runs and Atlassian system errors aren't charged. "Use Rovo" and "Use agent" components bill as Rovo credits, while third-party AI actions such as Use Cursor and Use GitHub Copilot count as automation steps.

Monthly step allowances per user are 400 (Jira Standard), 750 (Premium) and 1,000 (Enterprise); Confluence gets 100, 250 and 500; Service Collection gets 3,000, 6,500 and 9,500; Teamwork Collection 2,500, 5,000 and 7,500. Like Rovo credits, they pool across the organisation. Extra steps cost US$0.50 per 1,000.

The loop rule is where step counts grow. A rule triggered on a parent work item that checks one condition and then loops over five sub-tasks with two actions each runs 13 steps, not 4. Even Enterprise plans now have a ceiling: 1,000 steps per Jira user a month.

What will a 300-person organisation pay?

Take a 300-user organisation on Jira Standard and Confluence Standard, with no Collections. Its pooled monthly allowances are:

  • Rovo credits: 300 × 25 (Jira) + 300 × 25 (Confluence) = 15,000 credits.
  • Automation steps: 300 × 400 (Jira) + 300 × 100 (Confluence) = 150,000 steps.

Now assume half the staff use Rovo Chat or a basic agent three times a working day (10 credits each, 21 working days), and the team runs the 13-step sub-task rule above 25,000 times a month.

Meter Monthly use Allowance Extra usage Cost per month (USD) About AUD a month, ex GST
Rovo credits 94,500 15,000 79,500 US$795.00 A$1,140
Automation steps 325,000 150,000 175,000 US$87.50 A$125

AUD at US$0.6976 per A$1 (RBA, 3 November 2026), rounded to the nearest A$5.

The Rovo line works out at about A$13,700 a year before GST, for basic chat alone. Premium agents, Think Deeper and agents that run on every new work item would push it higher. On Premium plans the same usage leaves 52,500 credits over the 42,000-credit allowance, or US$525 a month. On Teamwork Collection Standard, the 300 users would share 75,000 credits a month, which covers about four-fifths of this example. Our Atlassian Cloud pricing guide compares those subscription prices in AUD.

Two currency points apply to every usage charge. Atlassian can't quote or invoice cloud products in Australian dollars, so usage is billed in USD, and Australian customers pay 10% GST on top (Atlassian purchasing FAQ). A weaker dollar raises the AUD cost of the same usage.

The automation line is small by comparison. Its real risk is operational, which the next section covers.

What happens when you hit the limit?

That depends on one setting per meter: extra usage. Atlassian says it is on by default for most organisations (usage-based pricing).

With extra usage on, everything keeps running after the allowance is used, and the overage is billed in arrears on your next invoice. For most customers that is monthly (usage charges and billing). If you also set a monthly limit, features pause when the limit is reached.

With extra usage off, features pause at 100% of the allowance until it resets:

  • Rovo stops billable chat and agent interactions. Search, summaries and definitions keep working.
  • Automation stops running new steps, including manual runs. Events that happen while automation is paused are not replayed when the allowance resets. A rule that assigns tickets, syncs a status to another system or notifies an on-call team simply doesn't run for those events.
  • In Customer Service Management, requests the AI agent would have resolved go to human agents instead.

For most teams, the right answer is to keep extra usage on for automation with a generous limit, because 1 million extra steps cost US$500, and to set a tighter limit on Rovo credits while you learn your real usage.

What should admins do before 3 December?

Atlassian sends usage alerts at 80% and 100% of the allowance and of any limit, but only to organisation and billing admins. Your Jira and Confluence users won't know they're spending until features pause. Five steps, in order:

  1. Export your usage since 31 August. In Atlassian Administration, go to Usage, then Meters, then Rovo credits, and select Export data. The CSV lists feature, user, agent, timestamp and credits for up to three months; the download link expires after 24 hours. Check the automation steps meter in the same view.
  2. Find the top consumers. In most organisations a handful of agents, rules or power users account for most of the usage. Look for agents triggered on every new work item, rules that fire on every update and filter afterwards, and loops over large result sets.
  3. Fix the expensive rules. Move conditions into the trigger where you can (conditions inside a trigger don't add steps), narrow triggers, and check whether a loop over many work items can be replaced by the free Lookup work items step and fewer actions.
  4. Set a limit per meter. Go to Billing and subscriptions, choose the meter, select Update extra usage limit and save a monthly cap. Organisation or billing admins can change it at any time (manage extra usage). If you set it below what's already been used that month, metered features stop until the reset.
  5. Decide on the plan question. If credit use is consistently several times your allowance, compare the cost of extra usage with Premium or a Collection at your next renewal. Atlassian lists usage packs and committed annual packs as coming soon.

Then add the meters to your monthly reporting. Usage-based billing makes Atlassian a variable cost, and finance will want a forecast and an owner.

Where does this fit with the rest of your Atlassian estate?

Rovo's value comes from what it can reach through the Teamwork Graph: Jira, Confluence, Jira Service Management and the third-party tools you connect. That also makes it the place where usage grows quietly, as more teams build agents on top of more connected data. Treat Rovo agents like any other automation: each one needs an owner, a purpose and a budget. Our guide to the Atlassian System of Work maturity model covers how to set that up across teams, and our ServiceNow to Jira Service Management cost comparison shows how the meters affect a service desk business case. For rule design, see integrating automation with Atlassian ITSM.

We have implemented Jira, Jira Service Management and Confluence for a global manufacturer, and our Rovo services page explains how we plan and build Rovo agents. Our Atlassian licensing team can quote and invoice in AUD and review your plan mix before renewal.

Frequently asked questions

Can I give each team its own Rovo budget?

Not yet. Allowances and limits apply at organisation level. Atlassian lists per-user allocation as coming soon, so for now the controls are the organisation limit and your own reporting from the usage export.

Do AI features in beta use credits?

Not at the moment. Atlassian says beta AI features don't count against allowances unless stated otherwise, but they may count once they are generally available.

Is the 3 December date the same for every customer?

Atlassian says billing begins on 3 December 2026 for most meters, and timing can vary by capability and billing cadence. Check the Platform usage page in Atlassian Administration for your organisation's dates.

If you'd like a second pair of eyes on your usage export, or a plan and limit recommendation before your first billed month, talk to us.

Let's work together.

Turn insight into action with a team that delivers.