Getting started
Core concepts
Assets, tenants, environments, actions, workflows, runs and policies — the vocabulary used throughout the product.
StackHeal models infrastructure directly rather than through generic records. Seven concepts cover most of the platform.
Asset
A thing a workflow can act on: a virtual machine, a physical host, a storage target, a service, a device. Assets carry attributes — class, location, owner, tags — that policy and targeting are expressed against.
Tenant
A customer or business unit scope. Credentials, policy, maintenance windows and run history belong to a tenant. A run is bound to exactly one tenant scope, resolved before any step executes.
Environment
A risk classification attached to assets — typically production, staging and development. Policy commonly differs by environment, and approvals are frequently required only in production.
Action
A single registered operation with a typed input schema: restart a service, create a VM, trigger a backup job, run a named playbook, call an HTTP endpoint. Actions live in the action catalogue and are the only operations a workflow may perform.
Workflow
A versioned definition composed of triggers, conditions, actions, approvals and verification assertions. Publishing a workflow creates an immutable version; each run records which version executed.
Run
One execution of one workflow version. A run holds its trigger payload, resolved scope, every step's inputs and outputs, branch decisions, approvals, timings and final verification result.
Policy
Deterministic rules evaluated before and during a run: who may trigger what, on which assets, in which environments, up to what blast radius, requiring whose approval. Policy is code, not model output.
Scope of this documentation