Aeion Notifications for Security & Incident Alerting
When production is on fire or a security event is in progress, the notification system is the critical path. Aeion Notifications routes security + incident events through the same engine that handles your transactional sends, with urgent-priority delivery that bypasses quiet hours and native webhook integration into PagerDuty, Opsgenie, Slack, or whatever your team already uses for on-call. It's the alert-routing layer, not a replacement for your on-call scheduling tool — keep PagerDuty/Opsgenie for rotation management and ack tracking; route the notifications themselves through Aeion. Walkthroughs for SaaS production incidents, financial fraud alerts, healthcare clinical alerts.
What Incident Alerting Requires
`
Walkthrough — SaaS Production Incident
`
Walkthrough — Financial Fraud Real-Time Alerting
`
Walkthrough — Healthcare Clinical Alert Routing
`
FAQ
No — Aeion Notifications is the delivery layer (urgent-priority SMS/push/email/webhook). On-call rotation scheduling, escalation-policy timers, ack-tracking, and status pages remain the job of PagerDuty, Opsgenie, or your own tooling. Aeion forwards alerts into them via webhook.
Webhook receiver. Per-alert payload parsing routes to the right notification channel and, optionally, forwards to your incident tool.
Not a native Aeion Notifications feature — manage rotations in PagerDuty/Opsgenie (or your internal tool) and have Aeion deliver into it.
Not supported — Aeion is send-only for SMS (no inbound reply parsing) and doesn't place voice calls. Interactive push notifications with action buttons (Confirm / Dismiss) are supported for cases like fraud confirmation.
Escalation-policy timers live in your incident tool (PagerDuty/Opsgenie), not in Aeion Notifications.
Not a native Aeion Notifications feature today. Webhook out to your existing status-page tool (StatusPage.io, Atlassian) if you want Aeion-triggered updates.
Not part of Aeion Notifications. Pair with your incident-management tool's post-mortem process; Aeion's audit log gives you the delivery timeline as raw input.
Not native to Aeion Notifications — those are incident-tool metrics (time-to-ack, time-to-resolve against the incident record). Aeion's notification_logs give you delivery-side timing (sent/delivered/opened) per alert.
Per-tenant BAA. Per-message PHI redaction. Per-message minimum-necessary. Per-audit-log retention.
PagerDuty is $20-80/user/month for rotation + escalation + status page — you'll likely still want it for those. Aeion Notifications is included free with any module and covers the alert-delivery layer, so the savings come from not needing a PagerDuty seat for every recipient of routine alerts (only the on-call rotation itself needs a seat).
Per-incident lifecycle webhooks (created / ack / resolved). Per-webhook signed payload.