Ignitify.dev
VMs
CLI reference

VMs

See the VMs that run your tasks, and delete them.

vm:list

List your live VMs with their state, age and idle time.

  • needs API key
  • --json: full
synopsis
$ ignitify vm:list [--pinned] [--deployment-id D] [--task-name N] [--preset P] [--older-than 24h] [--limit N] [--after <booted_at> --after-vm-id <vm-id>]
terminal
$ ignitify vm:listvm_id          vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83deployment_id  019f3c33-6e18-7a24-9c0b-3d7f5a82e1b4task_slug      workerpreset         std.microresidency      autostate          idleguest          {"runtime":null,"seen_at":1791969123900,"capabilities":["cancel-…age            5.2midle           45s
More examples (1)
A pinned VM idle for a long time
$ ignitify vm:list --pinnedvm_id                                    deployment_id                         task_slug  preset     residency  state           age   idle───────────────────────────────────────  ────────────────────────────────────  ─────────  ─────────  ─────────  ──────────────  ────  ──────vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83  019f3c33-6e18-7a24-9c0b-3d7f5a82e1b4  worker     std.micro  pinned     pinned-standby  1.1d  1.0d ⚠
FlagValueDefaultDescription
--deployment-idD—Only VMs of this deployment.
--task-nameN—Only VMs of this task.
--presetP—Only VMs of this instance class.
--older-than24h—Only VMs older than this age, for example 24h.
--limitN—Rows on the page. The server sets the default and the largest value.
--after<booted_at>—Boot time of the last row of the page before (ISO 8601). Use with --after-vm-id.
--after-vm-id<vm-id>—VM id of the last row of the page before. Use with --after.
--pinned——Only pinned VMs, the ones that stay up until you delete them.

vm:get

Show one VM: residency, state, age and its task nature.

  • needs API key
  • --json: full
synopsis
$ ignitify vm:get <vm-id>
terminal
$ ignitify vm:get vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83VM Detailsvm_id                   vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83tenant_id               019f2b10-3c55-7a01-b2e4-9d0c61f7a8b3deployment_id           019f3c33-6e18-7a24-9c0b-3d7f5a82e1b4task_slug               workerpreset                  std.microresidency               autostate                   idlebooted_at               2026-10-14T09:12:03.540Zboot_fingerprint        3f9c1a2be7d41056guest                   {"runtime":null,"seen_at":1791969123900,"capabilities":["cancel-ack","reattach"],"rootfs_build":null,"worker_version":"2026.09.26.2","announced_pubkey":true}age                     5.2midle                    45snature.state            independentnature.network          nonenature.duration         shortnature.residency        autonature.cardinality      manynature.interaction      boundary-onlynature.egress_tls_only  false
FlagValueDefaultDescription
<vm-id>required——The VM id, from vm:list.

vm:delete

Tear down a VM by hand.

  • needs API key
  • asks to confirm
  • deletes data
  • --json: full
synopsis
$ ignitify vm:delete <vm-id> [--yes] [--force]
terminal
$ ignitify vm:delete vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83Will tear down VM vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83.Proceed? [y/N] yVM deleted: vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83
More examples (1)
A pinned VM with --force
$ ignitify vm:delete vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83 --forceWill tear down VM vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83 (PINNED — --force given).Proceed? [y/N] yVM deleted: vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83
terminal
$ ignitify vm:delete vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83 --yes --json
--json
{
  "deleted": {
    "vm_id": "vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83",
    "residency": "auto",
    "failed_runs": 0
  }
}
A pinned VM without --force
$ ignitify vm:delete vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83Error: Refusing to delete vm_019f3c35-2c90-7d16-8b47-0e5a1d9f6c83: this VM is PINNED (permanent standby, alive 26.0h).Deleting it is exactly what "permanent" protects against — re-run with --force if you mean it.
FlagValueDefaultDescription
<vm-id>required——The VM id.
--yes, -y——Skip the question.
--force——Allow the delete of a pinned VM. It does not skip the question.

What happens

  1. Reads the VM, and refuses a pinned VM unless you pass --force.
  2. Prints what it will tear down.
  3. Asks you to confirm, unless you pass --yes.
  4. Deletes the VM, which fails a run that is busy on it.