Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rafftechnologies.com/llms.txt

Use this file to discover all available pages before exploring further.

Updated May 8, 2026 Every VM has a status field that reflects where it is in its lifecycle. Most actions you take in the dashboard or via the API are state transitions.

​
State diagram

Creation: initiating → provisioning → booting → active
Stop:     active     → finalizing   → passive
Start:    passive    → booting      → active
Reboot:   active     → booting      → active
Delete:   any        → terminated
Failure:  any        → failure      (non-billable)

​
State reference

StatusDescriptionBillable
initiatingQueued, initial setup before provisioningYes
provisioningVM being created in the hypervisorYes
bootingStarting upYes
activeRunning and accessibleYes
passiveStopped, resources reservedYes
finalizingShutting downYes
failureCreation or operation failedNo
unknownUnhandled stateNo

​
Why passive is billable

A stopped VM still holds CPU, RAM, disk, and IP allocations on the hypervisor. Those reservations are billed at the same per-hour plan rate even when the OS isn’t running. To stop billing, delete the VM (and its volumes, snapshots, and backups, if no longer needed). See Billing model for how subscription credits work when you delete mid-term.

​
provisioning during snapshots and backups

While a snapshot or scheduled/instant backup is running on a VM, the dashboard temporarily shows the VM in provisioning state — even though the VM was already up and serving traffic. This is normal and not a problem:
  • The VM continues running. Network traffic, SSH/RDP sessions, and applications keep working.
  • The state flips back to active automatically when the capture completes — snapshots are typically 1–2 minutes, backups around 3 minutes on average; both scale with the size of the disk being captured.
  • It’s the same provisioning label used during creation; the dashboard reuses the state because the hypervisor is doing capture work in the background.
If you see provisioning and you didn’t trigger anything, check the Snapshots or Backups tab on the VM detail page — there’s almost certainly a scheduled job running. No action needed; just wait for it to finish.
What you seeWhat it actually means
provisioning right after CreateReal provisioning — VM being built
provisioning on an existing VMSnapshot or backup in progress; VM is still serving
provisioning stuck for 10+ minutesPossible issue — see Troubleshooting

Manage power

Trigger state transitions.

Pricing

What each state costs.
Last modified on May 8, 2026