Jira Premium vs Enterprise pricing looks unanswerable below 801 users, because Atlassian's calculator won't show you an Enterprise number until you type 801. Set it to 350 users and the Enterprise column says "Enterprise plan pricing is available when you enter 801 or more users above", with a Contact sales button (it did on 30 October). But the same page carries Atlassian's whole price list as JSON, and that list prices Enterprise from 1 user up.
So I priced it. At 200 users Jira Enterprise is $52,000 a year against $34,500 for Premium. At 350 it's $86,500 against $57,000, and at 500 it's $102,000 against $67,000. Per seat per month that is $21.67 against $14.38, $20.60 against $13.57, and $17.00 against $11.17. Enterprise costs about one and a half times Premium. It's the same ratio at 801 users, where Atlassian does print the price.
I think most 200 to 500 seat companies that ask about Enterprise want one of four things: SSO through Guard, a second Jira site, faster support, or a bigger Rovo allowance before usage billing starts on 3 December. SSO and extra Rovo credits have list prices, and they cost less bought separately on top of Premium. Faster support has no price at all. A second site is more interesting, and it's the one case below where Enterprise comes out cheaper.
The prices below are Atlassian's own, read on 30 October 2026, after the 13 October increase. The assumptions sit near the end so you can swap in your own discount. Keep in mind that the Enterprise rows at 200 to 500 users are price list rows nobody offers you in public, and I couldn't confirm that Atlassian or a partner will quote at them. Treat them as the list price a quote would start from.
What we found: Enterprise is 1.5 times Premium below 801 users too
- Atlassian's Jira Enterprise annual plan in that price list is marked ACTIVE and has 84 user tiers. Eleven of them sit below 801 users, the lowest at $3,000 a year for up to 10 users. The calculator, the Enterprise offer in the page's own structured data (minimum 801 users) and the Cloud Pricing Tables page (Enterprise from 1,000 users) all leave them out.
- Enterprise is 1.51 to 1.52 times Premium at 200, 350, 500 and 801 users. The seat count doesn't change the ratio, so growing doesn't make Enterprise relatively cheaper inside this band.
- Of the priced things most buyers would use, Guard Standard is the biggest. Take it off and the gap per seat per month roughly halves, from $7.29 to $3.67 at 200 users.
- The extra Rovo credits and automation steps are worth $185 to $463 a month to the whole org, and only if you'd otherwise pay overage. They can't close the gap on their own at any size here.
- On our own test site, Rovo Chat logged 19 messages that cost 1,435 credits. Eleven cost 10 credits each and the other eight cost 65 to 310. Premium's 70 credits per user per month is seven short answers, or a fraction of one long multi-step one.
- Inside a tier the per-seat price swings a lot. Enterprise at 201 users is $29.23 per seat per month and $19.58 at 300, because both pay the $70,500 tier.
- With two Jira sites Enterprise can win. 350 people split across two Premium sites, with 50 of them on both, cost $97,100 a year with Guard Standard. Enterprise for the same 350 people is $86,500, so it's $10,600 cheaper.
Jira Premium vs Enterprise pricing at a glance (200, 350, 500 users)
All figures are Atlassian's annual list prices in US dollars, effective 13 October 2026, read from the price data on atlassian.com/software/jira/pricing on 30 October. No partner discount, no tax.
| Users | Premium per year | Enterprise per year | Premium per seat/month | Enterprise per seat/month | Gap per seat/month |
|---|---|---|---|---|---|
| 200 (tier 101-200) | $34,500 | $52,000 | $14.38 | $21.67 | $7.29 |
| 350 (tier 301-400) | $57,000 | $86,500 | $13.57 | $20.60 | $7.02 |
| 500 (tier 401-500) | $67,000 | $102,000 | $11.17 | $17.00 | $5.83 |
| 801 (tier 801-1,000) | $118,000 | $179,000 | $12.28 | $18.62 | $6.35 |
The 801 row is there as a check. It's the first size where the calculator prints an Enterprise price, and the calculator's $179,000 is exactly the price list row for 801-1,000 users. So the rows below it come from the same list the calculator reads. It just doesn't show them.
Enterprise has no monthly option. I found no monthly Enterprise plan in the list at all. If you compare against Premium on monthly billing instead, Premium costs $17.13 per seat at 200 users, $14.79 at 350 and $13.42 at 500 (Atlassian's calculator), so the gap narrows by $2.75, $1.22 and $2.25 a seat.
Watch the tier edges
Both plans are sold in user tiers on annual billing, so the price per seat moves a lot inside a band. At 201 users you pay for the 201-300 tier: $19.28 per seat per month on Premium and $29.23 on Enterprise, a gap of almost $10. At 300 users, same tier, it's $12.92 and $19.58. If you're sitting just above a tier line, the comparison looks worse than it will a year from now when you've grown into it. And at 201 users the cheaper Premium is actually the monthly one.
Premium's annual tiers aren't always cheaper than monthly. Monthly bills per user, so just above a tier line it can win. At 201 to 230 users Premium monthly costs less than Premium annual (at 201 it's $17.11 a seat against $19.28), and the same happens at 101 to 162, 301 to 308, 601 to 638 and 801 to 806. The calculator's "save up to 17%" is a ceiling. Enterprise has no monthly plan, so this only helps the Premium side.
Jira Enterprise minimum users: why the calculator starts at 801
There's no single page that says "the minimum is 801". The calculator implies it, and the Enterprise offer in the page's structured data has minValue: 801. Atlassian's Cloud Pricing Tables page goes further and starts its Enterprise table at 1,000 users, with $166,000 before 13 October and $179,000 after. The support article "What is an Enterprise plan?" says Enterprise plans "are aimed at large organizations and have a minimum user tier requirement", with no number, and that purchasing "is handled by our sales team".
Meanwhile the price list says something else. We pulled the plan rows out of the page HTML with a short script (no login, no API key, the JSON ships to every visitor):
The full Enterprise plan has 84 user tiers, from $3,000 a year for up to 10 users to $9,805,000 for 90,001 to 100,000, and 11 of them sit below 801. The picture shows the rows from 101 up.
Customers have been asking about this for years. A 2022 Community question, "Is there a minimum number of users for Enterprise accounts?", has 5,292 views; the asker noticed the same thing, that the calculators "start showing pricing if set to annual billing and at least 801 users". The answer there says there's no minimum, but it isn't from Atlassian staff. A 2025 thread (1,220 views) got the opposite answer and a pointer to sales. And the feature request CLOUD-11064, "Offer Atlassian cloud Enterprise plan subscriptions for user tiers below 1,000", had 349 votes and 279 watchers on 30 October, status Reviewing.
My reading: the price exists, the public door doesn't. If you're at 200 to 500 users and want Enterprise, you ask Atlassian or a partner for a quote and use the rows above as the list price that quote should start from. Has anyone reading this been quoted Jira Enterprise below 801? I'd like to know what number came back.
Jira Enterprise cost per user at 200, 350 and 500 users, once you subtract what it includes
To compare fairly, put Enterprise against Premium plus whatever you'd have to buy to get the same priced features. Atlassian publishes prices for three that nearly every buyer would use (sandboxes are a fourth, further down, and only count if you'd buy them).
Guard Standard. Enterprise includes it "at no extra cost". On Premium, SSO, SCIM and Active Directory sync show as "Requires Atlassian Guard Standard subscription". Guard Standard's annual list price is $8,700 at 200 users, $16,100 at 350 (tier 301-400) and $19,500 at 500. There's a catch in a footnote on Atlassian's support offerings page, written back when Guard was called Access: "We'll only charge for users not using Enterprise products in your Access bill." If your org has Confluence on Premium beside Jira Enterprise, those Confluence-only people are still billed for Guard.
Rovo credits. Jira Premium includes 70 credits per user per month, Enterprise 150. From 3 December, credits beyond the pooled allowance cost $0.01 each, and extra usage is on by default.
Automation steps. Premium gives 750 steps per user per month, Enterprise 1,000. Overage from 3 December is $0.50 per 1,000 steps.
| Users | Enterprise minus Premium, per year | Guard Standard value | Extra Rovo credits value | Extra automation value | Gap left, per year | Gap left, per seat/month |
|---|---|---|---|---|---|---|
| 200 | $17,500 | $8,700 | $1,920 | $300 | $6,580 | $2.74 |
| 350 | $29,500 | $16,100 | $3,360 | $525 | $9,515 | $2.27 |
| 500 | $35,000 | $19,500 | $4,800 | $750 | $9,950 | $1.66 |
How the two allowance columns are worked out: (150 − 70) credits × users × 12 months × $0.01, and (1,000 − 750) steps × users × 12 × $0.0005. Both are ceilings. They're only money you save if your org would otherwise blow past the Premium pool month after month, and unused credits and steps don't roll over.
So even if you need Guard and you'd use up the extra credits and steps, Enterprise still costs $6,580 to $9,950 a year more at these sizes. You're paying that for the rows with no price tag.
Which number goes in the budget? If you'd buy Guard Standard anyway, use the Premium plus Guard comparison: $8,800 a year more for Enterprise at 200 users ($3.67 a seat a month), $13,400 at 350 and $15,500 at 500. If you wouldn't buy Guard, the full list gap applies, $17,500 to $35,000 a year. The allowance columns only come off if you already expect overage.
I priced only Jira. If Confluence sits in the same organisation, Enterprise is a separate decision per app, and the Guard footnote below decides who still gets a Guard bill.
What changes on 3 December: Rovo credits and automation allowances, Premium vs Enterprise
The allowances are pooled across the org. At 200 users, Premium gives the pool 14,000 Rovo credits a month and Enterprise 30,000. At 500 users it's 35,000 against 75,000. A company with Jira and Confluence on the same plan gets both apps' allowances in one pool (we covered how the pool works in our 2027 usage-based pricing budget for 50, 200 and 500 seats, so I won't repeat it here).
Is 70 credits per person enough? It depends on what people do with Rovo. On our test site, Rovo Chat logged 19 messages between 8 September and 20 October, 1,435 credits in all. Eleven cost 10 credits each and the other eight cost 65 to 310. A Rovo agent called from an automation rule costs 10 credits a call, and a single "Think deeper" answer cost anywhere from 10 to 182 credits when we re-measured it after getting it wrong the first time. So Premium's allowance is seven short answers per person per month, or a fraction of one long multi-step one, and Enterprise's is fifteen short ones. In a pooled allowance light users cover heavy ones, and how many light users you have is the question. If you've rolled Rovo out to everyone and people use it daily, you'll probably run past the Premium pool. Past that point both plans charge $0.01 a credit. So the most Enterprise can save you is the 80 extra credits per user per month.
I think automation is smaller money than it looks. At 200 users the Enterprise pool has 50,000 more steps a month than Premium. A scheduled rule that runs every five minutes and matches nothing still uses one step per run, which is 8,640 steps a month (we counted steps rule by rule). So the Enterprise bonus covers about six forgotten rules like that, and if you paid for them as overage instead it would be $25 a month.
A small oddity. The FAQ on Atlassian's own Jira pricing page still says Enterprise comes with "unlimited automation" and "the inclusion of Atlassian Access". The compare table on the same page and the automation documentation both say 1,000 steps per user per month, and Access has been called Guard for a while now. I'd budget on 1,000.
Jira Enterprise features Premium does not have
These are the rows that differ between the two columns on Atlassian's compare table, plus what the support and SLA pages add. Data residency, IP allowlisting, release tracks and admin insights are on both plans, so they don't belong in this decision even though some partner pages list them under Enterprise. Sandboxes are on both too, one free against five.
| Feature | Premium | Enterprise | Has a list price? |
|---|---|---|---|
| Sites | 1 | Up to 150 | No, but a second Premium site is a second subscription |
| Critical-issue response | 1 hour, cloud support team, no phone | 30 minutes, dedicated senior team, phone number | No |
| Uptime SLA | 99.9% | 99.95% | No (service credits only) |
| Free sandboxes per app | 1 | 5 | Extra ones $10,000 each, per app |
| Atlassian Data Lake, data catalog and lineage | No | Yes | No |
| Multiple identity providers | No | Yes | No |
| Audit logs of user activity | No | Yes | No |
| Custom Jira templates | No | Yes | No |
| Centralized user subscriptions, user counts, app requests | No | Yes | No |
| Guard Standard | Bought separately | Included | Yes (in the table above) |
Multiple sites is where Enterprise can pay for itself
On Premium, each Jira site is its own subscription. Two Premium sites of 100 users each cost 2 × $19,500 = $39,000 a year, against $34,500 for one site of 200 (my reading of how separate subscriptions are tiered, using the 51-100 row of the same price list). As I read it, anyone with access to both sites counts on both bills. Enterprise covers "up to 150 instances of an Atlassian app without paying extra for those instances", so a company that has to keep a separate site per region, per client or per regulated unit stops paying per site. A partner in a 2022 Community thread on when to move to Enterprise (4,463 views) put it as predictable pricing: "you know what it's going to cost no matter how many new sites the team spins up". Of all the arguments here, it's the one I'd take seriously at 200 to 500 users. The worked case below shows why.
A worked case: 350 people on two Jira sites
Say you run one site for the product teams (200 people) and a separate one for a regulated unit (150 people), and you want SSO. On Premium that's two subscriptions. 200 users is the 101-200 tier at $34,500, and 150 users is the same tier, another $34,500. Guard Standard bills people in your organisation, so 350 users is $16,100. Total: $85,100 a year.
Enterprise for 350 users is $86,500 with Guard included and one subscription covering both sites. The difference is $1,400 a year, about 33 cents per seat per month, and you also get the 30-minute support, the bigger allowances and the rest of the table.
Now put 50 people on both sites, which happens a lot (managers, admins, the security team). On Premium the first site becomes 250 users, the 201-300 tier at $46,500, and the second stays at $34,500. With Guard that's $97,100. Enterprise still counts 350 people. Atlassian's Enterprise doc says "you only pay once for each user, no matter how many instances of the Atlassian app they have access to", so it stays at $86,500 and comes out $10,600 a year cheaper. Atlassian doesn't spell out the Premium side. My reading is that two Premium sites are two subscriptions and a person on both is billed twice, and it's the first thing I'd ask a partner to confirm in writing.
The 99.95% SLA adds a 5% credit, about $217 for a bad month at 200 users
Enterprise adds a service credit of 5% of the monthly fee when uptime falls between 99.9% and 99.95%. At 200 users that's 5% of $52,000 ÷ 12, about $217, for a 30-day month in which Jira was down between 22 and 43 minutes. Below 99.9% both plans pay the same 10%, 25% and 50% credits. I wouldn't buy Enterprise for the SLA credit. During an outage you care about the 30-minute response, and the credit is something you have to claim within 15 days of the month's end.
Sandboxes, only if you'd buy them anyway
Enterprise includes five free sandboxes per app, Premium one. Extra sandboxes cost "$10,000 per sandbox, per app" and need annual billing. If your change process really needs four more Jira sandboxes, that's $40,000 of value and Enterprise comes out cheaper. Atlassian's page doesn't say whether the $10,000 is per year or one-off, and I'd ask before putting it in a business case.
What to ask before you sign an Enterprise quote
If you do go to sales, these are the questions I'd want answered in writing next to the quote, because each one moves the comparison above.
Start with how users are counted. Ask whether someone on two of your sites counts once or twice. The whole two-site case hangs on it.
Then ask which price row the quote starts from. Bring the catalogue figures: $52,000 at 200 users, $86,500 at 350, $102,000 at 500. If the quote is higher, ask why.
Ask about Guard for people outside Enterprise. Atlassian's footnote says it only charges for "users not using Enterprise products" (the footnote still calls Guard by its old name, Access). If Confluence stays on Premium, those people are still on a Guard invoice.
Ask about your Marketplace apps. Enterprise "requires a switch to annual subscriptions for the Atlassian apps and all Marketplace apps", and their cost is not in the Enterprise price. A monthly app bill that turns annual is a cash-flow change even if the total stays the same.
Ask what happens to the Premium months you've already paid. Atlassian says it will credit the unused term toward Enterprise. Get the credit amount on the quote.
And ask whether the $10,000 extra sandbox is a year or forever. I couldn't find it written down.
None of this needs a partner, but a partner who has done a few Enterprise quotes will know the answers without asking.
These are list prices: what would change them
- Atlassian list prices in USD from the price data on atlassian.com/software/jira/pricing (Jira) and atlassian.com/software/guard/pricing (Guard), effective 13 October 2026, read 30 October 2026. Plan strings: "Jira, Premium, Annual (USD, Default, 13-10-2026)" and "Jira, Enterprise, Annual (USD, Default, 13-10-2026)".
- Annual billing for both plans, since Enterprise is annual only. No partner or volume discount. Enterprise is sold through sales, so a real quote may differ, and nothing I found confirms a quote at the sub-801 rows.
- Guard Standard counted for the same number of users as Jira. If your org has more users than Jira users, Guard costs more on Premium.
- Rovo and automation allowance values assume your org would pay overage for all the extra credits and steps. If you stay inside the Premium pool, those columns are $0 and the gap is bigger. Rates from 3 December 2026: $0.01 per Rovo credit, $0.50 per 1,000 automation steps.
- Moving from Premium mid-term: Atlassian says it "will credit the value of the unused maintenance term toward the Cloud Enterprise purchase". Enterprise also needs all your Marketplace apps on annual billing, and their costs aren't included. A quote dated before 13 October is honoured at the old prices until it expires. Premium went from $32,000 to $34,500 at 200 users (+7.8%), and Enterprise from $166,000 to $179,000 at 1,000 (+7.8%).
Should a 200-500 user company move from Premium to Enterprise?
At 200 to 500 users, stay on Premium unless one of these is true. You need more than one Jira site, or soon will. You need a phone line and a 30-minute response when Jira is down. Your security team insists on multiple identity providers, Data Lake or user activity audit logs. If you need none of that and want SSO, I'd add Guard Standard to Premium. You'll pay $3.67 a seat a month less than Enterprise at 200 users and $2.58 less at 500.
If one of them does apply, ask for a quote and bring the price list rows with you. $52,000 at 200 users, $86,500 at 350 and $102,000 at 500 are what Atlassian's own catalogue says, and a quote above them is worth questioning.
Whatever you pick, set an extra usage limit for Rovo credits in Atlassian Administration before 3 December, because it's on by default and neither plan caps it for you.
Did you get a Jira Enterprise quote under 801 users, or get told no? And if you moved from Premium, which of the unpriced rows actually decided it for you? Tell me in the comments. I'm especially curious whether anyone went to Enterprise for the sites alone.
Originally published on leanzero.net. More Atlassian, Forge and local-AI write-ups at leanzero.net/blog, and if you're planning a migration or a Forge app, that's what we do: leanzero.net/services.
Top comments (0)