finds.dev← search

// the find

StackStorm/st2

★ 6,494 · Python · Apache-2.0 · updated Feb 2026

StackStorm (aka "IFTTT for Ops") is event-driven automation for auto-remediation, incident responses, troubleshooting, deployments, and more for DevOps and SREs. Includes rules engine, workflow, 160 integration packs with 6000+ actions (see https://exchange.stackstorm.org) and ChatOps. Installer at https://docs.stackstorm.com/install/index.html

StackStorm is an event-driven automation platform for ops and SRE teams — think infrastructure IFTTT where sensors watch external systems, rules match triggers to actions, and Orquesta workflows chain those actions into multi-step remediations. It's aimed at teams managing complex heterogeneous environments who want to codify runbooks rather than run them manually. The 160+ integration packs covering AWS, Kubernetes, PagerDuty, Slack, and more are the main draw.

The pack ecosystem is genuinely useful — 6000+ pre-built actions mean you're probably not writing SSH wrappers yourself. Orquesta (the YAML-based workflow engine) handles branching, parallel execution, retries, and pause/resume for human-in-the-loop steps, which is more than most homegrown runbook solutions get right. Everything is stored as code (rules, workflows, actions), so it fits naturally into a GitOps workflow and can be code-reviewed like any other change. The audit trail with full execution context is good for post-incident analysis.

The install story is a curl-pipe-to-bash onto a dedicated Linux box — this is a system-level service with MongoDB, RabbitMQ, and PostgreSQL as hard dependencies, so it's a real operational commitment before you automate a single thing. The README still badges Python 3.6/3.8 support in 2026, which is a red flag about how actively the core is being modernized. The microservice architecture (separate processes for the API, sensor container, action runner, scheduler, timer) means local development is genuinely painful and production debugging requires correlating logs across multiple services. ChatOps integration depends on external bots (Errbot, Hubot) that are themselves largely unmaintained projects.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →