StackStorm
Runbook automation software
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if StackStorm and its alternatives fit your requirements.
Free Trial unavailable
Free version
Small
Medium
Large
-
What is StackStorm
StackStorm is an event-driven automation platform used to create and run operational runbooks and workflows across infrastructure and applications. It targets DevOps and SRE teams that need to automate incident response, routine operations, and integrations with monitoring, chat, and IT systems. The product combines sensors (event ingestion), rules (event-to-action mapping), actions, and workflows, with extensibility through integrations (“packs”) and APIs/CLI.
Event-driven automation model
StackStorm natively supports sensors and rules that trigger actions and workflows based on events from external systems. This fits incident response and operational automation where actions should run automatically when monitoring or ticketing events occur. The rule engine and workflow layer help standardize runbooks beyond ad-hoc scripts.
Extensible integrations via packs
StackStorm uses “packs” to package integrations, actions, sensors, and rules for third-party tools and internal systems. This structure supports reuse and versioning of automation content across teams and environments. It also enables organizations to build custom packs when a needed integration is not available.
Automation-as-code with APIs
StackStorm provides a CLI and REST API to manage actions, rules, and workflows as code. This supports CI/CD-style promotion of automation content and peer review through source control. It also enables integration with existing developer tooling and internal portals.
Operational overhead to run
StackStorm is typically self-hosted and requires operating multiple components (e.g., message bus, database, authentication, and workers) depending on deployment. Teams must plan for upgrades, backups, scaling, and high availability. This can be heavier than managed runbook services for organizations without platform engineering capacity.
Learning curve for model
Users must learn StackStorm concepts such as sensors, rules, actions, and workflow definitions, which can be unfamiliar compared with simpler script-based runbooks. Building reliable automations often requires understanding event payloads, error handling, and idempotency. Adoption can be slower for teams that primarily use point-and-click runbook tools.
Ecosystem maturity varies
The breadth and maintenance level of community packs can vary by integration and may require internal ownership for critical systems. Some enterprise features (e.g., governance, RBAC depth, audit/reporting expectations) may require additional configuration or complementary tooling. Organizations should validate required integrations and compliance needs early.
Plan & Pricing
| Plan | Price | Key features & notes |
|---|---|---|
| Community (Open Source) | Free | Apache 2.0 licensed; self-hosted Community Edition; documentation and community support via Slack, forums, and GitHub. |
| Enterprise / Commercial Support | Not listed on official site (contact partners) | Official site lists partners and contact channels for commercial support and services; no public subscription tiers, pricing, or trial details currently published. |
Seller details
StackStorm (open-source project; originally created by StackStorm, Inc., later acquired by Brocade Communications Systems, then Broadcom Inc.)
Open Source
https://stackstorm.com/
https://x.com/StackStorm
https://www.linkedin.com/company/stackstorm/
