Jira Cloud Premium lists at 14.54 dollars per user per month, Enterprise is custom and annual only, and the loyalty discount does not survive renewal unless you write it down. A 3,200 seat estate cuts year one cost by roughly 40 percent in our benchmark scenario.
Prepared by Redress Compliance · June 2026 · Representative Atlassian estate scenario (benchmark scenario, not a quote)
Atlassian sets the price reference, the billing unit, and the migration calendar. The published Cloud rate is per user per month: Standard at 7.91 dollars, Premium at 14.54 dollars, Enterprise custom and annual. Most buyers anchor on the per user list and miss the two levers that move the number most.
The first buyer side move is to bill on active users, not provisioned seats. In our benchmark estate a provisioned count of 3,200 users falls to 2,450 active users once dormant and duplicate accounts are removed. At Premium list that single step takes annual cost from 558,336 dollars to 427,476 dollars before any discount.
The second move is to choose the tier you consume. Enterprise carries a 99.95 percent SLA, up to 150 instances, BYOK, and bundled Atlassian Access, but those features only pay back above a real multi site governance threshold. Below it, Premium plus Access delivers the same control at roughly half the per user cost.
The trap is the renewal. The loyalty discount and the volume band are anchored to the order, not the relationship. Without a renewal floor and an uplift cap, year three cost in our scenario reaches 487,569 dollars instead of 367,608 dollars.
This paper gives the tier map, the baseline method, the volume breakpoints, the migration credits, the five clauses, and the BATNA you bring to the table.
Server end of life moved Atlassian from a one time perpetual license business to a recurring Cloud and Data Center subscription business, and that shift is the reason every renewal now sits on the vendor calendar. Atlassian ended Server support in February 2024, stopped new Server sales years earlier, and pushes every remaining estate toward Cloud or Data Center.
The commercial consequence is direct. A perpetual Server license was a sunk cost with a small annual maintenance line. Cloud is a per user subscription that recurs in full every year and rises with published price increases. Atlassian now controls the timing, the unit, and the reference price on every contract.
Data Center remains for now, but it carries its own clock. New buyers face an end of sale change, and the platform reaches full end of life on March 28, 2029, when products and apps become read only. The closer you sit to those dates, the less time you have to run a competitive process.
Contract mechanic worth knowing. Atlassian bills Cloud annual plans on a user tier, defined as the maximum number of people who can be invited to the app, not the number who log in. A provisioned seat that never signs in still counts toward the tier you pay for. That single rule is why baseline hygiene beats discount chasing.
Buy the tier you consume, not the tier the SLA marketing points you to. Standard fits single team estates, Premium fits most mid market and lower enterprise estates that need governance and analytics, and Enterprise pays back only above a real multi site, data residency, or BYOK threshold.
The published per user gap between Standard and Premium is large, and Enterprise adds a custom premium on top. The table sets out where each tier earns its price.
| Capability | Standard | Premium | Enterprise |
|---|---|---|---|
| List price per user per month | 7.91 dollars | 14.54 dollars | Custom, annual only |
| Uptime SLA | None | 99.9 percent | 99.95 percent |
| Instances or sites | 1 | 1 | Up to 150 |
| Data residency | Limited | Yes | Yes, plus BYOK |
| Atlassian Access and SSO | Add on | Add on | Included |
| Support | Standard | 24/7 Premium | Dedicated Enterprise |
Published Cloud list per user per month. Enterprise band is an indicative negotiated range at multi thousand seat scale, not a quote.
The standard reseller pitch is to move to Enterprise for the SLA and the AI features. We disagree for most estates. Below roughly 1,000 active users on a single production site, Premium plus Atlassian Access delivers about 95 percent of the governance at close to half the per user cost.
Enterprise earns its premium only when you run multiple sites, need BYOK or specific data residency, or require the 99.95 percent SLA in writing. Buy the SLA you can use, not the badge.
Atlassian Cloud pricing steps down at user count breakpoints, and Enterprise discounts deepen as the committed tier rises. The breakpoints matter because billing rounds up to the tier ceiling, so a count just over a threshold pays the full higher tier.
Use the breakpoints as negotiation anchors. If your active count lands just above a tier line, that is the strongest case for either trimming back under the line or pushing the next band discount. The indicative bands below come from our engagement file.
| Active user band | Typical posture | Indicative discount vs list |
|---|---|---|
| 100 to 250 | Standard or Premium, list | 0 to 5 percent |
| 251 to 800 | Premium, modest volume | 5 to 12 percent |
| 801 to 1,000 | Premium to Enterprise threshold | 12 to 18 percent |
| 1,001 to 5,000 | Enterprise, loyalty eligible | 18 to 30 percent |
| 5,000 and above | Enterprise, strategic | 28 to 40 percent |
Median provisioned seats that never logged in over a trailing 90 days, across the Atlassian estates we benchmarked.
Indicative discount range off list for estates between 1,001 and 5,000 active users on an annual Enterprise commitment.
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025.
Take a representative estate of 3,200 provisioned Jira and Confluence users. A trailing 90 day login audit removes 750 dormant and duplicate accounts, leaving 2,450 active. We then apply a 22 percent volume band for the 1,001 to 5,000 tier. The waterfall below is internally consistent at Premium list of 174.48 dollars per user per year.
| Step | Users | Annual cost |
|---|---|---|
| Provisioned at Premium list | 3,200 | 558,336 dollars |
| After active baseline rationalization | 2,450 | 427,476 dollars |
| After 22 percent volume band | 2,450 | 333,431 dollars |
| Year one realized vs provisioned list | 40 percent lower |
Benchmark scenario, not a quote. Premium list 174.48 dollars per user per year.
The migration credits stack, and they are time bound to your current on premises term. Treat them as three separate levers, not one. Each is anchored to the migration order, so the date you sign sets what you can claim.
Contract mechanic worth knowing. The Cloud Migration Trial runs free only for the remaining term of the equivalent paid Data Center license. If your Data Center renewal is six months out, you get roughly six months of free parallel Cloud. Time the migration order against your Data Center co terminus, not the vendor quarter.
Sequence the credits so they overlap rather than expire one at a time. Sign the Cloud order while your Data Center term still has runway, claim the trial against that runway, and use dual licensing to cover the cutover. The loyalty or Ascend discount then sets the price floor on the paid Cloud term that follows.
The discount you win at migration is not durable. Atlassian prices the relationship at the order, and the volume band and loyalty discount can lapse at renewal unless the contract holds them. Five clauses turn a one time discount into a multi year price.
The cost of skipping these clauses is the renewal drift. In our scenario the capped path rises 5 percent a year from the 333,431 dollar year one floor. The uncapped path loses most of the volume discount and absorbs a 9 percent list rise, so year three reaches 487,569 dollars instead of 367,608 dollars.
| Year | Capped path, 5 percent cap and floor held | Uncapped path, discount lapses and 9 percent list rise |
|---|---|---|
| Year 1 | 333,431 dollars | 333,431 dollars |
| Year 2 | 350,103 dollars | 447,311 dollars |
| Year 3 | 367,608 dollars | 487,569 dollars |
| Three year total | 1,051,142 dollars | 1,268,311 dollars |
Benchmark scenario, not a quote. Both paths start at the 333,431 dollar year one floor.
Your best alternative is the strongest lever you have, and Atlassian knows whether you have built one. A credible alternative on the table changes the discount conversation more than any volume argument. Four alternatives map to the Atlassian stack.
| Alternative | Replaces | Where it bites |
|---|---|---|
| GitHub Issues and Projects | Jira for software teams | Teams already on GitHub for source and CI can consolidate planning. |
| Linear | Jira for product and engineering | Lighter, faster issue tracking for modern product orgs. |
| ServiceNow ITSM | Jira Service Management | Enterprises with a ServiceNow footprint can absorb IT service desk. |
| Monday.com | Jira for business and ops teams | Non engineering work management at a lower governance bar. |
You do not need to migrate to use a BATNA. You need a costed, scoped alternative quote and an internal sponsor willing to pilot it. The point is to make the alternative real enough that Atlassian prices against losing the account, not against your renewal inertia.
Run the play in three phases over roughly 16 weeks, starting well before your renewal or migration deadline. The earlier you start, the more credible your BATNA and the more runway you have for the migration trial.
Pull trailing 90 day login telemetry, remove dormant and duplicate accounts, map current editions to Cloud tiers, and fix the active user count you will bill on.
Select the tier you consume, target the volume band for your active count, line up dual licensing and the migration trial, and obtain a costed BATNA quote.
Negotiate the renewal floor, uplift cap, tier hold, co terminus, and true down right, then sign against your Data Center co terminus, not the vendor quarter.
Recommendation: bill on active users, buy the tier you consume, and write the discount into the renewal.
We sit on the buyer side of the table for Atlassian renewals and migrations, from baseline audit through signed order. We are glad to tie a meaningful part of the fee to delivered value.