Submit a tool
Directory / automation

StackStorm

automationdevops

Event-driven automation platform for IT operations. Connects monitoring alerts, webhooks, and sensor data to runbook workflows that auto-remediate issues, trigger deployments, and execute security responses without human intervention

#automation#event-driven#ops#remediation#chatops#self-hosted
Alternative to PagerDuty runbooksmanual incident runbookscustom webhook-to-script glue codeRundeck (for event-driven use cases)
Visit Website Source Code

Quick Start

docker run -d --name stackstorm -p 443:443 stackstorm/stackstorm:latest

Overview

StackStorm is an event-driven automation platform built for IT operations teams. Where scheduled automation tools run jobs on a timer, StackStorm responds to events: a monitoring alert fires, a webhook arrives from a deployment pipeline, a sensor detects a threshold breach. The platform connects those events to runbook workflows that execute automatically, whether that means restarting a service, opening a ticket, triggering a deployment, or notifying a channel.

The core model is trigger-rule-action. Triggers are events from sensors and webhooks. Rules define which triggers should activate which actions, with filtering conditions so the same alert type can route to different workflows based on metadata. Actions are the operations that execute: an API call, a shell command, an Ansible playbook run, a message to Slack. Workflows chain multiple actions together with branching logic, parallel execution, and error handling.

Integration packs are the practical foundation. StackStorm ships with over 160 packs covering the infrastructure and monitoring tools most ops teams already run: AWS, Azure, Kubernetes, Ansible, PagerDuty, Jira, Slack, Datadog, Nagios, and more. Each pack includes pre-built actions and sensors for that platform. Rather than writing glue code to connect your monitoring system to your automation scripts, you configure rules that wire existing packs together.

ChatOps is a first-class capability. Engineers can trigger workflows, check execution status, and receive results directly in a Slack or Teams channel, which keeps automation visible and accessible without a separate dashboard.

StackStorm is not a lightweight tool. The full stack involves multiple services, a message bus, and a workflow engine that requires meaningful infrastructure to run reliably in production. For teams that need serious event-driven automation at scale, this investment is justified. For simpler automation needs, the operational overhead outweighs the benefit.

Use Cases

Specific ways to use StackStorm for your workflow.

01
Auto-remediate infrastructure alerts by triggering a runbook workflow the moment a monitoring system detects a problem
02
Execute deployment workflows in response to CI/CD events without polling or manual trigger steps
03
Run security response playbooks automatically when a threat detection system fires an alert
04
Give ops teams a ChatOps interface where they trigger and monitor automation workflows directly from Slack or Teams

Deployment Strategy

Recommended ways to host StackStorm in your own environment.

docker
self-hosted