Skip to content
  • VM Provisioning
  • Workflow Orchestration

Turning an order into a verified running instance

Provisioning involves a dozen steps across several systems, and a missed step produces a machine that is unmonitored, unprotected or untagged.

The workflow

How StackHeal handles it

Each step is a registered action, a condition or an approval. Nothing here is a general-purpose command.

  1. 1

    Normalise the order into a provisioning specification

  2. 2

    Check entitlement, quota and placement policy

  3. 3

    Build from the approved template through the platform API

  4. 4

    Enrol in monitoring and backup, then verify every registration

What the run verifies

A machine that is reachable, monitored, backed up and correctly attributed — verified before hand-off rather than after a complaint.

Where a person stays involved

Any step that changes state can be configured to require an approval, and a run that cannot verify its own outcome escalates rather than closing. The confidence threshold, the blast-radius limit and the approver are all yours to set.

Related products

StackHeal products share one workflow engine, one action catalogue and one run history.

Learn more about VM Provisioning

VM Provisioning

Standardize virtual machine provisioning and infrastructure lifecycle operations.

Learn more
Learn more about Workflow Orchestration

Workflow Orchestration

Connect systems and automate repetitive operational processes.

Learn more

See this workflow built against your systems.

We will walk through the intake, the policy checks, the approval points and the verification step using your own tooling.