TL;DR — Opsgenie is ending. Atlassian stopped new Opsgenie signups on June 4, 2025 and will shut the service down permanently on April 5, 2027. Any data not migrated by that date will be deleted. Atlassian's official migration paths are Jira Service Management (JSM) Operations and Compass. Many teams are using the forced migration as a chance to evaluate alternatives — especially AI-powered options that weren't available when Opsgenie was originally adopted.
Opsgenie is an alerting and on-call management platform that was acquired by Atlassian in 2018. For years it was one of the most widely adopted tools in the SRE stack, sitting alongside PagerDuty and xMatters. In March 2025 Atlassian announced that Opsgenie's capabilities would be absorbed into Jira Service Management and Compass, and that the standalone product would be retired.
This guide covers what Opsgenie is, how it works, what it costs, the exact end-of-life timeline, what happens to your data when it shuts down, the official migration paths, and the current landscape of alternatives. Every claim is linked to an official source.
Last updated: April 21, 2026.
What is Opsgenie?
Opsgenie is a cloud-based incident alerting and on-call management platform for DevOps and SRE teams. It routes alerts from 200+ monitoring tools to the right on-call responders via SMS, voice, email, push, Slack, and Microsoft Teams. Atlassian acquired Opsgenie in 2018 and will retire the standalone product on April 5, 2027.
The tool was founded in 2012 and its capabilities are being absorbed into Jira Service Management and Compass.
Opsgenie at a glance vs top alternatives
| Opsgenie (retiring) | JSM Operations | PagerDuty | Aurora | |
|---|---|---|---|---|
| Available after April 2027 | No | Yes | Yes | Yes |
| Starting price | N/A (closed) | Per-agent | $21/user/mo | Free (OSS) |
| Built-in AI RCA | No | Partial | Add-on ($699+/mo) | Yes (agentic) |
| Open source | No | No | No | Apache 2.0 |
| On-call + escalations | Yes | Yes | Yes | Via integration |
Opsgenie End-of-Life Timeline (Official)
Atlassian announced the end of Opsgenie in The Evolution of IT Operations. The three critical dates are:
| Milestone | Date | What it means |
|---|---|---|
| End of Sale | June 4, 2025 | No new signups, upgrades, or downgrades on standalone Opsgenie |
| End of Support / Shutdown | April 5, 2027 | Opsgenie service is turned off; REST APIs stop responding |
| Data Deletion | April 5, 2027 | All unmigrated alerts, schedules, escalation policies, integrations, and incidents are permanently deleted |
Existing customers can continue using Opsgenie through April 5, 2027, but cannot expand their footprint. After migration, Opsgenie and the new JSM or Compass instance can run in parallel for up to 120 days, after which Opsgenie is automatically switched off (official source).
"Opsgenie REST APIs will continue to work until April 5, 2027. However, Atlassian recommends updating all API endpoints before Opsgenie is turned off to avoid any disruptions." — Atlassian Support
Opsgenie Features
Opsgenie's core feature set is mature — this is a 13-year-old product. Here is what it currently provides, verified from Atlassian's documentation.
Integrations
Opsgenie ships with over 200 integrations with monitoring, ticketing, chat, and ITSM tools. Most are bidirectional — alerts flow in, and acknowledgement or closure events flow back.
Multi-Channel Notifications
Supported notification channels, per Atlassian documentation:
- SMS — Aggregated at a minimum 1-minute interval; users can acknowledge or close alerts via reply
- Voice calls — Capped at 2 minutes; dial-pad actions (1 = read, 2 = close, 3 = acknowledge, 4 = escalate)
- Email — With inline action buttons
- Push notifications — iOS and Android with swipe-to-ack/close
- Slack — Bidirectional integration
- Microsoft Teams — Bidirectional integration
On-Call Management
Opsgenie supports daily, weekly, and custom rotation types including follow-the-sun, with ad-hoc overrides, "Take on-call for an hour" self-service, and a "No-One" participant for scheduled gaps (official docs).
Escalation Policies
Default escalation is 5 minutes, then 10 minutes, repeatable up to 20 times per alert. Acknowledgement or closure stops the policy (official docs).
Heartbeat Monitoring
A "dead man's switch" — if an expected HTTP ping doesn't arrive within the configured interval (minimum 1 minute), Opsgenie fires an alert. Available on Standard and Enterprise plans only (official docs).
Alert Deduplication, Suppression, and Grouping
Opsgenie uses an alias field to deduplicate alerts — identical alias values increment a counter on the existing alert instead of creating a new one. The counter stops logging at 100 occurrences, but deduplication continues (official docs).
Delay policies can hold notifications for a fixed time, until a deduplication threshold is reached, or until an occurrence rate threshold triggers.
Routing Rules
Each team can have up to 100 routing rules, evaluated top-down with first-match semantics. Free and Essentials plans are limited to 1 routing rule and can only route by priority or tags. Standard and Enterprise plans support full-field routing.
Reporting by Plan
| Report | Essentials | Standard | Enterprise |
|---|---|---|---|
| Notifications + API Usage | Yes | Yes | Yes |
| Monthly Overview (Looker) | No | Yes | Yes |
| Advanced reporting / MTTA / MTTR | No | Yes | Yes |
| Team Reports | No | No | Yes |
| Global Reports + Looker dashboards | No | No | Yes |
| Post-Incident Analysis | No | No | Yes |
Source: Opsgenie Advanced Reporting.
Mobile App
Opsgenie's iOS and Android apps support swipe-to-acknowledge from the lock screen and iOS Critical Alerts that override Do Not Disturb and silent mode.
SSO / SAML
SSO is available on Standard and Enterprise plans only, with supported providers including Google, Azure AD, Okta, OneLogin, Ping Identity, and Microsoft AD FS (official docs).
Compliance
Opsgenie is covered under Atlassian's Trust program with SOC 2 Type II (annual), ISO/IEC 27001, ISO/IEC 27018, CSA, and TISAX AL2 certifications, plus a pre-signed GDPR DPA (official page).
Data Residency
Opsgenie is offered in US and EU regions, both hosted on AWS (official docs).
Who Should Use Opsgenie in 2026?
With end-of-sale already behind us, Opsgenie is only relevant to existing subscribers planning their exit. New teams cannot sign up. The question for existing subscribers is whether to stay with Atlassian (migrate to JSM or Compass) or evaluate alternatives.
- Stay with Atlassian (migrate to JSM Operations) if you are already a Jira Service Management customer, need ITSM workflows (change, problem, incident), and are comfortable with the Premium-tier price increase.
- Stay with Atlassian (migrate to Compass) if you are a DevOps or SRE team that wants alerting paired with a software component catalog and service ownership model, not ITSM.
- Switch to a dedicated alerting tool (PagerDuty, ilert, Squadcast) if you want deeper alerting features and do not need Atlassian platform integration.
- Switch to AI-powered incident management (incident.io, Rootly, Aurora) if you want autonomous investigation and root cause analysis, not just alert routing.
Opsgenie Pricing (Standalone, 100-User Reference)
Pricing below is for standalone Opsgenie with 100 users — sourced from the official Opsgenie pricing page. New signups are closed, so these numbers apply only to existing customers on legacy plans.
| Plan | Monthly | Annual | Routing Rules | Heartbeats | SSO |
|---|---|---|---|---|---|
| Free | $0 (up to 5 users) | — | 1 | No | No |
| Essentials | $11.55/user/mo | $9.45/user/mo | 1 | No | No |
| Standard | ~ $29/user/mo | Discounted | 100 per team | Yes | Yes |
| Enterprise | ~ $39/user/mo | Discounted | 100 per team | Yes | Yes |
Enterprise-exclusive features include Incident Command Center (built-in video chatroom tied to incidents), Stakeholders (notification-only users), Service Subscriptions, Incident Templates, and Post-Incident Analysis.
Incoming call routing is charged separately: $0.10 per minute for US/Canada and $0.35 per minute internationally after the free tier.
What Happens When Opsgenie Is Turned Off
On April 5, 2027, Atlassian will:
- Disable the Opsgenie web application, mobile apps, and REST APIs
- Delete all data that was not migrated to JSM or Compass — alerts, on-call schedules, escalation policies, integrations, incidents, notes, attachments
- Stop accepting any incoming webhooks or notifications
Important: unlike the legacy Opsgenie Enterprise plan, JSM automatically deletes alert data after a retention window. Once alert data is deleted in JSM, it cannot be recovered. Export anything you need for compliance or audit before migration (official source).
Opsgenie Migration Paths: JSM vs Compass
Atlassian offers two official migration destinations. Both share the same underlying Operations engine — schedules, alerts, and policies sync bidirectionally — but the wrapping product and pricing differ (managing operations across both).
Jira Service Management (JSM) Operations
JSM Operations is the ITSM-centric path — alerts are paired with change, problem, and incident workflows. JSM pricing (official page):
| JSM Plan | Price | Outbound Webhooks | Incident Command Center | Post-Incident Reviews | 99.9% SLA |
|---|---|---|---|---|---|
| Free | $0 (up to 3 agents) | No | No | No | No |
| Standard | Per-agent | No | No | No | No |
| Premium | Per-agent | Yes | No | Yes | Yes |
| Enterprise | Contact sales | Yes | Yes | Yes | 99.95% |
Opsgenie features that do not carry over to JSM Operations, per Atlassian's shifting guide:
- Incoming Call Routing integration is not supported
- Stakeholder role — custom Opsgenie roles default to User
- Alert creation rules from Opsgenie do not migrate
- Legacy
api.opsgenie.com/v1/servicesendpoint stops working - Chat integrations must be reconnected manually
- The old Opsgenie mobile app stops working — responders switch to the Jira mobile app
Compass
Compass is positioned as a software component catalog + alerting platform aimed at DevOps, SRE, and Platform Engineering teams rather than ITSM. Compass pricing (official page):
| Compass Plan | Price | Alerting | Heartbeats | 99.9% SLA |
|---|---|---|---|---|
| Free | $0 (up to 3 full users) | Basic | No | No |
| Standard | $8/user/mo | Yes (150+ integrations) | No | No |
| Premium | $25/user/mo | Advanced | Yes | Yes |
Migration Friction
Real complaints from the Atlassian Community:
- Price increases — JSM Premium is widely reported as more expensive than standalone Opsgenie Standard
- Feature parity gaps — some users need JSM and Compass together to match Opsgenie's alert processing depth
- 120-day forced cutover — Opsgenie auto-shuts-down 120 days after migration begins; Atlassian has declined requests to extend the window
- Split paths confusion — some features only exist in JSM, others only in Compass, forcing customers to choose or buy both
One user put it bluntly: "Switching to Compass seems like buying a new car just to listen to the radio."
Why Teams Are Evaluating Alternatives Instead of Migrating
The forced migration has created a rare evaluation moment. Teams that adopted Opsgenie in 2018 are re-evaluating the entire category with three shifts in mind:
- AI-native incident management has arrived. Products like Aurora, incident.io AI SRE, Rootly AI, and PagerDuty Advance didn't exist when most Opsgenie contracts were signed. Per Gartner (October 2025), 54% of I&O leaders are now adopting AI in operations.
- On-call burnout is a hiring and retention problem. The Catchpoint SRE Report 2025 found that roughly 70% of SREs cite on-call stress as a direct cause of burnout, and toil rose to 30% of SRE work.
- Downtime costs have climbed. PagerDuty's 2024 research put the average cost of a major incident at $794,000, or $4,537 per minute. ITIC's 2024 survey found 97% of large enterprises say an hour of downtime costs them over $100,000.
Against this backdrop, "like-for-like Opsgenie replacement" is no longer the only question — many teams are asking whether the replacement should also do autonomous investigation, not just alerting.
"By 2030, 75% of IT work will be human plus AI, 25% will be AI-only, and zero percent will be human-only." — Gartner CIO survey of 700+ CIOs, 2025
Top Opsgenie Alternatives in 2026
Verified pricing and capabilities from each vendor's official site. Last checked April 2026.
| Product | Starting price | Free plan | Open source | AI-native | Best for |
|---|---|---|---|---|---|
| Aurora by Arvo AI | $0 self-hosted | Yes (OSS) | Apache 2.0 | Yes (agentic) | OSS teams wanting alerting + autonomous RCA in one stack |
| PagerDuty | $21/user/mo | 14-day trial | No | Yes (PagerDuty Advance, $415+/mo) | Enterprises wanting the incumbent with AI add-ons |
| ilert | Up to €49/user/mo Scale | Yes (5 responders) | Partial (MCP server) | Yes | EU-based teams requiring GDPR data residency |
| Squadcast | $9/user/mo Pro | Yes (5 users) | No | Yes | Small SRE teams on tight budgets |
| Rootly OnCall | From $20/user/mo | Trial | Partial (MCP, Agents JSON) | Yes (AI SRE standalone) | Teams wanting modular IR + on-call + AI SRE |
| incident.io On-call | $19 base + $10 add-on | Trial | No | Yes (AI SRE) | Slack-native incident coordination with AI |
| FireHydrant Signals | Usage-based | Trial | No | Yes (AI Copilot) | Teams preferring pay-per-alert over per-seat |
| xMatters | $39/user/mo base | Yes (10 users) | No | Partial | Everbridge customers needing codeless workflows |
| Grafana OnCall OSS | Free | Yes | AGPLv3 (archived) | No | Not recommended — archived March 24, 2026 |
Product Notes
PagerDuty — Most mature alerting product. PagerDuty Advance adds AI agents (SRE, Scribe, Shift) but requires a paid base plan and a separate $415+/mo Advance subscription. AIOps features require a $699+/mo add-on.
ilert — EU-hosted with a clear GDPR and data-sovereignty story; the AI SRE opts out of LLM training on customer data. Free tier includes 5 responders.
Squadcast — Acquired by SolarWinds on March 3, 2025. Roadmap now driven by SolarWinds.
Rootly — Rootly AI Labs launched February 20, 2026; Rootly MCP GA April 2, 2026. Rootly sells IR, On-Call, and AI SRE as standalone products.
incident.io — $62M Series B funded the launch of AI SRE — an always-on agent that investigates alerts, drafts PRs, and can autoresolve incidents.
FireHydrant — Acquisition by Freshworks expected to close Q1 2026; FireHydrant will become the incident layer inside Freshservice.
Grafana OnCall — Entered maintenance mode March 11, 2025 and archived March 24, 2026. Do not start new deployments. Grafana is consolidating on a unified Cloud IRM app.
Splunk On-Call (VictorOps) — Pricing not publicly listed. Cisco completed its $28B Splunk acquisition in March 2024; no official EOL announcement as of April 2026, but the product has seen minimal public investment since.
How Aurora Integrates with Opsgenie and JSM Operations
Aurora is open-source agentic incident management that works alongside Opsgenie (and the JSM Operations successor). Most AI incident tools have already deprecated Opsgenie support ahead of the 2027 shutdown — Aurora supports both so teams can run their migration on their own timeline. The integration is fully documented in Aurora's docs.
What Aurora does with Opsgenie alerts:
- Bidirectional authentication — Accepts either a native Opsgenie GenieKey (US or EU region) or a JSM Operations Atlassian API token. Credentials are encrypted in HashiCorp Vault.
- Webhook ingestion — Receives Create, Acknowledge, Close, and custom alert actions. Only Create triggers an investigation, preventing duplicates from acknowledgement webhooks.
- Alert correlation — Aurora's AlertCorrelator groups incoming alerts with existing incidents by service, title, and time proximity. Correlated alerts attach to the parent incident instead of spawning a new one.
- Priority mapping — Opsgenie priorities map deterministically: P1 → critical, P2 → high, P3 → medium, P4/P5 → low.
-
Service extraction — Aurora reads alerts for a
service:xxxtag first, then falls back to the source and entity fields. - Autonomous RCA — On alert creation, Aurora creates an incident record, generates an AI summary, and launches a LangGraph-orchestrated agent that queries your cloud infrastructure to find the root cause.
- Bidirectional JSM commenting — For JSM Operations users, Aurora posts an "RCA in progress" comment back onto the linked Jira incident and updates it with findings.
- Chatbot query surface — Engineers can ask Aurora in natural language: "Who is on-call right now?", "Show me P1 alerts from the last 24 hours", "Get details for alert ABC-123". Aurora queries 8 Opsgenie resource types (alerts, alert details, incidents, incident details, services, on-call, schedules, teams) via parallel API calls.
"Most AI investigation tools only work with PagerDuty. We built Aurora to meet SRE teams where they already live — including Opsgenie and JSM — so AI-powered RCA isn't gated on migrating your alerting stack first." — Noah Casarotto-Dinning, CEO at Arvo AI
git clone https://github.com/Arvo-AI/aurora.git
cd aurora
make init && make prod-prebuilt
How to Migrate Off Opsgenie Before April 5, 2027
Prerequisites: administrator access to your Opsgenie account, access to your monitoring stack, and a target destination decided (JSM Operations, Compass, or a third-party alternative).
If You Are Staying with Atlassian
- Inventory your Opsgenie config. Document integrations, escalation policies, routing rules, heartbeats, on-call schedules, and custom roles.
- Choose JSM Operations vs Compass. Pick JSM if you need ITSM workflows (change, problem, incident); pick Compass if you want alerting tied to a service catalog.
- Verify feature parity. Review the Atlassian shifting guide for features that do not migrate.
- Export historical data. Alert data in JSM auto-deletes after a retention window — export anything needed for audit or compliance first.
- Run the in-product migration tool. Atlassian provides a guided migration that copies your data to JSM or Compass.
- Re-authenticate chat integrations. Re-authorize Slack and Microsoft Teams — OAuth grants do not transfer.
- Update API endpoints. Every consumer of the legacy Opsgenie REST API must be repointed to the new JSM Operations endpoints before April 5, 2027.
- Replan the mobile rollout. The standalone Opsgenie mobile app stops working — responders move to the Jira mobile app.
- Close Opsgenie within 120 days. After migration, Opsgenie runs in parallel for up to 120 days, then auto-shuts down.
If You Are Evaluating Alternatives
- Shortlist two or three alternatives using the comparison table above.
- Run a 90-day parallel trial alongside Opsgenie — most vendors offer free trials.
- Validate the integrations that matter — especially monitoring tool webhooks and your chat platform.
- Measure MTTR and on-call satisfaction against your Opsgenie baseline.
- Decide before Atlassian's 120-day cutover window closes on any migration you start with JSM or Compass.
Frequently Asked Questions
When is Opsgenie being shut down?
Atlassian will shut down Opsgenie permanently on April 5, 2027. End of sale was June 4, 2025 — no new signups, upgrades, or downgrades are allowed. On April 5, 2027 the service will be disabled and any data that has not been migrated to Jira Service Management or Compass will be permanently deleted.
Can I still buy Opsgenie in 2026?
No. Atlassian closed new Opsgenie sales on June 4, 2025. Existing customers can continue using their current Opsgenie subscription until April 5, 2027 but cannot upgrade, downgrade, or add new users beyond their existing plan limits.
What are the official Opsgenie migration paths?
Atlassian offers two paths: Jira Service Management (JSM) Operations for ITSM teams needing change, problem, and incident workflows, and Compass for DevOps/SRE teams wanting alerting paired with a service catalog. Both share the same Operations engine, so schedules, alerts, and policies sync if you use both.
Will my Opsgenie data be preserved after migration?
Only data you explicitly migrate through Atlassian's in-product migration tool is preserved. Unlike legacy Opsgenie Enterprise, JSM automatically deletes alert data after a retention window — so you must export anything needed for compliance or audit before migration. Some features like alert creation rules and custom roles do not carry over at all.
How much does Opsgenie cost in 2026?
Existing standalone customers pay $9.45/user/month annual or $11.55/user/month monthly on Essentials at 100 users. Standard and Enterprise add full routing, SSO, heartbeats, and advanced reporting. Incoming call routing is billed separately at $0.10/minute (US/Canada) and $0.35/minute (international). New signups are no longer accepted.
What are the best Opsgenie alternatives?
The strongest 2026 alternatives are PagerDuty (incumbent with AI add-ons), incident.io (Slack-native with AI SRE), ilert (EU-hosted, GDPR-focused), Squadcast (budget-friendly, SolarWinds-owned), Rootly (modular IR + on-call + AI SRE), and Aurora by Arvo AI (open-source agentic RCA with Opsgenie and JSM support). Grafana OnCall OSS was archived in March 2026.
Does Opsgenie support AI-powered root cause analysis?
Standalone Opsgenie is an alerting and on-call product — it does not perform root cause analysis. Atlassian is adding AIOps features (alert grouping, automated resolutions) to JSM and Compass. Teams wanting autonomous multi-step RCA typically pair Opsgenie with a dedicated tool like Aurora, which ingests Opsgenie webhooks and investigates incidents automatically.
What happens to my Opsgenie integrations after migration?
Monitoring integrations (Datadog, New Relic, Prometheus) migrate automatically via Atlassian's in-product tool. Chat integrations (Slack, Microsoft Teams) must be re-authorized manually because the OAuth grants do not transfer. Custom webhooks calling the legacy Opsgenie REST API must be repointed to the new JSM Operations endpoints before April 5, 2027.
Can Aurora connect to Opsgenie and JSM?
Yes. Aurora supports both standalone Opsgenie (GenieKey authentication, US and EU regions) and JSM Operations (Atlassian API token). Aurora ingests alert webhooks, runs AI-powered alert correlation to group related alerts into incidents, and autonomously investigates the root cause. For JSM users, Aurora posts findings back as comments on the linked Jira incident.
Is Jira Service Management cheaper than Opsgenie?
No. JSM Premium is widely reported by Atlassian Community users as more expensive than standalone Opsgenie Standard. Real-time outbound webhooks require JSM Premium, and Incident Command Center requires JSM Enterprise. Many Opsgenie customers see a net price increase after migration, which is why teams use the forced migration to evaluate alternatives.
Related reading: Top 10 AIOps Platforms Offering Free Root Cause Analysis · PagerDuty Alternative: Open-Source Root Cause Analysis · What is Agentic Incident Management? · Open Source Incident Management: Why It Matters
All Opsgenie, JSM, Compass, and alternative-vendor claims verified from official sources in April 2026. Last updated: April 21, 2026.
Originally published on arvoai.ca/blog.
By Team at Arvo AI.
Top comments (0)