Pricing plan for Incident management
Overview
Potential Pricing plan for the Incident Management category.
References
- Core is for a single developer, with the purchasing decision led by that same person
- Starter is for single team usage, with the purchasing decision led by a team manager
- Premium is for multiple team usage, with the purchasing decision led by one or more Directors
- Ultimate is for strategic organizational usage, with the purchasing decision led by one or more Exec
Proposed Pricing Plan
| Functionality | Core | Starter | Premium | Ultimate |
|---|---|---|---|---|
| ALERT INTEGRATIONS | ||||
| Generic REST | ||||
| Out of the box external Prometheus | ||||
| Multiple generic + email endpoints | ||||
| Create custom integrations - GUI based | ||||
| Special bi-directional out of the box integrations with popular monitoring tools | ||||
| INCIDENTS | ||||
| Manual Incident Creation | ||||
| Incident creation based on limited criteria (e.g. integration or severity) | ||||
| Incident creation based on extensive criteria | ||||
| Incident payload transformations | ||||
| On-call schedule management | ||||
| Create multiple schedules | ||||
| Escalation policies |
|
|
||
| Routing rules for alerts | ||||
| Runbooks | ||||
| Link runbooks to alerts via simple URL input - link appears in alert | ||||
| Automatically render linked runbooks in alerts/incidents | ||||
| Create new runbook when creating alert |