Jira Service Management pricing and cost per agent: the real tier ladder, plan by plan

The advertised $20 and $51.42 are averages for 75 agents, not prices

This is the single most repeated error about Jira Service Management pricing, and it is repeated by almost everyone who writes about it. The plan cards show Standard at $20 per agent a month and Premium at $51.42. Neither number appears anywhere in Atlassian's rate card, because neither is a rate. They are what you get when you apply the graduated ladder to a team of exactly 75 agents, which is where the pricing slider sits when the page loads.

Landing on both advertised figures to four decimal places is not a coincidence, and it tells you what the number means. It is an honest average for a 75-person service desk. It is a misleading one for everybody else, because the ladder only ever goes down. A team of 10 pays $25.00 an agent on Standard, a quarter more than the sticker. A team of 10 on Premium pays $57.30, about 11 percent more than the sticker. The advertised price is the floor of what you might pay, and you reach it only by hiring 75 agents.

The knock-on effect shows up in almost every third-party cost estimate. Multiplying a 25-agent team by $51.42 gives $15,426 a year for Premium, and that figure circulates widely. Atlassian's own ladder says a 25-agent Premium team pays $1,359 a month, which is $16,308 a year on monthly billing, or $13,600 on an annual contract. The commonly quoted number is neither of those. It is the wrong answer to both questions.

Annual billing can cost 56% more than monthly, not 17% less

The pricing page carries a badge reading "SAVE UP TO 17%" next to the annual toggle. The words "up to" are doing a great deal of work. Monthly billing is priced per agent, but an annual contract is priced per agent tier, as a single flat amount for the whole band. A team of 51 and a team of 100 pay the identical $19,700 for Standard. So the annual discount is real if you sit near the top of a tier, and it inverts into a penalty if you sit near the bottom of one.

Every row above is a team that would pay more by signing an annual contract. The worst case in the table is a 51-agent service desk, which pays $19,700 a year on the annual plan against $12,600 on monthly billing, a difference of $7,100. The saving only appears once you approach a tier ceiling: at 100 agents that same $19,700 annual contract beats $23,625 of monthly billing, a genuine saving of 16.6 percent.

There is a neat irony in the 75-agent case. That is the headcount Atlassian uses to advertise $20 and $51.42, and it is also a tier floor's near neighbour: at 75 agents an annual Standard contract costs $19,700 against $18,000 of monthly billing, so annual is 9.4 percent more expensive, and Premium at 75 agents is 10.2 percent more expensive. The team size in the advert is a team size where the advertised discount does not exist.

The practical rule is short. Work out where you sit inside your tier before you choose a term. If you have just crossed a boundary, stay on monthly billing until you grow into the tier you are already paying for.

A status page needs the Enterprise plan, which starts at $2,500 a year

"Create branded, real-time public and private status pages" appears exactly once in Atlassian's plan cards, and it sits under Enterprise. Standard and Premium customers do not get one at any team size. For a three-agent team that wants a status page and nothing else from the top tier, the entry price is $2,500 a year; at 25 agents it is $20,500.

This is worth flagging for anyone arriving from Opsgenie, because it is a step backwards. Opsgenie put service status pages on Essentials, its cheapest paid tier at $9.45 per user a month, which was more generous than most of this market. The migration Atlassian recommends moves that same capability to its most expensive tier. If a status page is the reason you are looking at Enterprise, price it as a separate purchase before you commit, and read the Opsgenie pricing and shutdown breakdown alongside this one.

The alternative most teams settle on is to keep the service desk for tickets and buy the status page from whoever also runs the checks behind it, so the page updates from real probe data instead of from somebody remembering to post an update. Our status page software comparison lays out what that costs across the market.

Where these numbers come from, and one trap we nearly fell into

The pricing page ships Atlassian's commerce catalogue as embedded JSON. Each plan carries a SKU, a billing cycle and an array of tiers with a floor, a ceiling and an amount in cents. Reading that array is more reliable than reading the rendered cards, because the cards show one blended figure for whatever the slider happens to be set to.

The trap: the catalogue carries two ladders for every plan, and they differ by a constant factor of about 1.367. They are not monthly and annual, and they are not two products. The description field next to each one settles it. One is labelled "USD, Default" and the other "JPY COMMERCIAL CLOUD". Reading the larger set as dollars would have published Standard at $34.20 and Premium at $78.30, which is wrong by a third. Only the USD list is used here, and it confirms that Atlassian serves country-specific price lists, as Uptrends, UptimeRobot and Site24x7 do.

One thing this page does not do is price a Data Center licence, Marketplace apps, partner implementation or Atlassian Guard Premium, none of which are on the page this data came from. Where a figure is not published, it is not guessed at here.