StackStorm alternatives and similar tools
Based on the "Cloud Orchestration" category.
Alternatively, view StackStorm alternatives based on common mentions on social networks and blogs.
9.8 9.7 StackStorm VS etcdDistributed reliable key-value store for the most critical data of a distributed system
9.6 10.0 StackStorm VS consulConsul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.
9.2 9.9 L2 StackStorm VS SaltSoftware to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:
8.7 9.9 StackStorm VS NomadNomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. Nomad is easy to operate and scale and has native Consul and Vault integrations.
7.4 9.8 StackStorm VS RundeckEnable Self-Service Operations: Give specific users access to your existing tools, services, and scripts
6.4 9.3 L4 StackStorm VS BOSHCloud Foundry BOSH is an open source tool chain for release engineering, deployment and lifecycle management of large scale distributed services.
6.0 9.9 StackStorm VS JujuUniversal Operator Lifecycle Manager (OLM) for Kubernetes operators, and operators for traditional Linux and Windows apps, with declarative integration between operators for automated microservice integration.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of StackStorm or a related project?
StackStorm is a platform for integration and automation across services and tools, taking actions in response to events. Learn more at www.stackstorm.com.
- Install Get yourself a clean 64-bit Linux box that fits the system requirements. Run the installer script:
curl -sSL https://stackstorm.com/packages/install.sh | bash -s -- --user=st2admin [email protected]
- Read the docs: https://docs.stackstorm.com/index.html
- Questions? Check out forum.stackstorm.com
- Or join our Slack community
StackStorm is a platform for integration and automation across services and tools. It 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.
StackStorm helps automate common operational patterns. Some examples are:
- Facilitated Troubleshooting - triggering on system failures captured by Nagios, Sensu, New Relic and other monitoring, running a series of diagnostic checks on physical nodes, OpenStack or Amazon instances, and application components, and posting results to a shared communication context, like Slack or JIRA.
- Automated remediation - identifying and verifying hardware failure on OpenStack compute node, properly evacuating instances and emailing VM about potential downtime, but if anything goes wrong - freezing the workflow and calling PagerDuty to wake up a human.
- Continuous deployment - build and test with Jenkins, provision a new AWS cluster, turn on some traffic with the load balancer, and roll-forth or roll-back based on NewRelic app performance data.
StackStorm helps you compose these and other operational patterns as rules and workflows or actions; and these rules and workflows - the content within the StackStorm platform - are stored as code which means they support the same approach to collaboration that you use today for code development and can be shared with the broader open source community via StackStorm Exchange.
Who is using StackStorm?
How it works
StackStorm plugs into the environment via an extensible set of adapters: sensors and actions.
Sensors are Python plugins for inbound integration that watch for events from external systems and fire a StackStorm trigger when an event happens.
Triggers are StackStorm representations of external events. There are generic triggers (e.g., timers, webhooks) and integration triggers (e.g., Sensu alert, JIRA issue updated). A new trigger type can be defined by writing a sensor plugin.
Actions are StackStorm outbound integrations. There are generic actions (SSH, HTTP request), integrations (OpenStack, Docker, Puppet), or custom actions. Actions are either Python plugins, or any scripts, consumed into StackStorm by adding a few lines of metadata. Actions can be invoked directly by user via CLI, API, or the web UI, or used and called as part of automations - rules and workflows.
Rules map triggers to actions (or to workflows), applying matching criterias and map trigger payload data to action inputs.
Workflows stitch actions together into "uber-actions", defining the order, transition conditions, and passing context data from one action to the next. Most automations are multi-step (eg: more than one action). Workflows, just like "atomic" actions, are available in the action library, and can be invoked manually or triggered by rules.
Packs are the units of content deployment. They simplify the management and sharing of StackStorm pluggable content by grouping integrations (triggers and actions) and automations (rules and workflows). A growing number of packs is available on the StackStorm Exchange. Users can create their own packs, share them on GitHub, or submit them to the StackStorm Exchange organization.
Audit trail is the historical list of action executions, manual or automated, and is recorded and stored with full details of triggering context and execution results. It is also captured in audit logs for integrating with external logging and analytical tools: LogStash, Splunk, statsd, or syslog.
StackStorm is a service with modular architecture. It is comprised of loosely coupled microservice components that communicate over a message bus, and scales horizontally to deliver automation at scale. StackStorm has a full REST API, CLI client, and web UI for admins and users to operate it locally or remotely, as well as Python client bindings for developer convenience.
StackStorm is an established project and remains actively developed by a broad community.
Additional documentation, including installation procedures, action/rule/workflow authoring, and how to setup and use triggers/sensors can be found at https://docs.stackstorm.com.
Hacking / Contributing
To set up a development environment and run StackStorm from sources, follow these instructions.
For information on how to contribute, our style guide, coding conventions and more, please visit the Development section in our documentation.
If you believe you found a security issue or a vulnerability, please send a description of it to our private mailing list at info [at] stackstorm [dot] com.
Once you've submitted an issue, you should receive an acknowledgment from one our of team members in 48 hours or less. If further action is necessary, you may receive additional follow-up emails.
For more information, please refer to https://docs.stackstorm.com/latest/security.html
Copyright, License, and Contributor Agreement
Copyright 2020 The StackStorm Authors. Copyright 2019 Extreme Networks, Inc. Copyright 2014-2018 StackStorm, Inc.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this work except in compliance with the License. You may obtain a copy of the License in the [LICENSE](LICENSE) file, or at:
By contributing you agree that these contributions are your own (or approved by your employer) and you grant a full, complete, irrevocable copyright license to all users and developers of the project, present and future, pursuant to the license of the project.
*Note that all licence references and agreements mentioned in the StackStorm README section above are relevant to that project's source code only.