Opsgenie is not disappearing tomorrow, but the clock is real. Atlassian stopped selling it to new customers on June 4, 2025, and will shut it off entirely on April 5, 2027, at which point any unmigrated data gets deleted. Existing accounts keep working without interruption in the meantime, and can still add seats or renew as long as the term ends before that date. That gives most teams a real planning window rather than a scramble, but it also means every new on-call rotation or escalation policy built in Opsgenie today is being built on a product with a fixed end date. Below is what Opsgenie still costs right now, what actually happens to your alerts, schedules and integrations when you move off it, and where ObserveOne fits and does not fit in that picture.
Atlassian never stopped charging for Opsgenie, it only stopped selling new accounts. Existing customers still see a full, current self-serve price list. Pulled from atlassian.com/software/opsgenie/pricing on September 20, 2026:
| Plan | Price | Detail |
|---|---|---|
| Free | $0/mo | Up to 5 users. Unlimited alerts, email and push notifications, 100 SMS notifications account-wide. One routing rule maximum. |
| Essentials | $9.45/user/mo billed annually, or $11.55/mo month-to-month | Unlimited alerting for a small team. Still one routing rule maximum, 100 incidents a month account-wide, six months of data retention. |
| Standard | $19.95/user/mo billed annually, or $24.15/mo month-to-month | Unlimited incidents, up to 100 routing rules per team, unlimited SMS and voice notifications, one year of data retention. Where most paying teams sit. |
| Enterprise | $31.90/user/mo billed annually, or $38.50/mo month-to-month | Adds 24/7 email and phone support, unlimited data retention, advanced incident analysis, and HIPAA compliance options. |
A ten-person on-call rotation on Standard runs about $200/mo billed annually before any add-on minutes or numbers. That number is not going away on its own: Atlassian's own FAQ confirms existing customers can keep buying seats and renewing this same plan right up until a term that ends before the April 5, 2027 end-of-support date. The reason to move is the fixed shutdown date, not a looming price change.
Source: atlassian.com/software/opsgenie/pricing, fetched September 20, 2026.
Atlassian's own answer for where Opsgenie goes is Jira Service Management, reached through an in-app automated migration tool (Settings > Products > Move from Opsgenie) that lets you pick a cutover date and run both products in parallel for up to 120 days before switching off the old one. Per Atlassian's own feature-by-feature migration guide, most of a working setup carries over on its own, but not all of it:
Auto-synced with no manual work: alerts, on-call schedules, escalation policies (up to 300 per team with 50 rules each on the migrated plan), notification rules, and quiet hours all move over as-is. This is the part of Opsgenie most teams care about most, and it is also the part Atlassian's guide says needs the least attention.
Incoming integrations auto-sync, but anything connecting to an on-prem system through the Opsgenie Edge Connector has to be rebuilt as a Jira Edge Connector, and Slack, Microsoft Teams and Zoom integrations need to be re-authenticated after the move rather than carrying credentials over.
Atlassian's own deprecation list is specific: Incident Command Center, conference rooms, response roles and email templates are all replaced by Jira Service Management's Incident Configurations rather than migrated as-is. Global notification policies have to be manually converted to team-based ones before the account moves, or they are dropped rather than carried forward. MSP sub-accounts lose the Opsgenie-to-Opsgenie link entirely and each becomes its own free account needing a separate migration.
None of the above is about what triggers an alert in the first place, it is about what happens once one fires. Whatever monitors your login page, checkout flow or API endpoints and decides something is actually down still has to exist somewhere, whether that is Jira Service Management's own monitoring, a dedicated on-call tool, or a synthetic monitoring layer like ObserveOne feeding alerts into whichever of those you land on.
Ranked by how closely each one replaces Opsgenie. Every row links to a full side-by-side breakdown.
| Tool | Best for | Pricing | Comparison |
|---|---|---|---|
1 ObserveOneAI-powered synthetic monitoring and self-healing test automation | AI-First QA Teams | Free tier available, paid plans from $6/mo | vs Opsgenie |
2 PagerDutyDigital operations management and incident response | DevOps Teams | Free (5 users), Pro $21/user/mo, Business $41/user/mo (+ Add-ons) | vs Opsgenie |
3 Atlassian StatuspageCommunicate incidents and build trust with status pages | DevOps Teams | Free (100 subs), Hobby $29/mo, Startup $99/mo, Business $399/mo | vs Opsgenie |
4 New RelicObservability platform for every engineer | Developers | 100 GB/mo free data ingest, $0.40/GB beyond. Standard from $10/mo/user, Pro from $349/user/mo | vs Opsgenie |
5 PingdomWebsite performance and uptime monitoring | Web Developers | Synthetic from $16.5/mo, RUM from $16.5/mo (100k pageviews) | vs Opsgenie |
6 GrafanaOpen-source observability and data visualization | Engineers | Open source free, Cloud from $0 (scalable usage-based) | vs Opsgenie |
7 UptimeRobotFree uptime monitoring for websites | Freelancers | Free (non-commercial, 50 monitors), Solo $10/mo ($9 billed annually), Team $41/mo ($35 billed annually) | vs Opsgenie |
8 PrometheusOpen-source metrics monitoring and alerting toolkit | DevOps | Free and open source | vs Opsgenie |
9 Better StackUptime monitoring, incident management and status pages | DevOps Teams | Free tier, paid from $29/responder/mo (billed annually, $34 monthly) | vs Opsgenie |
10 StatusCakeWebsite uptime, performance and SSL monitoring | Small Businesses | Free tier, Superior $24.49/mo ($20.41 billed annually), Business $79.99/mo ($66.66 billed annually) | vs Opsgenie |
This one is worth being direct about. ObserveOne has no on-call scheduling, no escalation policies, no ChatOps paging, and no incident command workflow, which is the actual job Opsgenie does and the reason people pay for it. That job does not disappear when Opsgenie does; it moves to Jira Service Management by default, or to a dedicated on-call tool if a team wants to stay out of the Atlassian ecosystem entirely. What ObserveOne does is sit in front of that decision: scheduled browser, API, uptime and SSL checks that run the same steps a real user would and raise the alert in the first place. A team migrating off Opsgenie still needs somewhere for the on-call and escalation side to live. ObserveOne is not that place, it is the thing that decides when to wake someone up.
Yes, on a fixed timeline. Atlassian stopped selling new Opsgenie accounts on June 4, 2025, and will shut off access entirely on April 5, 2027, deleting any data left unmigrated at that point. Existing customers keep full access without interruption until then, and can still buy additional seats or renew as long as the term ends before the shutdown date.
Atlassian's own supported path is Jira Service Management, reached through an automated in-app migration tool that lets you run both products in parallel for up to 120 days before cutting over. Alerts, schedules and escalations carry over automatically; a handful of features (Incident Command Center, conference rooms, response roles, MSP sub-accounts) are deprecated rather than migrated and get replaced by newer Jira Service Management equivalents.
No, and it is worth being clear about that rather than overselling it. ObserveOne has no on-call scheduling, escalation policies or paging of its own. It runs the synthetic checks that decide something is actually broken, then hands that alert to whatever on-call tool a team lands on after the Opsgenie migration, which is usually Jira Service Management.
Existing customers still pay the same current price list: Free for up to 5 users, Essentials at $9.45/user/mo, Standard at $19.95/user/mo, and Enterprise at $31.90/user/mo, all billed annually per atlassian.com/software/opsgenie/pricing. Nothing about the shutdown timeline changes those prices before the April 5, 2027 end-of-support date.
If the on-call and escalation side of this is already sorted, or handled through Atlassian's own migration tool, the open question is usually what is actually watching production to trigger those alerts. Point ObserveOne at the handful of flows that matter most and wire its alerts into whichever incident tool comes out of the Opsgenie migration.
Check your site free, no signup