# Rootly

Slack-based incident management with on-call paging, status pages and retrospectives.

- Website: https://rootly.com/
- Listing: https://openack.co/p/rootly
- Not evaluated. Listed by OpenACK: its 9 claimed capabilities are OpenACK's reading of the product's public site, not the maker's word, and nobody has checked them yet.

OpenACK's description (not checked):

> Rootly runs incidents from Slack and its web app, with on-call schedules, escalation policies, alert routing, status pages and collaborative retrospectives. New accounts start with a trial of about two weeks.

## Capabilities

- **not evaluated**: Declare an incident from Slack
- **not evaluated**: Send an alert to the service from a webhook or email
- **not evaluated**: Set who gets alerted with an on-call schedule
- **not evaluated**: Escalate an alert if nobody acknowledges it
- **not evaluated**: Acknowledge and resolve an alert
- **not evaluated**: Get an alert by SMS or phone call
- **not evaluated**: Publish a public status page
- **not evaluated**: Schedule a maintenance window
- **not evaluated**: Write a postmortem from an incident timeline

## What the statuses mean

- **confirmed** (ACK): a person from OpenACK signed in with a test account and saw it work.
- **not confirmed** (NAK or ?): it was tried and didn't work, or we couldn't reach or check it. Not proof it's missing, but not verified.
- **not evaluated** (—): nobody has checked it. It's the founder's word only.

Treat only "confirmed" as verified. A result is a record of one evaluation on the date shown, not a guarantee.