Skip to main content
AlertifyProAlertifyPro
FeaturesNotifications
Notifications

Get the alert. On the channel. With the right payload.

Notification worker pulls from a Redis incident queue and fans out concurrently. Every credential is encrypted at rest with AES-256-GCM.

Book a demo See pricing
9
Native channels
AES-256-GCM
Credential encryption
Per-channel
Templated payloads
HMAC-signed
Webhook integrity

Email

Rich HTML threaded by incident — every refire stays in the same thread so inbox triage is incident-by-incident, not event-by-event.

  • Threaded delivery — one thread per incident
  • Rich HTML with embedded timeline preview
  • Plain-text fallback for terminal mail clients
  • Per-org sender domain SPF/DKIM aligned
  • Per-org SMTP sender identity (white-label email)Roadmap

Slack

Interactive message buttons for acknowledge, escalate and resolve — without context-switching out of Slack.

  • Interactive ack / escalate / resolve buttons
  • Per-channel routing rules (e.g. critical → #pager-fire)
  • Threaded replies for incident updates
  • Slash command for status-of-service lookups
  • Token rotation supported without redeploying

Microsoft Teams & Discord

Native channel formatting on both — adaptive cards on Teams, rich embeds on Discord, with the same payload contract.

  • Microsoft Teams — adaptive cards with action buttons
  • Discord — rich embeds with severity-coloured side bar
  • Per-channel routing identical to Slack
  • Bot-token or webhook-URL connection modes

PagerDuty & Opsgenie

Native integrations for teams already on a dedicated paging tool — open, ack and resolve incidents bi-directionally.

  • PagerDuty Events API v2 — open / acknowledge / resolve
  • Opsgenie native deduplication keys
  • Per-service routing-key override
  • Bi-directional close — resolving in PagerDuty closes the incident here

SMS

Twilio-backed SMS for the cases where push notifications aren't enough.

  • Per-incident SMS to responder phone numbers
  • SMS reply-to-ack supported (when carrier permits)
  • Per-responder opt-out preference
  • Voice call escalation via TwilioRoadmap

Generic webhooks

HMAC-SHA256 signed, retried with exponential backoff, every delivery attempt captured in the inspector.

  • HMAC-SHA256 signature on every request
  • Configurable retry policy with exponential backoff
  • Per-webhook delivery inspector with full request/response capture
  • Replay-attack protection via timestamp tolerance
  • Per-webhook custom headers
http
POST /hooks/alertify HTTP/1.1
Host: hooks.acme.io
Content-Type: application/json
X-AlertifyPro-Signature: sha256=a3f1...
X-AlertifyPro-Timestamp: 1750497600

{
  "incident_id": "inc_01H...",
  "severity": "critical",
  "service": "checkout-api",
  "state": "open"
}

Templated payloads

Subject and body templates per channel, with conditional logic — so PagerDuty gets terse, email gets the full story.

  • Subject + body templates per channel
  • Mustache-style variable interpolation
  • Conditional sections by severity, channel and service tag
  • Live preview against a real recent incident
  • Per-org default template overrides

Failed-delivery viewer

When a third-party rejects a notification, you see exactly what — request, response, retry count, next attempt.

  • Per-channel failure dashboard
  • Full request and response body for forensic debugging
  • Retry-now button with the same payload
  • Failure rate graphs per channel

Mobile push (iOS + Android)

FCM + APNs with interactive ack/snooze/escalate actions, gated to Pro+ plans.

  • iOS via APNs with interactive notification actions
  • Android via FCM with high-priority delivery
  • Quiet-hours and per-severity routing per device
  • Multi-device — alerts ring every registered device until ack
  • Critical alert override on iOS for Pro+ plans
Notifications vs the market

How we stack up on notifications

Only rows relevant to this capability. See the full comparison →

FeatureAlertifyProDatadogUptimeRobotPingdom
9 native channels (email, Slack, Teams, Discord, PagerDuty, Opsgenie, SMS, webhook, push)
HMAC-signed webhooks
Templated payloads per channel
Failed-delivery inspector
Mobile push (iOS / Android)
Voice call escalationRoadmap

Frequently asked

Continue exploring

Incident Response

On-call schedules, multi-period rotations, escalation, runbooks and postmortems linked to every incident.

Read more

Integrations

Nine integration types with encrypted credentials, HMAC-signed webhooks, delivery inspection and per-integration health.

Read more

Mobile app

Flutter app focused on the on-call alert-response loop — push, ack, snooze, escalate. Not a dashboard port.

Read more

Ready to see notifications on your stack?

Spin up your first monitor in under a minute. Free forever for the first 5 services.

Book a demo See pricing