Skip to content
  • VM Provisioning
  • Server Operations

Decommission that leaves nothing behind

Cancelled services keep consuming capacity and appearing in monitoring, because decommission is a checklist that is rarely finished.

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

    Confirm the asset has no dependent services

  2. 2

    Take the final retained copy

  3. 3

    Collect owner sign-off

  4. 4

    Release the resource and update inventory, monitoring and billing

What the run verifies

Capacity actually returned, retention copy recorded, and no orphaned records in any system.

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 Server Operations

Server Operations

Run recurring server and facility tasks the same way every time, with a record of each run.

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.