StackStorm ties together your existing infrastructure and application environment so you can more easily automate that environment — with a particular focus on taking actions in response to events.
With StackStorm you define, and share – as code – your operational patterns from events and triggers through to actions taken in response.
Whether it is wiring together your continuous integration (CI) and continuous deployment (CD) environments in a transparent way, or automating your troubleshooting and even remediation (including responses to security events, or any of the other common patterns you perform each day manually or with the help of siloed automation), StackStorm helps.
How StackStorm Works
The StackStorm platform works with two main classes of content: integrations (both inbound and outbound) and automations (decisions you want made and workflows). The platform executes and manages that content, enabling you to tie events whether generated by people or systems to actions, which again can be responses from a system or a person.
StackStorm is easy to extend to work with just about anything. While our roots are in OpenStack (a great home for much of our workflow code, for example), StackStorm absorbs events and takes actions on almost everything that makes up today’s operational environments such as AWS, OpenStack, Docker, Jenkins, Bamboo, PagerDuty, HipChat or Slack, your ELK stack, your monitoring pipeline, your security event manager, and more.