Alerts in. Plain English out.
Named parsers for Datadog, Grafana, Prometheus, Sentry and CloudWatch turn a raw payload into a page that says what broke and how badly. Everything else comes in over a webhook. Every integration is included, because you pay per service, never per alert source.
Trigger an alert
Five named parsers pull out the fields that actually matter — what broke, how badly, and the link back to the source — so the page reads like a sentence. Anything else POSTs JSON to the generic webhook.
Datadog
Monitor alerts arrive with title, severity and tags mapped onto the page.
Grafana
Grafana alerting webhooks, with rule name and evaluation state carried through.
Prometheus
Alertmanager labels and annotations survive the trip onto the page.
Sentry
Issue alerts route with project, level and culprit intact.
CloudWatch
Amazon CloudWatch alarms, delivered over SNS.
Generic webhook
Anything that can POST JSON. If it can hit a webhook, it can page through gravityloop.
Choose a destination
Six channels, all in the base plan. The distinction that matters is whether a channel is meant to wake someone — acknowledge from whichever reaches you first and the rest stand down.
SMS
Delivered end-to-end in under 5 seconds at p95. Reply to acknowledge.
Voice
A phone call with IVR acknowledgment, for when a text won't wake someone up.
Push
Critical alerts ring through a silenced phone, and acknowledge in one tap.
Slack
Ack, escalate or resolve from the message without leaving the channel.
The full alert payload and timeline, for the people who want the detail.
Webhook
Fire the incident at your own systems — status pages, bots, whatever you run.
The waking channels are the ones a service's cover window governs: on business-hours cover they hold until the window opens, while Slack, email and webhooks still land immediately. Of those, only SMS and voice are metered — a carrier bills us for every text and every call, whereas push never touches one, so it stays unlimited.
What you bring with you
Your schedules, your policies and your people come across as they are. The importers are open-source, so the code that reads your API token is code you can read first.
PagerDuty importer
Reads schedules, escalation policies, users, and integrations. Open-source — read it before you hand over a token.
Opsgenie importer
The same one-command path off Opsgenie, built for teams moving ahead of its end-of-life.
SSO & SCIM
Your directory is an integration too — SCIM keeps the user list current, so someone who leaves stops being paged. Both in the base plan.
Don't see your stack? The generic webhook covers anything that can POST JSON, and the migration CLI is open on GitHub. Tell us what you're running at hello@gravityloop.io.