RunbookAI
5.2#18 in runbook automation softwareLinux
Visit
| Fact | RunbookAI | StackStorm |
|---|---|---|
| Audit trail | RunbookAI logs investigation hypotheses, evidence, proposed actions, approval decisions and execution results locally. | Action executions are recorded with triggering context and results, and audit logs can integrate with Logstash, Splunk, statsd and syslog. |
| Deployment | RunbookAI offers CLI mode and a self-hosted shared knowledge server, with no hosted service or control plane. | StackStorm is distributed as Linux RPMs and Debs and as Docker images; its documentation also describes Vagrant/OVA, Ansible, Puppet and Kubernetes deployment options. |
| Integrations | Documented integrations include AWS, Kubernetes, PagerDuty, OpsGenie, Slack and Claude Code. | Sensors and actions connect external systems; examples listed include webhooks, SSH, REST calls, OpenStack, Docker, Puppet, Sensu and JIRA. |
| Purpose | RunbookAI investigates production incidents by forming hypotheses, gathering evidence and recommending fixes. | StackStorm is a platform for integration and automation across services and tools, with a focus on taking actions in response to events. |
No prices published.
RunbookAI is aimed at SRE teams investigating production workloads, particularly teams running AWS and Kubernetes. It suits teams prepared to self-host and meet its runtime and API-key requirements.
StackStorm suits teams automating event-driven responses across connected services and tools. Listed uses include automated remediation, continuous deployment, ChatOps, and automated security response.