Jira Service Management Status Page Pricing and Cost

A Jira Service Management status page requires the Enterprise plan. There is no status page on Free, Standard or Premium at any team size. Enterprise is sold on annual billing only and starts at $2,500 a year for 1 to 3 agents, $8,500 for 6 to 10, $13,000 for 11 to 15 and $20,500 for 16 to 25. Measured against the Standard tier the same team would otherwise buy, that puts the status page surcharge at $1,750 a year for three agents and $14,850 a year for twenty five. Atlassian's own plan cards mention branded public and private status pages exactly once, and the mention sits under Enterprise.

This catches people out for a specific reason. Opsgenie, the product Atlassian is currently migrating customers away from, put service status pages on Essentials at $9.45 per user per month, which was one of the more generous arrangements in this market. The recommended destination moves that same capability to the most expensive tier Atlassian sells. If a status page was part of why you bought the old product, the migration is not a lateral move.

Every figure below was read on 8 September 2026 from the commerce catalogue embedded in Atlassian's Jira Service Management pricing page, in USD. The full ladder for all four plans, including why the advertised $20 per agent is really a blended average for a team of 75, is in our Jira Service Management pricing breakdown.

Does Jira Service Management include a status page?

Only on Enterprise. The phrase in Atlassian's plan card is "Create branded, real-time public and private status pages to keep customers informed", and it appears in the Enterprise feature list alongside Atlassian Analytics, advanced admin controls and multi-site support. Standard and Premium customers do not get a cut-down version or a subscriber-limited one. They get nothing.

That is unusual for the price. Premium at $57.30 per agent per month for the first 15 agents already buys advanced AIOps, a virtual service agent, real-time incident monitoring and change management. A team paying $8,600 a year for fifteen Premium agents still has no way to tell customers that something is broken, which is the one thing an outage actually requires you to do.

How much does a Jira Service Management status page cost?

The honest way to price it is as the difference between Enterprise and the tier you would have bought otherwise, because nobody buys Enterprise purely for the status page feature. Here is that gap at the agent tiers most teams sit in.

Annual contract prices, USD. Annual billing on this product is a flat amount for the whole agent tier rather than a per-agent rate, so a team of 51 and a team of 100 both pay $76,500 on Enterprise.

Enterprise runs about 3.3x Standard at three agents and 3.9x at a hundred, so the multiple grows rather than shrinking as you scale. Against Premium the gap is narrower, $6,900 a year at 25 agents, which is the comparison worth making if you were heading for Premium anyway for the AIOps and change management.

Why is the status page only on the Enterprise plan?

Atlassian has never really treated the status page as a service desk feature. It sells a separate product, Statuspage, which has its own four-tier price list running from $29 to $1,499 a month and meters you on subscribers rather than agents. Bundling a full status page into Standard or Premium would undercut that product directly. Putting it on Enterprise, where the buyer is already committed and price sensitivity is lowest, protects the standalone list.

Worth being clear about one thing, because it trips people up on procurement calls: a Jira licence has never included Statuspage, and the status page bundled into Enterprise is a different thing from the standalone product. If someone tells you your Jira subscription already covers it, ask which plan. We laid out the standalone list and how the subscriber meter behaves in our status page pricing comparison.

What Opsgenie customers lose in the migration

Opsgenie went off sale on 4 June 2025 and support ends on 5 April 2027, so this is not a hypothetical for anyone still on it. On headline seat cost the move to Jira Service Management Standard is close to neutral: 25 people cost $5,650 a year on a Standard annual contract against $5,985 a year for 25 users on Opsgenie Standard. That similarity is what most migration write-ups report, and on its own it is accurate.

The status page is where it stops being neutral. On Opsgenie a 25 person team got service status pages inside a $9.45 per user tier. On Jira Service Management the same team needs Enterprise at $20,500 a year to get one. Nothing in the seat-price comparison shows that, because it is not a seat price. The Opsgenie pricing and shutdown breakdown has the rest of the migration arithmetic, including the marginal volume ladder that makes most third-party estimates for large teams wrong.

One genuine credit to Atlassian while we are here. Alerts, on-call schedules, routing rules, escalation policies and incident templates are all on the Jira Service Management Free plan, capped at three agents. Most incident tools charge for the rota. If your on-call team is small and already lives in Jira, that part of the migration is better than it had any need to be.

Is it worth buying Enterprise just for a status page?

Almost never, and the reason is not really the price. It is that a status page bought this way is disconnected from anything that knows whether your service is up.

Jira Service Management does not run checks. It receives events from other systems and routes them to a responder. It does not request your checkout flow every 30 seconds from several regions, it does not notice a TLS certificate creeping toward expiry, and it does not watch an API endpoint's response time drift. So an Enterprise status page updates when a human remembers to update it, usually the same human who is currently trying to fix the outage. That is exactly when manual updates stop happening, which is why so many status pages sit green through incidents their customers can plainly see.

The arrangement most teams settle into is to keep the service desk for tickets and buy the status page from whoever runs the probes behind it, so the page reflects real check results rather than someone's spare attention during a bad hour. When we measured 40 major public status pages, only 12 published any uptime history at all, and every one of those 12 was on a platform where the monitoring and the page were joined up. The pattern is in our status page examples census.

What to check before you sign

Three things decide whether the Enterprise line is defensible.

First, work out where you sit inside your agent tier. Annual billing on this product is a flat tier price, so a team of 51 pays the same as a team of 100. If you have just crossed a boundary you are paying for headcount you do not have, and on the Standard tier that can mean an annual contract costs more than monthly billing rather than less. The cost per agent calculator prices both terms side by side.

Second, count what else on the Enterprise list you will actually use. Atlassian Analytics, Data Lake, Atlassian Guard Standard and up to 150 sites are real capabilities, and if two or three of them are already on your roadmap then the status page stops being the thing you are paying $14,850 for and becomes a bonus.

Third, be realistic about who maintains the page. A status page is an operational commitment more than a piece of software, and it fails on process far more often than on features. If your responder team turns over, the runbook that says who posts the update and how quickly needs to survive that turnover, which usually means somewhere to onboard and certify new responders rather than a document nobody opens. Teams that skip this end up with an expensive status page and the same silence during incidents they had before.

The short version

A Jira Service Management status page costs the difference between Enterprise and whatever you would otherwise buy, which is $1,750 a year at three agents, $6,000 at ten and $14,850 at twenty five. It is the only tier that has one. For Opsgenie migrants it is a step down from a feature that used to cost $9.45 a user, and it comes with no monitoring behind it either way.

If the reason you want a status page is that customers should find out from you rather than from a support queue, the cheaper and more reliable route is a page wired directly to the checks. Uptimehub runs those checks from six regions, watches certificate expiry and ports, and includes a branded status page on every plan rather than reserving it for the top of the price list.