Pagerly: Run on-call and incidents inside Slack
Pagerly is an on-call and incident response tool that runs rotations, paging, incidents and status pages inside Slack or Microsoft Teams.
What is Pagerly?
Pagerly keeps on-call work in the chat tool the team already uses. Rotations are built as round-robin or custom schedules, Slack user groups such as @oncall update from the schedule, and overrides, swaps and holiday handling are managed in the same place. Schedules can be imported from Opsgenie and JSM, and paging can reach an engineer by call, SMS and email when a page is not acknowledged. Incident response also runs in the channel: responders acknowledge pages, assign an Incident Commander, and Pagerly creates meeting links, Jira tickets and dashboard links automatically. Alerts can be raised from AWS, Datadog, Sentry and other observability tools, and MTTA and MTTR are tracked per incident. Status pages, uptime monitoring and monitoring of 3,000+ third-party services are included from the Starter plan, and an optional AI SRE agent investigates incidents when mentioned in the channel.
Focus areas: Incident Response.
Who is Pagerly for?
- Engineering teams running an on-call rotation
- SRE and platform teams handling incidents
- Operations teams that coordinate in Slack or Microsoft Teams
How much does Pagerly cost?
Pagerly starts at $4/mo. Always check the vendor’s own pricing page before you buy.
| Plan | Price | What you get |
|---|---|---|
| Basic | $19 per team / month | Round-robin rotations, Slack user group sync, schedule overrides, rotation reminders; paging optional at $4/user/month |
| Starter | $39 per team / month | Everything in Basic plus schedule sync from PagerDuty and Opsgenie, status pages, uptime and vendor monitoring, task management, Jira/PagerDuty/Opsgenie two-way sync; paging optional at $4/user/month |
| Enterprise | Custom | Everything in Starter plus customised Slack workflows, customised incident response and bot, workflows built on request, two-way ticket message and status sync, white-labeled Slack bot |
| Pro | $15 per month | Public status page on your own domain, uptime monitoring, status page aggregator, 3,000+ vendor monitors, outage alerts in Slack, Teams or Discord; paging optional at $4/user/month |
| On-call paging | $4 per responder / month | Optional add-on to Basic or Starter; call, SMS and email escalation, escalation policies, automatic incidents from AWS, Datadog, Sentry and 40+ tools, iOS/Android/macOS apps, MTTA and MTTR tracking |
| AI SRE agent | Custom | Optional add-on, not included in Basic or Starter; priced per team, scoped to chosen on-call teams and integrations |
Is Pagerly worth it?
A practical fit for teams that want rotations, paging and incident response to stay inside Slack or Teams rather than in a separate console
Where Pagerly is strong
- Scheduling, paging and incident response all happen inside Slack or Teams
- Billed per team rather than per seat, with paging charged only for responders in the rota
- Imports existing schedules from Opsgenie, PagerDuty and JSM, ahead of Opsgenie's April 2027 shutdown
Where it falls short
- Paging is not part of the Basic or Starter plan price and costs $4 per responder per month
- The AI SRE agent is not included in Basic or Starter and is quoted case by case
How do you get started with Pagerly?
- 01Add Pagerly to Slack, Teams or Discord, which is free and needs no credit card
- 02Import an existing schedule from Opsgenie, PagerDuty or JSM, or build a round-robin rotation
- 03Add the paging add-on for the responders who should receive calls, SMS and email
Pagerly: frequently asked questions
Does Pagerly replace Opsgenie?
Pagerly covers on-call scheduling, escalation, call, SMS and email paging, incident response and status pages. Existing schedules import from Opsgenie and JSM, and Opsgenie customers can migrate in one click ahead of its April 2027 shutdown.
Do responders have to leave Slack?
No. Acknowledging a page, swapping a shift, opening an incident, updating a status page and assigning an Incident Commander all happen inside Slack or Microsoft Teams.
Is paging included in the plan price?
No. Paging is an optional add-on at $4 per user per month on top of the team price, and it is charged only for people who can be paged. It adds call, SMS and email escalation, escalation policies and alerts from observability tools.
How does paging work if Slack is down?
Paging runs on Pagerly infrastructure rather than Slack, so calls, SMS and email are delivered regardless. Slack itself is one of the 3,000+ services Pagerly monitors.
Pagerly alternatives
The closest tools in our directory, matched on category, focus areas and audience.
| Tool | Best for | Free plan | Starting price | Focus areas |
|---|---|---|---|---|
| Pagerly | Teams that want on-call and incident response inside Slack | Yes | $4/mo | Incident Response |
| Doctor Droid | SRE teams investigating production incidents and root causes | No | $99/mo | Incident Response |
| Calmo | SRE and DevOps teams cutting time to root cause | No | — | Incident Response |
| Alfred AI | Teams needing one correlated view of API health, risk and usage | Yes | $233/mo | — |
| Pulumi | Platform teams automating provisioning, governance and cost checks | Yes | $40/mo | — |
| HeyCloud | DevOps and developer teams working primarily in AWS | Yes | — | — |
| Middleware | Engineering teams monitoring cloud-native apps and infrastructure | Yes | — | — |
| Crusoe | Teams running large-scale AI training and inference on managed GPU cloud | No | — | — |
| Autoheal | Enterprise engineering teams automating delivery work | No | — | — |
| Traversal | Enterprise SRE and platform teams | No | — | — |
| Cloudgeni | Teams bringing cloud resources under code with reviewable fixes | Unknown | — | — |

