OpsGenie users loved its focused simplicity for on-call management; alternatives like PagerDuty are expensive and JSM is bloated with Jira overhead.
A lightweight on-call scheduling and alert routing platform with an OpsGenie-compatible API, easy one-click import from OpsGenie exports, and pricing that undercuts PagerDuty.
Freemium: free for up to 5 users, $9/user/mo after that
This is not hypothetical pain — it's a forced migration with a hard deadline (April 2026). OpsGenie users are being kicked off a product they love. Reddit threads show genuine frustration: teams don't want JSM's bloat or PagerDuty's pricing. The pain is acute, time-bound, and already driving active searches for alternatives.
OpsGenie had an estimated 15,000+ paying teams. Even capturing 2-5% of displaced users at $9/user/mo with average 8-person teams would yield $1-3M ARR. The broader SMB on-call market adds more TAM beyond OpsGenie refugees. Not a billion-dollar market for this positioning, but solid for a bootstrapped/small-team business.
These teams were ALREADY paying for OpsGenie ($9-$29/user/mo). They have budget allocated. On-call is mission-critical infrastructure — nobody wants free-tier reliability for their production alerting. $9/user/month is positioned well below PagerDuty ($21+) and at or below what they were already paying. Price sensitivity exists but WTP is proven.
Core on-call scheduling and alert routing is buildable in 4-8 weeks. BUT: reliable multi-channel alerting (phone calls, SMS, push notifications) requires telephony infrastructure (Twilio), which adds cost and complexity. OpsGenie-compatible API is ambitious for an MVP. The hard part isn't the scheduling UI — it's the 99.99% reliable alert delivery pipeline that wakes people up at 3 AM. A solo dev can build an MVP, but 'production-grade alerting reliability' is the real challenge.
No competitor is specifically targeting OpsGenie refugees with migration tooling and API compatibility. Spike.sh is closest in simplicity but lacks the migration story. PagerDuty is too expensive. Grafana OnCall requires buying into the Grafana ecosystem. The 'one-click OpsGenie import + compatible API' positioning is genuinely unoccupied. This is the strongest differentiator.
On-call is inherently recurring — teams need it every single day, forever. Once schedules, escalation policies, and integrations are configured, switching cost is high. Churn should be very low if the product works reliably. This is textbook infrastructure SaaS with strong retention characteristics.
- +Rare forced-migration event creates a time-bound acquisition window with thousands of teams actively looking for alternatives right now
- +OpsGenie-compatible API and one-click import is a genuinely unoccupied niche — no competitor is doing this
- +Proven willingness to pay: these users already had budget for exactly this type of tool
- +Strong retention dynamics: on-call tooling is sticky infrastructure with high switching costs
- +Undercut pricing ($9/user) vs PagerDuty ($21+) is a clear, easy-to-communicate value prop
- !Reliability is table stakes: a single missed alert at 3 AM destroys trust permanently — you need rock-solid infrastructure from day one
- !Telephony costs (Twilio SMS/voice) can eat margins significantly at $9/user/month, especially for high-alert-volume teams
- !The migration window is time-sensitive — if you don't ship before April 2026 deadline, the urgency evaporates as teams settle elsewhere
- !Atlassian could extend OpsGenie's life or improve JSM migration, shrinking the displacement pool
- !Spike.sh, Squadcast, or even Grafana OnCall could ship OpsGenie migration tooling and steal the narrative
Enterprise-grade incident management platform with on-call scheduling, alert routing, event intelligence, and AIOps capabilities.
Open-source on-call management tool by Grafana Labs, integrates tightly with the Grafana observability stack. Available as self-hosted or Grafana Cloud.
Lightweight incident alerting and on-call scheduling tool targeting small teams, with phone/SMS/Slack/email notifications.
Incident management and on-call platform with SRE workflows, alert routing, postmortems, and runbooks.
Combined uptime monitoring and on-call incident management platform with status pages.
Week 1-2: On-call schedule builder with rotation support + Twilio-based phone/SMS/email alerting. Week 3-4: OpsGenie export JSON importer (schedules, teams, escalation policies). Week 5-6: Alert routing rules, basic integrations (Datadog, Prometheus/Alertmanager, Slack webhooks), and a clean dashboard. Week 7-8: OpsGenie-compatible REST API for the most-used endpoints so existing integrations 'just work'. Skip: postmortems, runbooks, AIOps, status pages — those are v2 features.
Free tier (up to 5 users, community support) to establish trust and capture small teams -> $9/user/month Pro tier (unlimited users, phone/SMS alerts, priority support) -> $15/user/month Business tier later (SSO/SAML, audit logs, SLA guarantees, advanced analytics). Upsell path: charge per additional phone/SMS alert beyond monthly quota to protect telephony margins.
4-6 weeks to MVP, first paying customers within 6-8 weeks if you launch before or right at OpsGenie's April 2026 read-only deadline. The urgency is NOW — every week of delay reduces the displacement advantage. Post on r/devops, HN, and DevOps Twitter with 'We built the OpsGenie replacement you actually want' and conversions should be fast given the active pain.
- “One of the best tools for on-call incident management in my opinion”
- “It's sad that the product will be sunset soon”
- “It is very much like OpsGenie for my usage”