Atlassian Data Center pricing.

01 Key findings

1. Pricing steps, it does not scale. Data Center is an annual subscription set by user-tier bands. You pay the band that covers your count regardless of where in it you sit, and crossing into the next band at renewal steps the price up.

2. The band boundary is the lever. Two estates at 480 and 520 users can pay materially different amounts. Reclaiming inactive accounts to drop under a boundary can save an entire band step — a direct cost lever, not just hygiene.

3. JSM breaks the user-band model. Jira Service Management is priced per agent, not per user. Agent counts are far smaller than the user population, so JSM is often inexpensive even for a large organisation.

4. Hosting is the invisible half of the bill. Servers, database, storage, high availability, and the staff to run the cluster never appear on the Atlassian invoice but are real and recurring. A fair Data Center total includes them.

5. Server is dead; Data Center is not. Atlassian ended Server sales and support and steers investment toward Cloud, but Data Center remains the supported self-managed option. The real decision is Data Center versus Cloud.

02 How the band model works

Data Center is the self-managed, enterprise-grade deployment option, run on infrastructure the customer controls, whether on-premises or in the customer's own cloud account. It is licensed as an annual subscription, not a perpetual license, and the price is set by user-tier bands. You buy the band that covers your user count and pay the band price regardless of where in the band your actual count sits.

This banded structure is the single most important feature of Data Center pricing. Two organizations with 480 and 520 users can pay quite different amounts because the second has crossed a band boundary. User count management therefore matters not just for the total but for which band you land in, and a small reduction that drops you under a boundary can save a full band step.

03 Tier band pricing

Each Data Center product carries its own banded price list. The figures below are indicative 2026 annual list pricing for the core products at common user bands. Actual figures vary with the price list in effect and any negotiated discount, so treat these as the shape of the structure rather than a quote.

Jira Service Management is the exception to the user-band model: it is priced per agent, the staff who resolve requests, rather than per user, much as other service-desk tools price per fulfiller. Because the agent count is usually far smaller than the total user population, JSM can be comparatively inexpensive for a large organization with a small service-desk team. Mixing the per-user and per-agent models correctly is part of pricing a combined Atlassian estate.

04 Cost at scale

The band model means cost does not rise in a straight line with users — it jumps at each boundary. Jira Software Data Center list price across the common bands shows how steeply the subscription climbs as the estate grows:

The figure that matters for a budget or a Cloud comparison is the fully loaded one: the subscription band plus the clustered infrastructure plus the staff time. Data Center is built for high availability and scale through clustering — multiple application nodes, a shared database, a shared file system, and often a load balancer and a separate search index, each provisioned, monitored, and maintained. The subscription band buys the right to run that architecture; the architecture itself is the customer's cost.

05 The EOL & renewal traps

Two recurring traps catch Data Center buyers off guard. The first is the trajectory question — whether Data Center follows Server into end-of-sale. The second is the renewal uplift that quietly compounds the band price across every term.

06 Apps & hosting cost

The product subscriptions are only part of the Data Center bill. Marketplace apps are licensed to the same user tier as the product they extend, so a heavily extended Jira estate carries an app cost that can rival the core subscription. Apps follow the same banded structure, which means crossing a user band can step up both the product and every app at once.

Hosting and administration are the other side of Data Center economics. Because it runs on infrastructure you provide, the true cost includes servers or cloud compute, database, storage, the staff to patch and maintain the cluster, and the high-availability setup Data Center is designed for. These costs do not appear on the Atlassian invoice but are real, and they are exactly the costs a Cloud migration is pitched as removing.

07 Stay vs migrate

The live question for most Atlassian customers is whether to stay on Data Center or move to Cloud. Weight these four factors to your situation before committing either way.

08 Negotiation levers

Data Center pricing is more negotiable than the published band list suggests, especially at the larger tiers and at renewal. Atlassian discounts off list for multi-year commitments and larger bands, and a buyer who arrives with an accurate, reclaimed user count and a credible view of the Cloud alternative negotiates from a stronger position than one who accepts the band renewal.

The strongest Data Center renewals combine a reclaimed user count, a rationalized app list, and a written uplift cap, secured before the renewal date rather than negotiated under its deadline. Start the band and renewal work at least three to six months out, because reclaiming inactive users, rationalizing apps, and confirming the band the estate truly needs all take time to do properly.

09 Our recommendation