Atlassian Pricing Updates - Fall 2026 - What to Know, What to Do

On August 28, 2026, Atlassian announced Cloud list price updates affecting new purchases, renewals, and upgrades, effective October 13, 2026. On September 1, they announced something separate: usage-based pricing across five metered capabilities, with billing starting December 3, 2026.

Note: As an Atlassian Partner, Sketch offers free licensing services. If these pricing changes are putting you in a budgetary bind, please reach out, and we’ll see if we can help.

The price update reflects a year of real investment. Agents that complete work instead of just answering questions. The Teamwork Graph connecting context across every app your teams touch. Enterprise-grade security built into every layer. The platform you're renewing isn't the same platform you bought last year. All of Atlassian’s updates over the year can be viewed here.

The short version of both announcements

The first change raises what you pay per seat. The second adds a second thing you pay for. They are independent of each other, and you can be affected by both.

Change 1: Atlassian cloud pricing changes October 13

Effective October 13, 2026 PT, Atlassian is raising list prices across the Cloud portfolio.

Comparing Atlassian’s published current and future pricing tables, the increases work out to approximately:

Ranges appear where the increase varies by user tier.

How the timing actually works

This is the part worth reading twice, because it determines whether you pay the old price or the new one.

• Existing monthly subscriptions: any bill dated on or after October 13 uses new pricing.

• Existing annual subscriptions: any quote generated or modified on or after October 13 uses new pricing.

• Auto-renewing annual subscriptions: any bill on or after October 13 uses new pricing. Your card on file gets charged at the new rate.

• Open quotes created before October 13: honored at the old price until the quote’s stated expiration date.

• New purchases on or after October 13: new pricing.

• Tier upgrades or plan upgrades on or after October 13: new pricing. Upgrade before October 13 and you stay on existing pricing.

Two constraints on acting early:

1. You can only renew early inside your 90-day renewal window. Atlassian or your partner sends a renewal quote 90 days before an annual subscription expires (unless you already have an open quote for another product on the same site). You cannot purchase a renewal outside that window. If your renewal is in March, the “lock in the old price now” is not available to you.
2. Monthly customers have a different door. If you’re on a monthly plan, you can’t renew early, but you can request an annual quote any time before October 13 and get existing pricing. Payment has to land before that quote expires. Moving monthly to annual can also carry a discount depending on seat count.

Change 2: Usage-based pricing starts billing December 3

Your seat-based subscription doesn’t change. Usage-based pricing adds a consumption layer on top of it for five metered capabilities:

Four mechanics that decide your bill

1. Allowances are pooled at the org level, not per user or per app. All your subscriptions contribute to one shared pool per meter. Everyone draws from the same bucket. One team running heavy automation consumes allowance that another team was counting on.
2. Allowances refresh monthly and don’t roll over. This holds even on annual plans — annual customers get a fresh monthly allowance, not a lump-sum yearly one. Unused capacity is gone at the end of each month.
3. Check your extra usage setting: Allowances are calibrated against real usage patterns, and Atlassian expects most customers won't exceed them. Even so, take thirty seconds in Atlassian Administration to see how your organization is configured. Your extra usage setting decides what happens if you do go past an allowance: consumption either continues and gets billed at published rates, or that meter pauses until the allowance refreshes (disabling extra usage).
4. Automation is metered per step. Every action, condition, branch, or loop counts individually. A flow with one trigger, one condition, and two actions is four steps. If you’ve built dense multi-branch automation, your measured consumption will look very different from what the number of flows suggests. Every plan carries a defined monthly Automation allowance.

Related reading:

Set up Jira to Confluence automation the smart way

Set up Jira work routing automation

What to do

If you have any questions or want a second set of eyes, our team of experts will help you review your licensing:

1. Deactivate inactive users. Users who aren’t using the product still count toward your bill. On monthly plans this reduces your next bill directly. On annual it lowers what you renew at rather than what you’re paying now, which makes doing it well before your renewal date the point. If you haven’t audited this in a year, there’s almost certainly something there.
2. Check where you sit in your pricing tier. Annual Cloud pricing is fixed-tier, not per-user. An org with 480 Jira Standard users bills at the 500-user tier. If you’re at 480, you have 20 seats of headroom you’ve already paid for. If you’re at 505, you’ve just crossed into the 600 tier, and the same logic applies in reverse when you deactivate users. Know which side of a tier boundary you’re on before your renewal, not after.
3. Look at your extra usage settings. Atlassian Administration → Billing, or Insights → Platform usage. Decide deliberately whether you want extra usage on. Changes take effect immediately, and will be turned on by default. This is the single highest-value thing on this list.
4. Baseline your consumption ASAP. The Platform usage dashboard shows up to 90 days of history plus forecasting, and you can export to CSV. Pull your Rovo, Automation, and Assets numbers now, while there’s no invoice attached. If your automation is step-heavy, this is where you’ll find out.
5. Look at plan structure. With real numbers in hand, some structural options may or may not make sense: consolidating multiple Standard or Premium subscriptions of the same product into one Enterprise subscription; consolidating Jira, Confluence, Guard, and Loom onto Teamwork Collection if seat counts are similar; moving monthly to annual. Atlassian lists all of these as ways to reduce a bill, and higher tiers and Collections do carry larger allowances. Whether that math works for you depends entirely on step 4. Run the numbers before you run the change.

At Sketch, we help you get real results from Atlassian without paying enterprise prices. A big part of that is free Atlassian license management without surprises. There's a lot of detail that goes into these two changes coming this fall. If you have any questions or want a second set of eyes, we’ll help you review your licensing.

As always, it’s no charge. Just contact us and we’ll see what we can do.

Sources:

Atlassian’s announcement regarding the annual price increase

Atlassian’s announcement regarding usage based billing