Atlassian usage-based pricing: what starts billing on December 3, and who has to act

Atlassian usage-based pricing becomes real money on December 3, 2026: that is the day extra usage billing takes effect for Rovo credits and for automation steps in Jira and Confluence. Extra usage is enabled by default, so if nobody in your organization touches the setting, the first surprise arrives on a December invoice.

That is the whole change in one sentence, but the detail decides whether it costs you anything. Below are the meters that start billing, the allowance your plan includes, what a step and a credit actually consume, the three clicks that cap or switch off overage, and which teams can ignore all of it.

What Atlassian usage-based pricing bills from December 3

Atlassian announced the expanded meters on September 1, 2026, in a post by chief product and AI officer Tamar Yehoshua that named three things it would start metering: Rovo credits, automation steps and AI agent resolutions. The post said allowance limits and billing take effect on December 3, 2026.

The meters sit beside your seat subscription rather than replacing it. Seats still cost what they cost; the meters bill only what runs past the allowance those seats include.

What each one counts, per Atlassian's own documentation:

• Rovo credits cover the deeper AI interactions - Rovo Chat, Confluence AI Slides, the Jira coding agent, Teamwork Graph queries. Atlassian says in-line summaries, rewrites and Rovo Search stay free.
• Automation steps count every executed part of a flow. Atlassian's automation docs are explicit: "Every trigger, condition, action, branch, and loop that runs in a flow counts as a step toward your usage." A trigger that fires and matches nothing still ran.
• AI agent resolutions apply to customer service work, where an AI agent closes a request without human escalation.

Atlassian's billing documentation also lists Assets objects and four Bitbucket meters - build minutes, Git LFS, packages network and packages storage. Extra usage is charged on your next invoice, and for most customers that invoice is monthly.

Your allowance is per seat on paid plans, and pooled across the organization

The allowance is not a flat number per site. It scales with your plan and your seat count, then pools across the organization, and unused capacity does not roll over to next month. These are the figures Atlassian publishes, as of October 2026:

Sources: Atlassian's Rovo credit allowances and its automation usage documentation, which also gives Free-plan allowances of 150 automation steps per Jira subscription and 50 per Confluence subscription - per subscription, not per user.

Past the allowance, Rovo credits list at $0.01 each, or $10 per 1,000. Extra automation steps are $0.50 per 1,000 steps. Those rates look small, and in our view that is exactly what makes them easy to miss: a single busy automation rule, multiplied by its steps and its runs, is where a metered bill grows without anyone deciding to spend. We made the same argument about credit-based pricing at GitHub, Notion and Warp - the unit is cheap, the consumption is invisible until it is billed.

The 25-credit tier is the one to model first

A Jira Standard seat includes 25 Rovo credits a month. Atlassian does not publish a per-action credit price list on the pages above, so we are not going to guess how many credits a Rovo Chat thread burns - but 25 credits per user is a small pool, and it is shared with everyone else in the organization.

In our view, that makes Standard the tier most likely to produce an unexpected December invoice, not Enterprise. Enterprise gets 150 credits per user, six times the Standard pool, and an Enterprise agreement is bought by someone whose job includes the invoice. A 40-person Standard organization has 1,000 pooled credits for the whole month, shared between everyone who opens Rovo Chat.

Enterprise automation is no longer unlimited

The quieter half of this change is automation. Atlassian moved from counting whole flow runs to counting individual steps, and Enterprise plans now carry a published allowance - 1,000 steps per user per month for Jira - rather than unlimited automation.

If you built your Jira automation on the assumption that runs were free at Enterprise, that assumption expires on December 3. Multi-step rules with branches and loops are the expensive ones, because Atlassian counts a loop as its repeated iterations rather than as a single step.

Atlassian's documentation is clear about what happens at the ceiling. With extra usage enabled, "Metered features continue to run without interruption" and the overage lands on your next invoice. With extra usage disabled, "your automation flows will stop running until usage resets on your usage billing date" - and we would decide that trade-off deliberately rather than by default, because a stopped flow can mean unassigned tickets rather than a saved dollar.

Who has to act, and who can skip this

Act before December 3 if you are an organization or billing admin for a paid Jira, Confluence, Service Collection or Teamwork Collection subscription - especially on Standard, and especially if your team runs automation rules with loops or has Rovo turned on.

You can mostly ignore it if you are on a Free plan, where there is nothing to bill against, or if your team's Atlassian use is Trello and nothing else: Trello does not appear in Atlassian's Rovo credit allowance table as of October 2026, which covers Jira and Confluence plus Loom, Service Collection and Teamwork Collection. Bitbucket is metered separately under its own four meters.

One honest wrinkle in the documentation: the Rovo credits page states "Extra usage is enabled by default," while the billing page says enabling extra usage requires a payment method on file, and that a billing admin must add payment information if none exists. If your organization has never stored a card, the practical exposure may be lower than "enabled by default" sounds. We would not rely on that - check the setting rather than infer it.

Three things to do before December 3

1. Open Atlassian Administration, click Billing, and open each meter in the Subscriptions list to see current consumption against your allowance. Organization admins can reach the same view through Insights then Platform usage.
2. Decide per meter. Atlassian's instructions are to click Update extra usage limit to set a monthly cap, or to use the dropdown beside it and select Disable extra usage to stop overage entirely. Disabling does not erase extra usage you already incurred - that still bills.
3. Audit your heaviest automation rules for loops and branches now, while the step counter is visible and nothing is billable. If a rule exists only to sync a field nobody reads, we would delete it this month.

Separately, Atlassian raised cloud list prices on October 13, 2026 for Jira, Confluence, Jira Service Management and several other products, and its pricing FAQs say quotes created before that date hold the old price until they expire, with no extension past November 11, 2026 PT. That is a separate change from the meters, and worth checking if your renewal is close.

If auditing the rules points you toward moving some workflows out of Jira entirely, Upfynd lists 297 products in Automation & No-Code and 589 in Task & Project Management as of October 2026, including Activepieces, listed as open-source automation; Confluence-adjacent options sit in Notes & Knowledge. Check any of them against their own pricing page before you commit: on the changes we have tracked this year, per-step and per-credit billing is spreading, so a move can swap one meter for another.