CX news · Retention and loyalty · Atlassian
Atlassian's October 2026 cloud price rise: what it means for the renewal journey
In short
On 13 October 2026, Atlassian lifted cloud list prices across Jira, Confluence, Jira Service Management, Guard, Bitbucket and Jira Product Discovery. The rise applies to renewals and upgrades as well as new purchases, and auto renewing annual subscriptions are charged the new price. An independent tracker puts Jira's per user rise at about 7%. For any software company, a price rise is a renewal moment that customer success should design, not just announce.
Who this is for: Customer success leads, renewal managers and executives in Australian software and subscription companies, and the teams who buy and renew business software.
What changed, and when
Atlassian's pricing FAQ states that new cloud list prices took effect on 13 October 2026, Pacific Time. The update covers Standard, Premium and Enterprise plans for Teamwork Collection, Jira, Confluence and Jira Service Management, as well as Atlassian Guard, Bitbucket Premium, Jira Product Discovery and Atlassian Government Cloud.
The FAQ is explicit that the update "impacts new purchases as well as renewals and upgrades of existing subscriptions." Monthly customers see the new price on bills issued on or after 13 October. For annual customers, quotes generated or modified from that date use the new price, and auto renewing annual subscriptions are charged the new price on the card on file.
Atlassian says it is updating prices to reflect new capabilities, citing Loom and Rovo in Teamwork Collection, AI in Jira and Confluence, and Bitbucket improvements.
How big the rise is
Atlassian's FAQ does not give a single percentage. PricingSaaS, which tracks published software prices, recorded Jira Cloud Standard moving from $7.91 to $8.48 per user per month and Premium from $14.54 to $15.56, about 7% each, based on monthly billing for 300 users. It counts this as the third Jira price rise on its record.
The same tracker noted that Atlassian's pricing page carried no announcement of the change on the page itself, and its other copy was unchanged.
What Atlassian built into the transition
The FAQ shows several transition steps that are worth noticing because they shape the renewal experience:
- Quotes generated before 13 October are honoured at the prior price until they expire.
- Monthly customers could request an annual quote before 13 October to keep existing pricing, with payment due before the quote expires and no extension beyond 11 November 2026.
- Upgrades made before the effective date kept existing pricing.
- Usage based charges are separate from the list price rise, and the FAQ states that extra usage billing requires opt in.
What it means for the renewal journey
A list price rise lands differently for each customer. For a monthly customer it shows up on the next bill. For an annual customer on auto renewal it shows up as a larger charge on a card. For a customer mid negotiation it shows up in a new quote. Each of those is a separate moment in the journey, and each needs its own message.
In our experience, the price rise is rarely the problem on its own. The trouble starts when the customer learns about it from the invoice, when the person who signs off on the renewal is not the person who uses the product, or when nobody can explain what the customer has gained since last year.
Atlassian tied its rise to new features. That only works if customers have actually adopted them. A customer success team facing its own price change should check adoption of the features it plans to point to before the notice goes out.
If your company is planning a price change
These are the questions we would work through with the renewal and customer success teams before any price rise:
- Who hears first: the user, the admin or the person who pays? Map all three.
- How far ahead of the effective date does each segment hear, and through which channel?
- What can a customer do before the date, such as lock in a term, and is that easy to find?
- Which accounts have low adoption of the features the rise is justified by, and who calls them first?
- Who owns the follow up when an auto renewal is charged at a higher price?
Where to start
Price changes, renewals and the first 90 days are the journeys we are focused on this month for software and subscription teams. More at breme.com.au/customer-success/.