Opsgenie is going away. Plan your migration calmly.
Atlassian is retiring Opsgenie and Grafana OnCall has been archived. Thousands of teams need a new on-call tool. inalarm takes over your escalation rules, channels and incident history - with EU hosting and straightforward billing.
Opsgenie: sales end
Atlassian stops selling Opsgenie to new customers and steers them toward Jira Service Management.
Opsgenie: end of life (EOL)
The product is fully retired. Teams have to pick a new on-call tool - this is a migration, not a \"maybe someday\".
Grafana OnCall archived
A popular free self-hosted option is stepping back. More teams are looking for an Opsgenie alternative.
Opsgenie migration is not \"maybe someday\" - it is a date on the calendar
After April 5, 2027 Opsgenie stops working. This is not a feature freeze but a hard end: escalation rules, integrations and rotations need a new home before they stop waking people up at night. The earlier you start the migration, the less you risk an incident falling into the void.
Most global alternatives share two problems: they charge per account user rather than per person actually on call, and they bill in dollars without local invoicing or same-timezone support. For many teams that means a higher bill and slower help in a different time zone.
inalarm was built as a straightforward answer: the same escalation model the on-call leaders use, alerts over SMS, e-mail, Slack and the app, ingestion via webhook, API and connectors, and pay-per-responder pricing. We host in the EU and we are honest about what is not ready yet - those parts are clearly marked as planned.
An Opsgenie equivalent, cheaper and closer
Rules, acknowledgements and history work from day one. Features that are not there yet carry a \"soon\" badge - so your migration does not rest on promises.
Escalation rules and time steps
The equivalent of Opsgenie escalation policies: condition, priority and path - after X minutes without a response the alert moves up.
Acknowledge and take over
\"I've got this\" stops the escalation in one click, and a teammate can take the incident over at any time.
Alerts from anywhere
Webhook, API and connectors - plug in monitoring, uptime, CI or your own system just like you did with Opsgenie.
Notification channels
App, e-mail and Slack with no limit, SMS as a channel on Team and up. It reaches wherever it needs to wake someone.
Pay per responder
You pay only for people on call, not for every head on the account. The rest of the team uses it for free.
EU hosting and support
Data hosted in the EU and support in your own time zone, close to your team rather than an ocean away.
On-call schedules and rotations soon
Shift schedules, rotations and cover instead of pinning a single person. We are working on it.
Wake-up phone call and push soon
A voice call with keypad confirmation and push that bypasses \"do not disturb\" mode. In the works.
Slack as the incident hub soon
Running the whole incident inside a Slack channel, not just a notification. For now Slack works as an alert channel.
From Opsgenie to inalarm in four steps
You do not have to move everything at once. Recreate the rules, repoint the alerts and switch over team by team.
List your Opsgenie rules
Export the escalation policies, schedules and integrations that wake your team today.
Recreate the escalations
Move conditions and time steps into inalarm rules one to one, together with channels and acknowledgements.
Repoint the alerts
Send webhooks from monitoring and CI to inalarm the same way they pointed at Opsgenie.
Test and switch
Fire a test incident, check the channels and switch production over. History records every step for audit.
You have time to migrate before Opsgenie goes dark.
Start free in minutes. No card, no limit on team size - you only pay for responders.