Opsgenie ends on 5 April 2027. Map it before you move.
Atlassian stopped selling Opsgenie on 4 June 2025 and shuts it down on 5 April 2027, deleting unmigrated data. Small teams that used it to route monitoring alerts can move to Vigil: Opsgenie heartbeats become Vigil heartbeat URLs, incoming alerts go to a Vigil ingest URL, and schedules become rotations with overrides. Phone and SMS paging is the part that does not carry over on hosted Vigil.
Free plan: 20 monitors at 5-minute checks, commercial use allowed, no card. New accounts also get a 14-day trial of a paid plan.
Timeline
- 4 June 2025: end of sale. No new Opsgenie purchases, upgrades or downgrades.
- 5 April 2027: end of support. Opsgenie is shut down and data that was not migrated is deleted.
- Atlassian's own paths are Jira Service Management and Compass (Atlassian migration page, read September 2026). If your team lives in Jira or needs phone paging, that is the easy move. This page is for small teams that mainly used Opsgenie to route monitoring alerts.
Opsgenie → Vigil mapping
| Opsgenie | In Vigil | Notes |
|---|---|---|
| Heartbeats (a job pings Opsgenie on an interval) | Heartbeat monitor | Each heartbeat gets its own URL: https://puzaricloud.in/ping/<token>. GET, POST or HEAD, no API key header. Add /start, /fail or /<exit code>; the POST body is kept as the run's log. Period or cron schedule with a grace time. |
| Integrations that create alerts (Prometheus, Grafana, API) | Alert ingestion URL | POST https://puzaricloud.in/ingest/<token> accepts Alertmanager, Grafana and generic JSON (title, description, severity, status firing/resolved, a dedup id). It is not the Opsgenie Alert API format, so point each sender at the new URL. |
| Uptime checks you sent into Opsgenie from another tool | Vigil monitors | Vigil runs the checks itself (HTTP, API assertions, TCP, DNS, SSL, domains, cron), so the middle tool can go. |
| On-call schedules, rotations, overrides | On-call rotations | Layered rotations with handoffs, time windows (follow-the-sun), overrides and an ICS feed per schedule. |
| Escalation policies | Escalation | If an incident is not acknowledged within N minutes, a second set of channels is alerted. Simpler than Opsgenie's multi-step policies. |
| Acknowledge / close | Acknowledge / resolve | From the app, the alert's chat buttons (Slack, Teams) or the API. |
| Teams and routing rules | Teams + per-monitor channels | Monitors belong to a team and alert that team's channels. |
| Maintenance | Maintenance windows | One-off, daily or weekly, by monitor or tag; alerts are silenced and status pages show the window. |
| Mobile app push | Web Push (installable app) | Install Vigil as a PWA on Android or iOS for push alerts; Pushover, ntfy and Telegram work too. |
| Phone calls and SMS | Not on hosted Vigil | The self-hosted edition can call and text through your own Twilio account. If phone paging is essential, look at Jira Service Management or PagerDuty. |
Migration checklist
- Export what you need to keep from Opsgenie (alert history, schedules) before 5 April 2027.
- Create a free Vigil account and rebuild your rotations and overrides under On-call.
- For every Opsgenie heartbeat, create a Vigil heartbeat with the same period and grace, and swap the URL in the job (
curl -fsS -m 10 https://puzaricloud.in/ping/<token>). - Create an ingest source per alert sender and change its webhook URL; send a test alert from each.
- Run both for a week, then switch Opsgenie off. If you also used another uptime tool, the importer moves UptimeRobot, Better Stack, Uptime Kuma and URL lists.
Questions
Is there an automatic Opsgenie importer?
No. Vigil imports monitors from UptimeRobot, Better Stack, Uptime Kuma, Statuspage and URL lists, but schedules and heartbeats from Opsgenie are recreated by hand. For a small team that is usually under an hour.
Can on-call people get woken at night?
Through push (installed app, Pushover with emergency priority, ntfy), Telegram, WhatsApp or Slack. Hosted Vigil makes no phone calls; if that is a requirement, keep a paging tool and send it Vigil's alerts by webhook.
Before you switch: honest limits
- Vigil's checks run from one location (Hetzner, Germany) plus any private locations you install; there is no multi-region confirmation yet. Every failure is re-checked after 12 seconds before it counts.
- Hosted Vigil does not make phone calls or send SMS. WhatsApp alerts go through CallMeBot and suit personal use.
- Fastest interval is 1 minute (5 minutes on Free).
Feature-by-feature: Opsgenie alternative · Vigil vs Opsgenie · Other switching guides: UptimeRobot · Freshping · Uptime Kuma