Atlassian changes its prices twice this autumn: list prices on 13 October, metered AI from 3 December

Atlassian changes its prices twice this autumn: list prices on 13 October, metered AI from 3 December

21 September 2026 — Atlassian customers face two separate changes in the next ten weeks, and they need different responses. The first is an ordinary list-price rise. The second changes what is being paid for.

13 October: list prices

Atlassian notified cloud customers on 28 August that list prices rise on 13 October 2026 for new purchases, renewals and upgrades. We have not been able to read the detail on Atlassian's own pricing-update page, which did not render it to us, so the figures here are as published by two Atlassian partners from that customer notice.

Both put the range at 3% to 10% depending on product, plan and seat count. Jira, Confluence and the Teamwork Collection rise by 7% to 10% on the Standard and Premium plans — one partner ties the step to size, 7% below 5,000 seats and 10% at or above — and by about 8% on Enterprise. The Service Collection rises 7.5% on Standard and Premium and 10% on Enterprise; Bitbucket Premium 10%; Jira Product Discovery 5%; Atlassian Guard 3% on Standard and 5% on Premium. Government Cloud prices rise too.

A third partner quotes slightly lower figures for individual plans — 7.2% on Jira Standard and 6.7% on Confluence Standard — so treat every percentage here as approximate until your own quote arrives. The same notice adds the point that matters most for timing: a quote generated before 13 October is honoured at the old rate until the quote expires.

3 December: usage becomes a line on the bill

The second change is Atlassian's own announcement, published on 1 September by its chief product and AI officer. Three capabilities become metered: Rovo credits, automation steps, and resolutions completed by AI agents. In Atlassian's words, "allowance limits and billing for these meters will go into effect on December 3, 2026." Eligible paid plans include allowances; beyond them a customer can upgrade the plan, pre-pay for credits or pay as they go, with alerts before a limit is reached. In-line summaries, rewrites and Rovo search remain free.

What the announcement does not state is the size of each plan's allowance or the price of usage beyond it, which is exactly what a buyer needs to estimate the effect.

What it means for a buyer

For the list price, the lever is the calendar. If a renewal or an expansion falls after 13 October, get a quote before that date and check its expiry.

For the December change, the lever is measurement, and it is the more consequential of the two for heavy users of automation, because a busy automation estate starts to show up as usage on a bill rather than only as a plan limit. Between now and December, find out how many automation steps and agent resolutions each site actually consumes, ask your account team or partner for the allowance that applies to your plan in writing, and set the usage limits and alerts in Atlassian Administration before billing starts rather than after the first invoice. A rule that loops, or an agent enabled on a busy queue, can become a cost from 3 December in a way it was not on 2 December.

Sources

• Atlassian, "Atlassian's usage-based pricing: AI value with predictability and control", Tamar Yehoshua — 1 September 2026
• The Adaptavist Group, "Atlassian Cloud price updates, effective October 2026" — 28 August 2026
• Seibert Group, "Atlassian Cloud Price Increase 2026: What Changes Oct 13" — 10 September 2026
• TribusIT, "Atlassian Cloud Prices Are Going Up in October 2026" (read 21 September 2026) — 21 September 2026