Guide
After Opsgenie: paging for uptime checks.
Opsgenie support ends on 5 April 2027. Vigil replaces it only for teams whose pages come from uptime and endpoint checks. On-call schedules and escalation are Commercial. A stream of alerts from somewhere else needs a different tool.
The dates Atlassian published
These are from Atlassian's Opsgenie licensing page and from what happens when Opsgenie is turned off.
- 4 March 2025: Atlassian announced that Opsgenie would no longer be sold.
- 4 June 2025: end of sale. New purchases stop. Plan upgrades and downgrades stop. Extra seats can still be bought until the end of support, and a renewal is allowed only if the term ends before that date.
- 5 April 2027: end of support. Access is shut off. Customer data that has not been moved to Jira Service Management is deleted.
- If you migrate and do not turn Opsgenie off yourself, Atlassian shuts it down automatically 120 days after the migration date.
- The Opsgenie REST APIs keep working until 5 April 2027. After the product is turned off, only data that was migrated is available in Jira Service Management.
If those pages change, they win. This paragraph is a reading of them, not a second copy Atlassian has to keep.
Two different replacements
The useful split is where the alert comes from.
If the alerts are produced by Alertmanager, Grafana, or another system that posts events into Opsgenie, you need something that accepts those events, routes them and runs on-call. Atlassian's own path is Jira Service Management. GoAlert is the self-hosted tool people use in front of Alertmanager. Vigil does not ingest those alerts. It has no Opsgenie-compatible API, and it will not import an Opsgenie schedule. Pointing it at that job would leave the alerts with nowhere to land.
If Opsgenie was mostly paging because a URL, a port, a certificate or a heartbeat had failed, the check and the page can live in one product. That is the case this page is about.
What you get in that second case
Vigil Core runs the checks, opens an incident when the failure window has elapsed, resolves it when a later check passes, and notifies the channels you configure. Core has no on-call schedule and no escalation ladder. Acknowledgement is stored on the incident, and nothing further happens because of it.
Commercial adds the on-call half for those same checks:
- Schedules, and an escalation ladder. Each rung checks the incident again. Acknowledgement or resolution stops the rest. The escalation page has the detail.
- Email without an extra account. SMS and voice through a Twilio account you supply. Vigil does not resell the messages.
- Maintenance windows, so a planned silence does not page and does not fire a restart hook.
- Status pages and the incident record in the same install.
The licence is $149 once per company, not per responder seat. Opsgenie counts responder users. That is a pricing difference, not a claim that the products do the same work.
What this does not cover
- Alerts that do not come from a Vigil check.
- A migration of Opsgenie configuration, schedules, or alert history. You recreate the monitors and the rota.
- SSO. It is not in the product.
- A hosted on-call cloud. You run Vigil on a server you supply.
If most of the rotation is "the endpoint is down", start with the quick start, read pricing before you pay for the ladder, and use the escalation screen in the tour to see the shape of a policy. If most of the rotation is other people's alerts, pick the on-call product that accepts them and leave Vigil out of that path.
Vigil and Uptime Kuma is the comparison if the thing you are leaving is a monitor rather than a pager.