The Atlassian price increase for 2026. Data Center is being priced toward Cloud.

Atlassian raised prices again for 2026, and the two increases are not comparable. Cloud rose like an annual uplift on public list prices. Data Center rose two to three times faster, on private renewal quotes, because the increase is meant to make staying uneconomic.

Atlassian now raises prices every year on two calendars: Data Center in February and Cloud in October. The Cloud uplift behaves like an ordinary annual rise on a public price list. The Data Center uplift shows up mostly in renewal quotes, and it is part of Atlassian's plan to move every customer to Cloud before end of life in 2029.

What changed in Atlassian pricing for 2026?

Two things changed. Jira, Confluence and Jira Service Management Data Center prices rose on February 17, 2026 PT for new purchases, renewals and upgrades. Cloud prices for Jira, Confluence, Jira Service Management, the Teamwork and Service Collections, Guard, Bitbucket and Jira Product Discovery rise on October 13, 2026 PT, again for new purchases and renewals alike.

Atlassian honors a quote generated before an effective date at the old price until that quote expires, and for most buyers that rule is worth more than the headline percentage.

Atlassian's FAQ pages for the 2026 steps give dates and products but no single percentage, so compare your quote line by line with last year's. Our analysis of Data Center price increases in 2026 follows the February steps in more detail.

Why are Atlassian Data Center prices rising faster than Cloud?

Because the Data Center increase is a migration tool, meant to make staying progressively uneconomic. In the renewals we benchmarked, Data Center quotes rose 15 to 30 percent year over year, while Cloud rose a typical 5 to 12 percent on published list prices.

Atlassian has been explicit that Cloud is the destination. New customers could no longer buy Data Center after March 30, 2026. Existing customers can buy new subscriptions, apps and expansions until March 30, 2028, and on March 28, 2029 Data Center products and their apps become read only. Our Data Center end of life guide covers each phase.

Why are Data Center quotes so hard to compare?

Cloud increases land on list prices that any buyer can see, compare and check against peers. Data Center increases land on renewal quotes, which are negotiated one customer at a time and are effectively private. The larger increase sits exactly where the buyer has the least reference data.

There is also a mechanical reason quotes outran list: many long standing customers held advantaged pricing below list. In February 2025 Atlassian raised advantaged Jira Software pricing by 30 percent across all tiers. Confluence and Jira Service Management advantaged prices had already been brought up to list in FY24, so those customers now take the full list rise each year.

What do the end of life dates mean for a renewal this year?

• Term length. On request, Atlassian and its partners can sell a Data Center term of up to 24 months, so a renewal signed in 2026 can carry you into 2028 at one agreed rate.
• Growth. Expansions stop on March 30, 2028. If you expect to cross a tier before migrating, buy that tier while you still can and price it now.
• Apps. Marketplace apps on Data Center expire with the platform in 2029. Set app terms to end at your planned migration date so you do not pay for months you will not use.

How do Atlassian user tiers turn a few extra users into a full price step?

Atlassian prices Data Center and annual Cloud subscriptions in user tiers, and you pay the tier price for your whole user base. The marginal user who pushes you over a boundary is the most expensive user you have. Deactivating a small number of dormant accounts can move the entire subscription down a tier.

In our benchmarks, roughly 1 in 4 customers sat within 10 percent of a tier boundary at renewal. For them a cleanup changed the tier for everyone. It is the cheapest saving available, and it stays invisible unless someone compares the count with the boundary before renewal.

A worked example at a tier boundary

Say you run Jira Data Center with 1,040 users holding application access. That puts you in the 2,000 user tier. Assume, for illustration only, that your renewal quote prices the 1,000 user tier at $60,000 and the 2,000 user tier at $110,000, and that you run three Marketplace apps that must follow the same tier.

Removing 45 accounts that have not logged in for six months cuts this renewal by $63,000, or 45 percent. Each removed account was worth about $1,400 a year, roughly ten times the $135 average per user on the original quote.

How do you check your own user count?

• Cloud counts. In Atlassian Administration, open Products, then User counts, and choose View for each product. Export users gives a CSV with last seen dates, and View usage shows unique users over 12 months.
• Pending invitations. The count includes people who were invited but never accepted. Revoke stale invitations before the renewal date.
• Threshold alerts. Turn on the 80 percent notification in the same screen so an approaching boundary shows up months ahead.
• Data Center counts. In Jira administration, Applications then Versions & licenses shows users against the licensed tier. Access comes from application access groups, so take leavers and dormant accounts out of those groups or deactivate them in the directory.
• Monthly Cloud plans. Since October 2025, monthly subscriptions bill the highest seat count reached during the month. Seats removed mid month still count, so clean up before the month starts.

Why must the cleanup happen before the quote is built?

Partners and Atlassian price a renewal from the user count they see when they build the quote. Once it exists at the higher tier, you are asking them to rework a document. On annual Cloud plans you cannot drop a tier mid term, so a missed cleanup costs a full year.

Do Atlassian Marketplace apps rise with the platform price?

Yes. Apps reprice against the same user tiers as the platform, so a platform increase multiplies through the app stack. On Data Center every Marketplace app must match or exceed the parent product's tier. On Cloud, Atlassian upgrades the app tier together with the product tier so the two always stay in step.

App spend is usually reviewed on its own cycle, if at all, so the compounded cost lands without anyone owning the total. Removing apps that duplicate features now built into the platform typically cuts 5 to 15 percent of app spend. Our marketplace app scaling analysis shows how user growth carries through each app.

