JSM Premium and Atlassian Statuspage: Why Opsgenie Migrators Still Need Two Products

The migration everyone is being pointed toward

If you run on-call through Opsgenie, you already know the date. Atlassian stopped selling new Opsgenie subscriptions on June 4, 2025, and the product shuts down completely on April 5, 2027, after which remaining customer data is deleted. Atlassian's own recommended destination for that migration is Jira Service Management, its combined ITSM and operations platform.

For teams that also run a public status page on Opsgenie, or that are adding one for the first time as part of this move, the natural assumption is that JSM covers it. Atlassian is, after all, the same company that owns Atlassian Statuspage, one of the best-known status page products on the market. Surely a single vendor bundles its own products together.

It does, eventually, and that word is doing a lot of work.

How this actually rolled out in 2026

This isn't a feature Atlassian has quietly had for years. Reading its own product communications in order shows a specific, recent rollout, which matters because it means most existing "Opsgenie alternatives" and "JSM review" content on the web predates it and hasn't caught up.

16 February 2026: Atlassian's Community forum publishes "No More Incident Communication Stress: Introducing Status Pages," announcing status pages built directly into JSM. The post describes custom branding (logo, colors, favicon, custom domain), subscriber management by email or webhook capped at 10,000 subscribers per site, Service Registry integration linking components to incident data, and AI-drafted status updates pulled from the incident itself. It states plainly that admins reach the feature from "Operations > Status pages" inside JSM, not through a separate product.

2 July 2026: a follow-up post, "What's New for Status Pages in JSM: Automation, Email Subscribers and Custom Domains," adds three specific improvements: a Jira Automation action ("Send update to Statuspage") that pushes incident updates automatically, manual email-subscriber management via comma-separated lists, and a guided custom-domain setup that replaces manual DNS configuration. Atlassian also says it's separately working on maintenance-update automation and draft emails for stakeholders, meaning the feature is still actively being built out five months later.

Both posts agree on the one detail that matters most for anyone budgeting a migration: which plan this ships on.

"status pages native to JSM are only available on enterprise tier." Source: Deeksha, Atlassian Team, Atlassian Community, 2 July 2026

The February announcement says the same thing in its own words: native public status pages are listed as an Enterprise-exclusive capability, alongside AI-powered features that split further, Smart Stakeholder Suggestions on Premium and Enterprise, auto-drafted updates on Enterprise only.

That leaves JSM Standard and JSM Premium, the two plans most Opsgenie migrators are actually choosing between, with no native status page at all. Not a limited version. None.

The real cost stack, if you're on Standard or Premium

Atlassian's own pricing page, checked 25 September 2026, lists JSM Standard at $20 per agent/month, Premium at $51.42 per agent/month, and Enterprise with no public price at all: the page requires switching to annual billing to even attempt to view an Enterprise figure, and otherwise routes you to "Contact sales." (At higher agent-count volume tiers, Atlassian's calculator applies lower blended rates, $18.74 Standard and $47.48 Premium at the 100-agent tier as confirmed separately on 24 September 2026, but the tier gate on status pages does not move with volume: it is Enterprise or nothing regardless of headcount.)

So a team on JSM Premium wanting a status page has exactly two paths, and both cost more than the plan they're already paying for:

1. Upgrade the whole organization to Enterprise, a plan with no public price, to get status pages for every agent whether they need the rest of the Enterprise feature set or not. That means a sales negotiation for a plan whose price Atlassian doesn't publish, just to unlock one feature, and a quote you can't compare against anything until you have it.
2. Keep Premium and buy Atlassian Statuspage separately. This is the path most teams actually take, and it is worth pricing out in full.

Even the "integration" is a bridge between two bills, not a merger

Atlassian does publish a connector for exactly this situation: Statuspage for Jira Service Management on the Atlassian Marketplace. It is free, and it is worth being precise about what "free" means here.

"This is a FREE add-on, so you don't have to pay anything on top of the cost of your Statuspage account." Source: Statuspage for Jira Service Management, Atlassian Marketplace listing, checked 25 September 2026

That sentence only makes sense if a Statuspage account is a separate, paid thing you are expected to already have, or to go get, which the same listing confirms directly: it invites anyone without one to "try it today for free." What the app actually does, per its own description, is display status banners and incident information inside the JSM help center by reading from an already-existing, separately-billed Statuspage subscription. It is a display layer, not a data merge. Your status page still lives on Statuspage's infrastructure, under Statuspage's pricing, managed from a second console.

What that second product actually costs

Atlassian Statuspage's own pricing page, checked 24 September 2026, runs two separate ladders depending on whether pages are public or require authentication.

Public status pages

Private / authenticated status pages, a separate tier ladder

The math at four team sizes

A single example can look like a cherry-picked scenario, so here is the same calculation run at four common team sizes, using each vendor's own published list prices, checked on the dates cited above. All Quiet figures assume the Pro plan ($9.99/user/month), which includes status pages at every size shown; the JSM Premium figures use the public per-agent list price, not the lower volume-tier rate, since the volume discount and the status-page gate are independent of each other.

The Statuspage tier assumption at 50 and 100 agents is a reasonable estimate based on typical subscriber counts at that org size, not a quoted figure; a team's actual subscriber count could put them in a different tier on either side. The JSM Premium figures, and every Statuspage tier price shown, are exact list prices from the vendor pages cited throughout this article.

