PocketNOC vs Opsgenie for SolarWinds Orion on-call teams

Last updated: 2026-06-29

Opsgenie routes the page to whoever is on call. PocketNOC is what that engineer opens in Orion to see what is actually broken. They work in the same workflow at different layers — and Opsgenie is shutting down in April 2027.

Summary

Opsgenie is an on-call management and alert routing platform from Atlassian. PocketNOC is a native iOS and Android app that reads SolarWinds Orion node health, alerts, and performance data on a phone. They serve adjacent problems: Opsgenie decides who gets paged and ensures the page gets through; PocketNOC is what that engineer opens to see what is actually broken without needing a laptop. One major change to be aware of: Atlassian stopped selling Opsgenie on June 4, 2025. The platform shuts off on April 5, 2027. Teams currently running Opsgenie need a migration plan. The mobile Orion-viewing layer that PocketNOC fills is unaffected by that transition.

When PocketNOC fits

• Your team already runs SolarWinds Orion (NPM, SAM, NTA, NCM, IPAM, or DPA) and needs phone-native access to the data Orion collects, without opening a browser or a laptop.
• An on-call engineer gets paged at 3am and needs to see which node is down, what the performance chart looked like in the minutes before the failure, and whether related nodes are also affected.
• You want to acknowledge an Orion alert directly from the phone, writing the acknowledgment back via the SWIS API.
• Monitoring data must stay inside your network. PocketNOC calls your Orion SWIS API from the device. Nothing passes through an external cloud service for the monitoring path.
• Your Orion server uses a self-signed certificate. PocketNOC supports Trust On First Use on the initial connection, with no changes to your internal CA.

When Opsgenie fits

• You need a structured on-call rotation calendar with escalation policies: if the primary engineer does not acknowledge within N minutes, page the secondary.
• Your alerts come from multiple systems (Orion, Datadog, AWS CloudWatch, a custom webhook source) and need to route through a single on-call schedule.
• You need guaranteed page delivery with override-DND behavior: push notifications that ring through silent mode and re-alert until acknowledged.
• You are already on the Atlassian stack (Jira, Confluence) and want incident management wired into your ITSM workflow.
• You are an existing Opsgenie customer who has not yet started planning a migration.

