Opsgenie Pricing, End of Life Date and Migration (Oct 2026)

Opsgenie's list prices, read on Atlassian's Opsgenie pricing page on October 21, 2026, are Free (up to 5 users), Essentials $9.45, Standard $19.95 and Enterprise $31.90 per user per month billed annually ($11.55, $24.15 and $38.50 billed monthly), but you can no longer buy it: sales ended on June 4, 2025. Opsgenie reaches end of support on April 5, 2027, when Atlassian shuts it off and deletes any data you have not migrated. Atlassian's migration path is Jira Service Management (JSM), where Opsgenie Standard customers are pointed at JSM Premium ($55.28 per agent per month, the monthly list price at the page's default 75 agents), about 2.5 times what 100 Opsgenie Standard users pay; Compass is the developer-focused alternative destination at $7.67 or $23.96 per user per month. Outside Atlassian, PagerDuty, incident.io, Rootly, ilert, Grafana Cloud IRM, FireHydrant, xMatters and SolarWinds (Squadcast) all publish per-user prices, listed below.

Every price and date on this page was read on the vendor's own site on October 21, 2026 and is linked where it appears. Where we did arithmetic on top of a vendor's numbers, the page says so. Arvo AI builds Aurora, an open source incident investigation tool that connects to Opsgenie and JSM; it is not a paging or on-call tool and is not one of the alternatives in the price table.

How much does Opsgenie cost?

Source: atlassian.com/software/opsgenie/pricing, which now opens with "New signups and sales of Opsgenie have ended and Opsgenie alert, on-call, and incident response features are available in Jira Service Management." Essentials is capped at "100 incidents per month (account-wide)"; Standard and Enterprise are unlimited, and the Free plan has no incident management. International SMS and voice on Essentials is users x 25, then $0.35 each. Incoming call routing on Standard and Enterprise includes one number ($10 for each additional number) and 100 US and Canada minutes, then $0.10 a minute, or $0.35 a minute internationally.

The headline prices are for the first 25 users. The page's price calculator uses progressive tiers, so each additional block of users is cheaper. For example, the monthly Standard rate is $24.15 for users 1 to 25, $22.05 for users 26 to 50 and $21 for users 51 to 100. Totals for a 100-user account, our arithmetic from those tiers:

Above 10,000 users Atlassian asks you to contact sales. These prices only matter for renewals now (see below).

When is Opsgenie end of life?

Atlassian announced the change on March 3, 2025 in The Evolution of IT Operations and Opsgenie. The dates:

As of October 21, 2026 that leaves 166 days. Two details change your real deadline:

• The 120-day clock. Once your data has migrated, "Opsgenie will also shut down automatically 120 days after your migration date if you don't turn it of[f] manually," and turning it off "CANNOT be undone" (Atlassian). Your Opsgenie may therefore go dark before April 2027. The JSM guide adds that the turn-off date "may change depending on your subscription, so it's best to refer to your product UI" (source).
• The REST API. "Opsgenie REST APIs will continue to work until April 5, 2027," but Atlassian recommends moving to the JSM Operations REST API before your Opsgenie is turned off. Every script, Terraform module and monitoring tool that calls api.opsgenie.com needs a new endpoint; Atlassian has a separate guide for moving from the Opsgenie Terraform provider to the Atlassian Operations provider.

What happens to my data when Opsgenie shuts down?

From What happens when Opsgenie is turned off: users can no longer log in or retrieve any data, the Opsgenie mobile app is deactivated, remaining Opsgenie-based integrations stop working, and features left behind (deprecated notification policies, incident rules, Opsgenie actions, older integrations) become permanently unavailable. Only migrated data survives in JSM: alerts, on-call schedules, escalation policies, incident history, audit logs, and migrated configurations and integrations.

What are the Opsgenie migration paths?

Jira Service Management

JSM is the destination Atlassian's tooling is built around. The in-app tool (Settings > Plan your move) recommends a plan based on your Opsgenie plan (source):

The JSM prices are the monthly-billing figures the pricing page shows at its default team size of 75 agents. They are averages: the price data behind the page's calculator charges Premium at $61.60 for each of the first 15 agents and $53.70 for agents 16 to 100 ((15 x 61.60 + 60 x 53.70) / 75 = $55.28), and Standard at $26.90 then $20.15 (which averages $21.50 at 75). Annual billing saves "up to 17%" and is sold in agent bands; 51 to 100 Premium agents is $55,000 a year. JSM is now sold as part of Atlassian's Service Collection, which bundles Rovo AI features, Assets and customer service apps into the same per-agent price.

What it costs compared with Opsgenie. Our arithmetic, assuming every one of 100 Opsgenie Standard users becomes a JSM agent, at list prices read on October 21, 2026:

So the plan Atlassian recommends costs about two and a half times as much at list price, before any negotiated discount or any credit for unused Opsgenie time. Teams that only need some people to respond can license fewer agents. In return, JSM Premium includes ITSM, asset management and AI alert grouping that Opsgenie does not. Atlassian also notes that the trial "may be extended to make up for any unused time left on your Opsgenie plan" (billing guide).

