Alerting and integrations
This page lists what actually ships today, and names what does not exist yet. A short honest list beats a long vague one.
Alert channels, today
| channel | detail | plan |
|---|---|---|
| Push | native iOS app and Apple Watch, currently in TestFlight | all plans |
| incident open and recovery, to members | all plans | |
| SMS | escalation step, to verified numbers | Sentinel and up |
| Phone call | final escalation step, at most 2 calls per incident | Sentinel and up |
| Signed webhooks | HMAC-signed (X-Datargo-Signature), secret rotation, test fire | all plans |
| Slack | incident open and recovery, via incoming webhook | all plans |
| Status page subscribers | double-opt-in email to your customers, on open and recovery | Sentinel and up |
Escalation walks the ladder until someone acknowledges: push, then SMS, then a phone call, with timings configured per schedule. Phone numbers must be verified by a one-time code before they can ever be paged, and acknowledging takes ownership: every other device quiets down.
Webhook targets fire on incident opened and resolved, carry an HMAC signature in
X-Datargo-Signature so your receiver can verify origin, support secret rotation, and
have a test fire in the product. Webhook destinations are validated against the same
SSRF blocklist the probes use.
Embeds
- Status page on your own domain (CNAME-verified, TLS managed), public or private.
- SLA badge: an SVG badge with copyable Markdown and HTML snippets, served from your status page.
- RSS: every status page carries a feed.
What we do not have yet
We would rather you read this here than discover it after signing up:
- No native Slack or Microsoft Teams app. Slack is reached via an incoming webhook today; an app with interactive actions is not built.
- No PagerDuty or Opsgenie forwarding. Perstat replaces the paging layer rather than feeding it; the Opsgenie comparison is honest about what that swap involves.
- No Zapier.
- No public API with scoped keys yet, which also means no Terraform provider and no monitors-as-code. It is the stated next step; it appears on the changelog when it lands, dated.
If one of these is the thing that decides it for you, tell us: hello@perstat.io reads every message, and the answer you get will be concrete.