NOCgenie ingests alerts from every monitoring system, deduplicates and routes them to the right responder by schedule and escalation policy, and keeps paging across SMS, voice, push, Slack, Teams and email until someone owns it.
<5s from accepted webhook to first page · feature-parity with Opsgenie workflows
Built feature-for-feature so your runbooks, integrations and rotations come across intact.
Deduplicate by alias, auto-close on recovery, correlate and enrich. Retried, idempotent webhooks — no double-pages, no dropped alerts.
Layered rotations, follow-the-sun, one-off overrides, timezone- and DST-correct. "Who's on call now?" plus an iCal feed for every team.
Multi-step, time-based policies that escalate to the next person, team or schedule — and survive worker restarts because timers are persisted.
Per-user rules with staggered delays, quiet hours that P1 can override, maintenance windows and storm-collapse so people aren't flooded.
Dead-man's-switch monitoring: if a job stops pinging, NOCgenie pages you. Because the thing that watches prod has to watch itself.
Entra ID / OIDC single sign-on, role-based access, scoped API tokens, and a full REST API — the UI is just another client.
Degrade gracefully — if Slack is down, the SMS still goes out.
Two-way Slack & Teams — acknowledge or close right from the message.
First-class parsers for what NOC teams actually run.
Import users, teams, schedules, escalations and integrations directly from your Opsgenie export. Run both systems in parallel and diff the routing decisions until you're confident — then cut over.
One command pulls your Opsgenie config into NOCgenie.
Both systems get the same alerts; compare routing in a diff report.
Flip integrations across when parity hits 100%.
webhook → parse → dedupe / auto-close → route (rule → policy)
→ escalate (schedule on-call → next person → team)
→ notify (push now · SMS +2m · call +5m) until acked
Sign in to your workspace and route your first alert.