VM Provisioning
Provisioning goes wrong in the gaps — a missing tag, the wrong template, a quota nobody checked, a machine that never got monitored. StackHeal turns a provisioning request into a defined sequence with the checks built in, so every build comes out the same shape.
Provisioning request
Requested specification
Checks before build
Benefits
Templates, naming, tagging, networking and monitoring enrolment are part of the workflow rather than something an engineer remembers to do.
Quota, tenant entitlements, placement rules and approval thresholds are validated up front, so failures surface as a clear answer instead of a half-built VM.
A request for Proxmox, vSphere or a public cloud follows the same intake, approval and verification steps, with platform specifics handled in the workflow.
Resize, re-tag, snapshot, suspend and decommission are workflows too, with the same approvals and the same record of what happened.
How it works
The same five stages run whether the request arrived from a ticket, a form or an API call.
A request arrives from your service desk, a self-service form or the StackHeal API, and is normalised into a specification: size, image, network, location, owner, tags.
The specification is tested against your rules — who may request what, in which environment, up to which size, with which images.
Capacity, quota, address availability and placement constraints are confirmed against the target platform before any build begins.
The workflow builds the machine through your platform's own API, applies the template, configures networking and storage, and registers it in inventory.
Reachability, agent enrolment, monitoring coverage and backup registration are all confirmed. A build that fails verification is reported, not silently handed over.
Example workflows
Each of these replaces a checklist that someone was previously following by hand.
Trigger: Approved order or ticket requesting a new instance
Trigger: Request for accelerated compute capacity
Trigger: Scheduled rebuild of a staging environment
Trigger: Cancellation or an end-of-life date being reached
About these examples
Compatibility
Systems connect through maintained connectors or through their own APIs and webhooks. Check the directory for each system's current status.
Controls
Provisioning spends money and creates attack surface. Both deserve a gate.
Bind request types to requesters, tenants, environments and size ceilings. Requests outside the rules are refused with a reason.
Require a named approver above a size, cost or environment boundary you set.
Only approved images and templates are selectable, so builds cannot drift onto unmaintained base images.
Retries resume rather than duplicate, so a failed step does not leave two machines behind.
StackHeal products share one workflow engine, one action catalogue and one run history.
Coordinate backup jobs, monitor outcomes, and simplify recovery procedures.
Learn moreRun recurring server and facility tasks the same way every time, with a record of each run.
Learn moreConnect systems and automate repetitive operational processes.
Learn moreThe questions we are asked most often in evaluation calls.
Something not covered here? Ask our team.
We will scope a proof of concept around one or two of the request types your team handles most often, and show you what the run history looks like.