The right person, woken once, with the whole story.
Schedules people can read at a glance, escalation that doesn’t give up, and an incident view that already knows what changed. Pay for responders, never for the people who just need to watch.
- 0 min Page primary · push
- 5 min Page secondary · push + email
- 15 min Notify #incidents and engineering lead
Rotations you can read at a glance.
Daily, weekly or custom shift lengths with a handoff day and time in the schedule’s own time zone. Limit a layer to business hours, cover a gap with an override, and see the next 30 days of your own shifts in the app.
- Ask a teammate to swap a shift from your phone in two taps; accepting creates the override
- Overrides show dashed on the schedule, so cover is obvious
- Handoffs are time-zone-aware, daylight saving included
Escalation keeps going until someone answers.
Each step pages a schedule’s current on-call, a specific person or a Slack channel after a delay you set. After the last step the policy repeats until someone acknowledges, and acknowledging cancels everything still queued.
- Up to 10 steps, each with its own delay and targets
- Repeat the policy every few minutes, a set number of times
- Each person’s own notification rules: push at once, a call a minute later, a text after three
- Recovery notifications go out automatically when the monitor comes back
- Step 1 Platform primary · push, repeated 0m
- Step 2 Platform secondary · push + email +5m
- Step 3 #incidents in Slack + engineering lead +15m
Every channel, and every page on the record.
Push, email, Slack and webhooks, each retried with backoff until delivered. The delivery log shows who was paged, how, and when they answered.
-
Push
Time-sensitive notifications on iOS and Android with an Acknowledge button right on the alert.
-
Email
Every alert email takes replies: answer
ackorresolveand it happens. Anything else becomes a note. -
Slack
Post to a channel like
Team and up#incidentsas an escalation step, so the team sees what the on-call sees. -
Webhooks
HMAC-signed JSON on triggered, acknowledged, resolved, notes and monitor up/down events.
One incident view, with the likely cause attached.
Alerts with the same dedup key group into the open incident instead of paging again, and failures elsewhere in the same environment within five minutes show up as related alerts. Deploys from the 30 minutes before the trigger are ranked, and the best match is named as the likely cause.
- Triggered, acknowledged, identified, monitoring, resolved: one lifecycle, one timeline
- Owner, responders, notes and the p95 chart around the incident with deploy markers
- “What we know” summaries and postmortem drafts written from the timeline (Starter and up)
- Post to your status page from the incident; subscribers get the update by email
What we know
Drafted by Pulseback · updated 1m agop95 latency on the Public API rose from 120ms to 2.4s at 08:51, confirmed from 3 regions. The api service was deployed 4 minutes earlier; commit a3f9c12 moved session storage to a new Redis cluster.
Timeline
- 08:47 Deploy api@a3f9c12 “Move sessions to Redis cluster” by dana-k
- 08:51 Triggered: p95 above 2s on Public API, confirmed from 3 regions
- 08:51 Paged Priya N. by push
- 08:53 Acknowledged by Priya N. via push
- 08:55 Status page: Investigating, 214 subscribers emailed
- 09:02 Identified: rolling back a3f9c12
Your pager keeps working, even when we don’t.
Alert delivery and escalation run on infrastructure separate from the dashboard. If our app goes down, your 3am page still happens.
- Independent alert path Escalations are scheduled durably and keep firing through a control-plane outage.
- Every channel, with fallback Push, email, Slack and webhooks — retried until delivered, with email as the fallback.
- Exactly-once paging Idempotent processing means one outage is one page, not forty.
- A full audit trail See who was paged, how, and when they answered — for every alert.
Bring the alerts you already have.
Monitors are one source. Your existing alerting, scripts and CI can open, acknowledge and resolve incidents too.
-
Your monitors
Confirmed failures open incidents on their own, and recovery resolves them when every linked monitor is back up.
-
Events API
PagerDuty Events v2–compatible: point existing alerting at
/api/v1/eventswith a Pulseback routing key. Docs -
Email-to-incident
Anything that can send an email can open an incident at its own
@alerts.pulseback.ioaddress. Docs -
Deploys
GitHub or a generic deploy webhook records every release, ready to be named as the likely cause. Docs
Responders
Compare plans- Free
- 1
- Starter
- 2
- Team
- 5
- Business
- 15
- Enterprise
- Custom
Viewers are unlimited on every plan.
Rotations & escalation
Compare plans- Free
- —
- Starter
- —
- Team
- Included
- Business
- Included
- Enterprise
- Included
Multi-step escalation policies, overrides and swaps.
Get paged when Pulseback launches.
Pulseback is almost ready. Join the waitlist and we’ll email you the day it opens, Free plan and all.
Join the waitlist