Lifecycle states
Out-of-capacity (UNAVAILABLE)
When the cloud provider has no capacity for a VM’s size (mostly GPU sizes), the create or resume lands in UNAVAILABLE. machine0 get explains what happened, and recovery is automatic:
- A resume that failed returns to
SUSPENDED within about ten minutes. Your data is safe in the suspend snapshot the whole time.
- A brand-new VM that never started is removed automatically about 30 minutes after the failure.
machine0 start <name> retries right away in either case — it fails fast with a clear error if the size is still out of stock.
Stopped VMs bill at full rate because cloud resources stay reserved. Suspend or destroy to stop machine billing.
Suspend vs stop vs destroy
Stop keeps the cloud instance alive. Resources stay reserved, billing continues, IP is retained. Use when you need the VM back quickly with the same IP.
Suspend snapshots the VM, deletes the cloud instance, and stops machine billing. You pay only image storage (~$1.95/mo for a 25 GB boot disk). Disks attached to the VM keep billing while it is suspended and are re-attached on resume. Resume later with machine0 start — the VM gets a new IP. The snapshot (named suspended-<machine>-<date>-<time>) is the suspended VM’s only copy of its disk: deleting it with machine0 images rm also destroys the suspended machine.
Destroy deletes everything permanently.
HTTPS proxy
Every VM gets authenticated HTTPS at https://<name>.mac0.io, proxying to port 80. No DNS or TLS setup needed. Renaming a VM updates the endpoint.
In-browser terminal
VMs created with a managed key get a one-click in-browser shell from the web
dashboard. See SSH → In-browser terminal.
Commands
See CLI reference and MCP reference.