Which cost reductions are available at an Atlassian renewal?

There are five, and they behave differently. Tier cleanup comes first because it is the only one where the saving is discontinuous. Every other item returns a percentage roughly in proportion to the effort you put in.

Why review edition fit every year?

The gaps between Standard, Premium and Enterprise widen with each cycle. In October 2024, for example, Atlassian raised Jira and Confluence Premium and Enterprise by 10 percent against 5 percent for Standard. An edition that fit two years ago may now cost more than the features your teams use.

Before each renewal, ask every product owner which Premium features they use. Our Premium and Enterprise comparison lists what each plan adds.

How should a Data Center customer price the renewal against Cloud?

Put three numbers on one page: the Data Center renewal, the Cloud equivalent and the cost of migrating. Reading the renewal quote and the migration case separately is what makes a large Data Center increase look unanswerable.

• Data Center renewal. Subscription at the new rate for your tier, every Marketplace app at the same tier, and the servers, database and admin time you carry to run it.
• Cloud equivalent. The edition and user tier you would need, the Cloud price of each app or its replacement, and any credits Atlassian offers against unused Data Center maintenance.
• Migration. Partner services, app replacement, testing, training and, for larger customers, a period of dual licensing while both platforms run.

Atlassian's incentives belong on the Cloud line: step up credits worth the prorated value of unused Data Center maintenance, and migration trials that last the rest of your Data Center term. Customers buying Cloud Enterprise by June 2027 may qualify for a first year discount of between 10 and 20 percent. Our Cloud migration guide covers the project.

How does a credible Cloud option help if you plan to stay?

It turns the renewal into a retention conversation. Once the account team believes you will migrate on your own schedule, with or without its incentives, it has a reason to hold the Data Center price. If you intend to stay for now, trade that commitment for a multi year Data Center rate that flattens the next two increases.

Should you migrate early just to escape the Data Center increases?

The advice customers hear most often is to move to Cloud as fast as possible. We disagree with it as a pricing decision. Cloud rises every October as well, and a rushed migration signed close to list gives up the one period in which you hold a real alternative.

The better course is to set a migration date that suits your projects, price Cloud against that date, and use the time before March 30, 2028 to negotiate both sides. A customer who can credibly stay two more years gets better Cloud terms than one who has already announced its migration.

A credible Cloud plan improves the Data Center quote whether or not you ever use it.

When should you sign to avoid the next Atlassian price increase?

Before the effective date, with a quote in hand. Atlassian honors any quote generated before October 13, 2026 PT at the old Cloud price until that quote expires. Annual subscriptions can renew early within 90 days of their expiry date, and monthly customers can lock the old price only by moving to an annual plan first.

With increases now annual and announced months ahead, timing is a recurring opportunity. Atlassian's fiscal year ends on June 30, and account teams often have the most room on price in the weeks before it.

What will the Atlassian account team say, and how should you answer?

• "The increase is a global list change, so we cannot discount it." The list change applies to list. Your renewal is a negotiated document, so ask for last year's rate held for the new term, or the uplift offset in the discount.
• "Data Center is ending, so there is little point negotiating it." You can buy and expand Data Center until March 30, 2028. Tell them you will set the migration date and want the renewal priced for the period you will use it.
• "Move to Cloud Enterprise now and we can offer a migration discount." Ask for the year two and year three prices in the same document. A first year discount that disappears at renewal only delays the increase.
• "The quote reflects your current user count." Send the cleaned export and ask for a requote at the lower tier before any price discussion starts.

Which contract terms should you ask Atlassian for?

• Price hold for the full term. Fixed annual rates on a multi year Cloud deal protect you from the next two October steps.
• Renewal uplift cap. A stated maximum increase at the next renewal stops the saving from being clawed back a year later.
• Tier reduction at renewal. The right to renew at a lower tier after a cleanup, without losing the discount you negotiated.
• One renewal date. Platform and Marketplace apps on the same date, so the app increase is priced in the same conversation.
• Written migration credits. The step up credit value and any dual licensing period stated in the order form, not in an email.

What have we seen in recent Atlassian renewals?

Across roughly 20 to 30 Atlassian renewals we benchmarked in 2024 and 2025, customers who treated announced increases as negotiable consistently beat those who budgeted them as fixed.

• Data Center outpaced Cloud. Renewal quotes rose 15 to 30 percent year over year against Cloud's 5 to 12 percent.
• Tier boundaries decided the bill. Roughly 1 in 4 customers sat within 10 percent of a boundary, where a small deactivation exercise avoided a full tier jump.
• Timing paid. Multi year Cloud agreements signed before an announced increase saved 10 to 20 percent against the post increase run rate.

The wider library, including tier tables and negotiation guidance, sits in the Atlassian practice.

What to do next

1. This week. If a Cloud renewal falls within 90 days, or you pay monthly, get a quote generated before October 13, 2026 PT.
2. Before any quote. Run the tier boundary check on every product.
3. Price three lines. Renewal, Cloud equivalent and migration, on one page.
4. Choose a term. If you are staying on Data Center, ask for a 24 month rate. If you are moving, ask for fixed multi year Cloud pricing.
5. Align apps and editions. Review both on the platform renewal cycle.
6. Negotiate from the full picture. Take the comparison into the renewal using our Atlassian negotiation guide, or ask the Atlassian practice to run the renewal with you.

Frequently asked questions