Why the plan level matters. Atlassian's feature table puts several Opsgenie Standard features behind JSM Premium or Enterprise:

What does not carry over at all, per the same page and the JSM shifting guide:

• Incident Command Center, conference rooms, incident templates, response roles and email templates (replaced by Incident Configurations).
• Opsgenie actions and incident rules: they "won't be automatically moved" and are rebuilt as Jira Automation.
• Chat integrations must be re-authenticated by hand.
• Custom roles not supported in JSM fall back to the User role; heartbeats with no assigned team are not moved.
• Opsgenie-provided phone numbers for call routing must be ported to your own Twilio account before migration (source).
• The Opsgenie mobile app is replaced by the Jira mobile app; notification rules must be recreated there and insistent notifications are not available (source).
• MSP sub-accounts become free accounts that need their own migration.

Compass

Atlassian's docs describe migrating "from Opsgenie to Jira Service Management or Compass" with one shared Operations layer: alerts, schedules, escalation policies, routing rules and integrations stay in sync across both, and users only get licenses for the product you pick as the primary destination (source). Compass ties alerts to software components instead of ITSM tickets. The plan recommendation table in the migration docs lists only JSM plans; to land in Compass you pick it as the primary destination product when you set up the migration.

Compass pricing, monthly only ("Subscriptions to Compass are currently only available as monthly payments"):

The page shows these at its default team size of 300 users.

Should I move to JSM or find an alternative to Opsgenie?

Stay with Atlassian if you already run JSM or Jira and want incidents tied to tickets, changes and assets; that is what the Premium price buys. If your Opsgenie use was paging, schedules and escalations, and you were on Essentials or Standard, the JSM plan with feature parity costs more than you pay today, and the dedicated on-call tools below are priced closer to Opsgenie. Compass is the cheaper Atlassian option for engineering teams, as long as the features you need are on its Premium plan.

What are the alternatives to Opsgenie, and what do they cost?

Status notes, each from the vendor's own page: Grafana OnCall OSS "entered maintenance mode and was archived on 2026-03-24" and points users to Grafana Cloud IRM (GitHub). Freshworks signed an agreement to acquire FireHydrant on December 15, 2025, "expected to close in Freshworks' first fiscal quarter of 2026"; FireHydrant now has a product page on freshworks.com, but we found no closing announcement on Freshworks' newsroom. For the full PagerDuty versus JSM trade-off, see PagerDuty vs Jira Service Management; for AI pricing across these vendors, see AI SRE and incident tool pricing.

Which Opsgenie alternatives can import our existing schedules and escalation policies?

Three of the vendors above advertise Opsgenie migration on their pricing pages; we have not tested any of them. FireHydrant's page carries a banner for "Signals Migrator: Migrate your PagerDuty or Opsgenie config in minutes". incident.io's on-call plan lists "Best-in-class migration support", and Rootly promises "A tailored and proven migration that avoids any downtime". Ask each vendor for the exact objects its importer moves (schedules, rotations, overrides, escalation policies, routing rules, integrations) and try it on a copy of your config before the 120-day clock starts. Atlassian's own migration moves alerts, schedules, escalation policies and incident history into JSM automatically.

What none of these tables tell you is how well each product investigates an alert. That is a separate category, covered in AI-powered incident investigation tools.

Where Aurora fits after the page

Aurora is not a paging tool. It has no on-call schedules, escalations or notifications, so it does not replace Opsgenie, JSM or anything in the table above. It is an open source investigator that takes the alert after the page fires. Its Opsgenie and JSM connector takes either an Opsgenie API key (GenieKey, US or EU region) or an Atlassian account email and API token for JSM Operations. When an alert Create event arrives on its webhook, it opens an incident and starts a root cause investigation (tasks.py skips every other action), and it answers questions like "who is on call right now?" from the same API.

The plan level decides whether that works. Atlassian's Webhook integration doc says "Webhook is an outgoing integration which means you should be on a Premium or Enterprise plan to use it." So on JSM Standard, Aurora's docs tell users it can only query alerts on demand from chat: nothing is pushed, so no investigation starts on its own. The same limit applies to any tool you want Opsgenie alerts pushed to after the move. If you plan to land on JSM Standard and keep a downstream webhook consumer, check this before you migrate.

How well it investigates is published, with its limits, on /benchmark: Aurora found the root cause in 34 of 38 runs (4 partial) on 19 injected Kubernetes faults, with every grade read by a person, at a median of 153.5 seconds and $0.35 per investigation. HolmesGPT was 3.4 times faster at the median (45 seconds). The two agents' prompts differed slightly (both are quoted on /benchmark), and Arvo AI wrote the scenarios and builds Aurora; the lab is open so you can rerun it. For what one of those investigations looks like, see the runbook on an alert that covers only one of two faults. Aurora is on GitHub under Apache 2.0, or book a demo.

Prices and dates verified on Atlassian's and each vendor's own pages on October 21, 2026. List prices change; check the linked page before you sign.