To be direct about what this comparison is and isn't: JSM Premium includes a full ITSM platform, change management, approval workflows, and a service catalog that All Quiet does not attempt to replace and was never designed to. If your organization genuinely runs ITIL processes and needs that surface, JSM is doing a different, bigger job than an on-call and incident tool, and that's a legitimate reason to be on it. The point here is narrower and doesn't require ignoring that: the specific requirement of "we need a status page" costs $0 extra inside All Quiet's plan and $29 to $1,499 extra a month on top of JSM Premium, indefinitely, because it is priced by a company that treats status pages as a standalone product with its own subscriber-based ladder, not as a feature of the plan you're already paying for.

"We already have Atlassian Statuspage, so this doesn't apply to us"

It's a fair objection, and worth answering directly rather than skipping past. If your organization already has an active Statuspage subscription, separate from JSM, before this migration, moving your alerting off Opsgenie doesn't force you to also move your status page. Statuspage will keep working exactly as it does today, JSM or no JSM.

What doesn't go away is the underlying structure: you are still running two vendor relationships to do one team's job, still paying two invoices, and still maintaining incident data in two places that don't share a model unless you also install the free connector, which, as shown above, only displays one system's data inside the other rather than unifying them. The question this article is actually answering isn't "should you cancel Statuspage today." It's "does JSM's status-page story remove the need for a second product," and for Standard and Premium customers, it doesn't. Whether that second product is a cost worth accepting is a separate, legitimate decision each team can make with the numbers above in hand.

Why All Quiet doesn't have this problem

The reason is structural, not promotional. All Quiet was built as one incident management platform: on-call scheduling, multi-channel alerting, incident response, and status pages, sharing the same data model. When an incident updates, the status page can reflect it because it's reading from the same incident, not from a second product that has to be told separately.

That shows up in three concrete ways worth stating in order of how hard they are for a bundled-and-metered incumbent to copy.

One flat price for the whole platform, not a metered add-on. Atlassian prices status pages as a distinct product with its own subscriber-count ladder, on top of whatever you already pay for JSM or for Opsgenie's replacement. All Quiet includes status pages inside the $9.99/user/month Pro plan, the same plan that also covers on-call, escalations, and multi-channel alerting.

No subscriber-count tax. Atlassian Statuspage's tiers step up at 100, 250, 1,000, 5,000, and 25,000 subscribers on the public ladder alone, with a second, steeper ladder for private pages. All Quiet doesn't meter status pages by how many people subscribe to them.

It's not a bolt-on. The free JSM-to-Statuspage connector is a display bridge between two separately billed products, confirmed directly by its own Marketplace listing, quoted above. All Quiet's status page draws from the same incident your on-call engineer is already working, so nothing needs to be typed twice into a second system.

A fourth point is worth stating as fact rather than as a competitive jab, because Atlassian also offers EU regions and this isn't a place All Quiet has a clean advantage to claim: All Quiet is a European incident management platform, built in Berlin, with selectable EU data residency in Frankfurt, GDPR compliance, and ISO 27001 certification.

If you're migrating off Opsgenie before April 2027

The shutdown date isn't the hard part of this migration. Exporting schedules, escalation policies, and integrations before the cutoff is a known, plannable task, and All Quiet's Terraform-first migration guides exist specifically for it. The part worth catching before you commit to a destination is the one this article covers: if status pages are part of what you're replacing, check which JSM plan you're actually being quoted, because "Jira Service Management" and "a status page" are not the same purchase unless you're paying for Enterprise.

A short checklist for anyone weighing this specific decision:

1. Confirm which JSM tier your quote or renewal is actually for. Standard and Premium do not include native status pages; only Enterprise does, per the sources quoted above.
2. If you're on or considering Premium, price out Atlassian Statuspage separately at your expected subscriber count, using the tables above, before comparing total cost against alternatives.
3. If you're considering the Enterprise upgrade specifically to get status pages, get the actual sales-quoted per-agent rate in writing and compare it against Premium plus a standalone Statuspage tier; the free connector app doesn't change this math, since it only displays an existing subscription rather than replacing one.
4. Weigh whether your organization needs JSM's ITSM surface at all. If the honest answer is "no, we mainly used Opsgenie for on-call and alerting," a platform built around that job, with status pages included, may be a simpler and cheaper fit than reproducing JSM's structure to keep one feature.

See the full breakdown on All Quiet vs. Jira Service Management, and the underlying case for leaving Opsgenie on our Opsgenie alternative page. If status pages are the part you're replacing, see how All Quiet compares on our Atlassian Statuspage alternative page.

Sources checked for this article

• Native Status Pages in Jira Service Management, Atlassian Community, published 16 February 2026: confirms native status pages are a built-in JSM feature, Enterprise plan only.
• What's New for Status Pages in JSM, Atlassian Community, published 2 July 2026: confirms, in an Atlassian Team member's own words, that native status pages remain Enterprise-only, and adds automation, email-subscriber, and custom-domain detail.
• Jira Service Management pricing, Atlassian, checked 25 September 2026: Standard $20/agent/month, Premium $51.42/agent/month, Enterprise unpriced/contact sales.
• Statuspage for Jira Service Management, Atlassian Marketplace, checked 25 September 2026: confirms the connector is free but requires an existing, separate Statuspage subscription.
• Migrate from Opsgenie, Atlassian, checked 25 September 2026: confirms the April 5, 2027 shutdown date and JSM as Atlassian's recommended migration path.
• Atlassian Statuspage pricing, checked 24 September 2026: public and private tier tables above.