The one distinction that matters
A module is an outcome you own. A workflow is a sequence of steps inside it. A module contains workflows.
So “Incident management & troubleshooting” is not a workflow, and “Production Alert Investigation” is not a module. The module
is the domain; the workflow is the automation. When you open a module you see its workflows; when
you open a workflow you see its steps.
What a workflow is made of
A workflow is an ordered set of steps, and each step delivers a task to one or more agents. A step names the work; the agents bound to it do the work. Because binding is explicit, you can see exactly which agent handles which stage — and a step with nothing bound still carries its task, it just has no agent to execute it. That structure is what lets a module coordinate specialists: one step correlates the incoming signal, the next fans out to domain investigators, the next proposes a remediation and asks a human to approve it.The three families
Every module belongs to one family, which tells you the kind of outcome it owns.AI SRE
Keep production healthy — incident response, alert intelligence, and proactive reliability.
Cost Optimization
Spend less across Kubernetes, cloud infrastructure, and observability.
AI Software Operations
Control change risk, production readiness, and CI/CD health.
Enabling a module
Modules are enabled per workspace. Modules → Overview lists the modules configured for yours, across the three families above. Each entry shows its family, what it owns, and how many workflows it contains.1
Open Modules → Overview
Find the module under Configured.
2
Open the module
Configured modules appear in your sidebar with their workflows ready to operate.
3
Connect what it needs
A module reads and writes through integrations. Its page lists what to connect before its
workflows can do useful work.
Disabling a configured module moves it to Available and removes it from the sidebar. Enable it
again from the catalog when you want to operate its workflows.
What a module produces
An enabled module gives you a place to work: a list of the records it has produced — incidents, findings, drifts, verdicts — each carrying the evidence behind it, the runs that generated it, and any decision it needs from a human. That record list is the module’s home in the sidebar.Next steps
Orchestration
How steps, agent binding, and orchestrators work under the hood.
Concepts & glossary
The full vocabulary, in one place.
Incident management & troubleshooting
The module most teams start with.
Approvals
How a workflow asks a human before it acts.