Atlassian's Prices Are Going Up Again: Here's What's Changing and What To Do About It
Brett Celliers
31 August, 2026
You’ve probably had an email from Atlassian in the last day or two. Subject line: “Important updates to Atlassian Cloud pricing.” If you skimmed it and moved on, it’s worth a proper look, so we’re breaking it all down here.
From 13 October 2026 (Pacific Time), Atlassian is increasing list prices across pretty much its entire Cloud portfolio. New purchases, renewals and upgrades from that date will be at the new rates. If you’ve already got a quote in hand from before then, it’ll be honoured until it expires. If your annual subscription renews after that date, you’re on the new pricing.
The Numbers
Here’s what’s actually changing, plan by plan:
- Jira Cloud (Standard and Premium): 7% for orgs under 5,000 seats, 10% for orgs over 5,000. Enterprise is a flat 8%
- Confluence Cloud (Standard and Premium): same shape, 7% under 5,000 seats, 10% over. Enterprise at 8%
- Jira Service Management / Service Collection: 7.5% on Standard and Premium, 10% on Enterprise
- Teamwork Collection (Standard and Premium): 7% under 5,000 seats, 10% over. Enterprise at 8%
- Bitbucket: Premium up 10%, and Standard is losing its minimum 5-seat tier
- Jira Product Discovery: 5% on both Standard and Premium
- Atlassian Guard: 3% on Standard, 5% on Premium
If you’re running Jira Service Management specifically, that’s a 7.5 to 10% increase on top of whatever you’re already paying, and it comes hot on the heels of Atlassian folding Customer Service Management, Assets and Rovo into Service Collection. More is included than there was six months ago. It also costs more than it did six months ago.
Why It’s Going Up
Atlassian’s answer, in short, is AI and platform investment, and they’ve published a proper breakdown of what that’s meant product by product. The headline items:
- Jira: agents you can assign work to, @mention in comments or trigger from workflows, plus Rovo turning briefs and meeting notes into structured work items, and native support for third-party agents like Claude, GitHub Copilot and Cursor through MCP
- Confluence: Confluence Slides (turning a page into a deck), an AI editor giving inline writing help, and Rovo-powered page creation from scratch
- Jira Service Management / Service Collection: out-of-the-box AI request resolution and HR onboarding agents, Rovo Ops for alert grouping and incident handling, and Asset Management now scaling to 10 million objects with lower per-object costs
- Bitbucket: built-in package management, merge queues, and self-hosted runners
- Atlassian Guard: 60 new detections, full-site scanning for legacy content, and SIEM integration
Underneath all of that sits the Teamwork Graph, now over 150 billion objects and relationships deep, which is what lets the AI agents actually understand context across your tools rather than working blind. Jira is being pitched as “the control plane for AI-native teams.” Confluence is now an “AI-native source of truth.” Service Collection is the vehicle for running IT operations and resolving requests with AI working across every step.
None of that’s wrong. Atlassian has genuinely shipped a lot in the last twelve months, and if you’re on JSM / Service Collection, quite a bit of it (Rovo Ops, the AI agents, the expanded Asset Management) is sitting in your licence right now whether you’ve turned it on or not. But shipped features and used features are two very different things, and that gap is exactly where this gets interesting.
The Bit That Actually Matters
Here’s the pattern worth sitting with: Atlassian puts prices up every year, usually somewhere in the high single digits. That’s not going to stop. It’s priced in as a strategy, tied to genuine investment, and every vendor in this space is doing some version of the same thing.
So the only lever a customer actually controls isn’t whether the price goes up. It’s whether they’re getting proportionally more value out of what they’re paying for. If your JSM bill goes up 7.5% this October but you’re still only using half of what’s actually sitting inside your licence, you’ve taken a straight cost increase with nothing to show for it. If you go and switch on Customer Service Management, get Assets properly configured as a CMDB, and start using the Rovo agents that came bundled in for free, that same price increase looks a lot more reasonable, because the platform’s doing more for you than it was last year.
We’ve seen this play out with real numbers. Zip cut 36% off its Atlassian licensing costs in year one and another 38% the year after, over a million USD saved across five years, largely by consolidating projects and switching off add-ons that native Enterprise functionality had already made redundant. Harrison AI avoided AUD 229k in costs over 24 months by consolidating onto Teamwork Collection Premium, a 4.4x return with breakeven inside six months. Neither of those started with a discount conversation. They started by working out what was actually included and unused.
This is exactly why we keep running events like the one we’ve got coming up in Sydney.
Why We Run These Sessions
Atlassian Service Collection: The Value You Haven’t Uncovered is coming up on 16 September at Atlassian’s Sydney office. Vincent Wong from Atlassian is building a Customer Service Management AI agent live from a blank canvas. Mark Edwards is walking through the Assets standard plan expansion and what it actually takes to get a working CMDB out of it.
None of that’s a sales pitch dressed up as content. It’s the practical stuff that determines whether a price increase like this one lands as fair or as a straight loss. Every attendee also gets a free Service Collection Readiness Check afterwards, a proper look at what’s switched on in your environment versus what’s sitting there unused, no obligation attached.
If Atlassian’s going to keep putting the price up every year, and every signal says they will, the only sensible response is making sure the value’s actually keeping pace. That’s the entire reason we put these sessions on for free. Turning up isn’t about loyalty to Elegance Group. It’s about not leaving money on the table in a licence you’re already paying for.
Register for the Sydney session here
Full details on the pricing changes, including the complete FAQ, are available directly from Atlassian here.
Recent Posts
Too Many Tools, Not Enough Value: How to Consolidate Without the Regret
Asana Goals and OKRs: What the Live Demo Actually Showed