One note: Opsgenie is no longer available for purchase (new sales ended June 4, 2025) and the platform shuts off April 5, 2027. Teams evaluating new on-call tools today should look at Jira Service Management (Atlassian's designated successor), PagerDuty, incident.io, or Squadcast (acquired by SolarWinds, March 2025). The on-call routing layer is what needs replacing. The monitoring-viewer layer PocketNOC fills is separate.

Side-by-side

Opsgenie pricing figures sourced from SaaSworthy and TrustRadius (June 2026). The Atlassian pricing page was unreachable from this environment on draft date 2026-06-29 (HTTP 403); verify current figures before citing in external documents.

Real-world workflow notes

The standard pattern for a SolarWinds on-call team using Opsgenie has always been: Orion fires an alert and uses its "Send a Post Request to a Web Server" action to push the alert payload to Opsgenie's ingest endpoint. Opsgenie routes the page to whoever is currently on the rotation schedule, using whatever escalation policy applies. Orion handles the monitoring; Opsgenie handles the who-gets-woken-up logic. PocketNOC enters the workflow at the point where the engineer is awake and holding their phone. Opening PocketNOC shows the affected node, the performance chart leading up to the failure, related alerts, and interface or application data from whatever Orion modules are licensed. The engineer can acknowledge the Orion alert from inside the app without touching a laptop.

The Opsgenie shutdown does not change the Orion-to-phone investigation step. Any on-call routing tool that delivers the page to the engineer substitutes for Opsgenie at the top of the chain. PagerDuty, incident.io, Squadcast, and Jira Service Management all accept Orion webhooks or email alert triggers, and the setup in Orion is similar regardless of which tool receives the POST. Once the page is delivered, PocketNOC reads the same SWIS API it always did. The engineer's investigation workflow is identical.

Teams currently on Opsgenie and planning the April 2027 migration should audit their Orion integration configuration, specifically the bidirectional acknowledgment path. The OEC (Opsgenie Edge Connector) that writes acknowledgments back to NPM will need a replacement at the destination tool. Most alternatives support a comparable callback mechanism, but the setup differs. PocketNOC handles Orion acknowledgment from the device independently of the upstream alert routing platform, so that part of the workflow transfers without changes. For a comparison of PocketNOC with the built-in Orion browser alternative for mobile access, see PocketNOC vs the Orion Web Console mobile view. For context on the on-call paging category and how PocketNOC sits alongside dedicated paging tools, see PocketNOC vs OnPage for SolarWinds Orion.

FAQ

Is PocketNOC a replacement for Opsgenie?

No. Opsgenie manages on-call rotation, escalation policies, and delivers the page with override-DND urgency. PocketNOC is a mobile viewer for SolarWinds Orion data. They sit at different layers of the same workflow: Opsgenie gets the alert to the right engineer, PocketNOC shows that engineer what is broken without requiring a laptop. You need both a routing layer and a monitoring-viewer layer. PocketNOC is the viewing layer; it is not a scheduling or paging tool.

Is Opsgenie shutting down?

Yes. Atlassian stopped selling Opsgenie on June 4, 2025. Existing customers retain access until the platform turns off on April 5, 2027. Atlassian is directing Opsgenie users toward Jira Service Management (JSM) for the on-call scheduling, escalation, and alerting functionality. Customers using JSM-bundled Opsgenie features may lose access sooner, by October 2025, based on Atlassian's transition schedule.

What replaces Opsgenie for SolarWinds Orion teams?

SolarWinds acquired Squadcast in March 2025 and is positioning it as a native incident response layer for SolarWinds Observability. For teams running standalone Orion (NPM, SAM, NCM), common replacement paths include PagerDuty, incident.io, and Jira Service Management. All of them accept Orion webhook pushes or email-based alert triggers. PocketNOC is not a replacement for the routing layer. It handles the mobile Orion-viewing step after the page is delivered, and that step works the same regardless of which paging tool you migrate to.

How does Opsgenie connect to SolarWinds NPM?

SolarWinds NPM uses its "Send a Post Request to a Web Server" alert action to push a webhook payload to Opsgenie's ingest endpoint when an alert fires. The Opsgenie Edge Connector (OEC) enables bidirectional acknowledgment: confirming an alert in Opsgenie writes the acknowledgment back to NPM automatically by running a script inside OEC. Opsgenie never reads SWIS directly. It only receives the outbound push from Orion's alert engine and routes from there.

Can I use both PocketNOC and a replacement on-call tool?

Yes, and the workflow is identical to what it was with Opsgenie. The routing tool delivers the alert to whoever is on call. PocketNOC is what they open on their phone to see Orion node health, performance charts, and alert history without booting a laptop. PocketNOC connects directly to your Orion SWIS API from the device and has no dependency on the upstream alert platform.

Does Opsgenie need access to my Orion server?

No. The integration is push-only from Orion. SolarWinds NPM sends a POST to Opsgenie's HTTPS ingest endpoint when an alert fires. Opsgenie receives the alert text and metadata in that payload. It does not query SWIS, read node health, or access performance charts or configuration data. PocketNOC fills exactly that gap: Opsgenie knows an alert fired on a specific node, PocketNOC shows you what that node looks like right now.

What does PocketNOC cost?

Free tier is demo mode with sample data, useful for evaluating the interface before connecting to a live Orion server. Pro is $99.99 per year or $9.99 per month per device (pocketnoc.weavehub.app), billed through the App Store or Google Play. There is no per-user charge on the monitoring data path. One active device license covers one on-call engineer's phone.

Conclusion

Opsgenie and PocketNOC occupied different layers of the same on-call workflow: Opsgenie decided who got paged, PocketNOC showed that person what was broken in Orion. With Opsgenie heading toward its April 2027 shutdown, teams need a replacement routing tool, but the mobile Orion-viewing layer PocketNOC provides works identically with any paging platform upstream. Install the app, point it at your Orion server, and the investigation workflow from a phone stays the same regardless of what delivers the initial page.