Opsgenie and OpsPing are both paging-first on-call tools: schedules, rotations, escalations, and an alert API. The difference is status and packaging. Opsgenie support ends April 5, 2027, with permanent data deletion. OpsPing is actively developed, accepts a documented subset of the Opsgenie Alert API v2 (same JSON shape and GenieKey header, new base URL and key), and imports users, teams, schedules, escalations, heartbeats, and integrations. Pricing is per responder, with unlimited push and unlimited stakeholder seats free on every plan. If you need a service desk rather than a pager, compare the Atlassian JSM path separately.
Feature parity
| OpsPing | Opsgenie | |
|---|---|---|
| Status | Live and shipping | Shut down April 5, 2027 — permanent data deletion |
| On-call scheduling | Yes, every plan (Free: 1 schedule; Team and Business: unlimited, with rotations, overrides, and PTO) | Yes, until shutdown |
| Escalation policies | Single-level on Free; unlimited multi-level on Team and Business | Yes, until shutdown |
| Heartbeat monitoring | Included on Team and Business; pings are POST only | Yes, until shutdown (GET, PUT, and PATCH pings also accepted) |
| Alert API | Opsgenie v2-compatible documented subset, GenieKey auth | v2 alert API (the reference) |
| Who pays for stakeholders? | Unlimited, free on every plan | Opsgenie offered a non-paging stakeholder role; confirm pricing on your existing plan (new sales ended June 4, 2025) |
| Push delivery | iOS Critical Alerts, Android DND-bypass alarms, per-severity sounds; unlimited on every plan | Mobile push with known silent-mode failures on Android |
| Voice and email | Paid-plan fallback, subject to channel availability | Yes, until shutdown |
| Status pages | Included on Team and Business | Required Atlassian Statuspage separately |
| Postmortems | One-click from the audit trail, Markdown and PDF | Not native (incident timeline only) |
| Private deployment | Private single-tenant deployments available | Opsgenie Edge (legacy on-prem agent) |
Cost
OpsPing is mid-range, per-responder pricing: Free for up to 5 responders; Team at $15/responder/month or $12 billed annually; Business at $25 or $20 billed annually, self-serve up to 100 responders. Push is unlimited, and stakeholder seats are unlimited and free, on every plan. Opsgenie switchers get 35% off the first annual term if redeemed by April 5, 2027 — $7.80/responder/month on Team and $13.00 on Business.
Opsgenie is no longer sold to new customers (end of sale June 4, 2025). Existing-customer list rates, banded by seat count, are in the on-call cost calculator (Essentials, Standard, and Enterprise). A related cost of the Atlassian path: heartbeat monitoring is listed under Service Collection Premium on Atlassian's pricing page (checked November 16, 2026), while OpsPing includes heartbeats on Team.
OpsPing prices as of November 16, 2026, from opsping.com/pricing. Opsgenie new sales ended June 4, 2025 (atlassian.com).
API compatibility
The practical difference for most alert sources is the host and the key. OpsPing accepts the Opsgenie v2 JSON body and the Authorization: GenieKey <key> header at https://api.opsping.com (or your private deployment). Use a new OpsPing API key; the Opsgenie key will not work. Alertmanager and Grafana can keep auto-resolve on, because OpsPing closes alerts by alias.
It is a documented subset, not a complete replica of every Opsgenie route:
- Create, get, acknowledge, close, notes, tags, assign, responders, escalate, snooze, details, and priority updates work by alert ID, tiny ID, or alias (
identifierType=alias) where supported. - Only
GET /v2/alerts/counts(plural) applies alias or status filters;GET /v2/alerts/countis an unfiltered count. - Unacknowledge, unassign, reopen, unsnooze, mark-read, and delete are not available by alias — they take the alert ID returned on create, or the numeric tiny ID.
- Priority changes do not re-run alert policies or escalation; request-status polling is unavailable. List queries understand
alias:andstatus:tokens, not the full Opsgenie query language. - Heartbeat ping accepts GET, POST, PUT and PATCH. Schedules, teams, and policies use OpsPing-native API schemas. Import them rather than replaying Opsgenie configuration calls.
The full endpoint and field list is on the Opsgenie-compatible alert API page.
Migration steps
This is the OpsPing-specific cutover. The migration guide covers the importer wizard, and Switch from Opsgenie is the narrative walkthrough.
- Export history now. Alert history, incidents, and audit logs are not imported. Atlassian deletes unmigrated data on April 5, 2027. Keep that archive separately.
- Dry-run the importer. It is free. Review users, teams, services, schedules and overrides, escalation policies, heartbeats, and integrations. Routing, policies, notifications, and maintenance are review-gated. Terraform configuration resources and some forwarding-rule specifics are not drop-in.
- Apply the plan on Team or Business after you have reviewed it.
- Repoint integrations. Change the base URL to
https://api.opsping.comand put a new OpsPing key in the existingGenieKeyheader. Heartbeat cron jobs can retain their GET, POST, PUT or PATCH ping method; all four verbs are accepted. The curl before-and-after is in Moving your Opsgenie heartbeats. - Verify. Send one firing and one resolution through every path, and confirm alias close, priority, and responder delivery.
- Cut over once those checks pass. Install the OpsPing mobile app and enable push (iOS Critical Alerts and Android DND bypass) before you retire the Opsgenie rotation.
FAQ
Is OpsPing really API-compatible with Opsgenie?
For the alert API, yes for the documented subset: create with alias deduplication, get by alias and the common actions (acknowledge, close, notes, tags, assign, responders, escalate, snooze, details) by alert ID, tiny ID or alias (identifierType=alias), alias: and status: list-query tokens, the v2 alert JSON shape, and the GenieKey auth header. Unacknowledge, unassign, reopen, unsnooze, mark-read and delete still use the alert ID, which OpsPing returns as alertId when the alert is created, or the tiny ID. Configuration APIs (schedules, teams, policies) exist in OpsPing but are not schema-identical, so scripts need review. The migration guide has a per-endpoint compatibility reference.
How does OpsPing pricing compare with Opsgenie?
OpsPing Team is $15/responder/month ($12 billed annually) and Business is $25 ($20 billed annually), with unlimited push and unlimited stakeholder seats free on every plan. Opsgenie switchers get 35% off the first annual term if redeemed by April 5, 2027 — $7.80/responder/month on Team and $13.00 on Business. Opsgenie is no longer sold; existing-customer list rates are in the on-call cost calculator. Heartbeats are included on OpsPing Team; Atlassian lists JSM heartbeat monitoring under Service Collection Premium.
What are the steps to move from Opsgenie to OpsPing?
Export alert history, incidents, and audit logs from Opsgenie first. Run a free importer dry run, review the plan, and apply it on Team or Business. Repoint each integration to https://api.opsping.com with a new OpsPing key (GenieKey header syntax still works), send a firing and a resolution through every path, then cut over. The migration guide walks through the wizard in detail.
Can OpsPing run where Opsgenie Edge ran?
In the sense that matters — on-prem ingestion — OpsPing offers private single-tenant deployments (a single static Go binary plus PostgreSQL) on your infrastructure or managed by us. The legacy Edge agent itself has no equivalent and is not needed.