Skip to main content
This feature is in public preview.
An instance SKU (stock keeping unit) is a unique combination of node properties such as accelerator_type and interconnect_type. Two nodes with the same SKU are interchangeable, so the market treats them as one pool for pricing and allocation. Each SKU has a stable id (isku_...) and a human-readable name set by the operator who registered it. Orders, procurements, and pool transfers are pinned to a single SKU id. Pass it with --instance-sku <id> or omit the flag to pick from a list. 
sf orders create --side buy --pool dev --nodes 1 --start now --duration 1h \
  --max-rate 20.00 \
  --instance-sku isku_4UpxzQw7A8N

​
List instance SKUs

sf instance-skus list

NAME         ACCELERATOR               MEMORY     STORAGE  VCPUS  ID
sea-3-h100   8 x NVIDIA H100 (80GB)    2,016 GiB  1.5 TiB  56     isku_cxcwpDW93MaaBelmnLaez
iad-12-h200  8 x NVIDIA H200 (141GB)   2,016 GiB  1.5 TiB  56     isku_NWhD6SrbjcXstGRvgl0eC
Add --verbose to see every property column (interconnect type, zone, etc.).

​
Get details for one SKU

sf instance-skus get isku_cxcwpDW93MaaBelmnLaez

​
Interactive picker

Run any command that accepts --instance-sku (e.g. sf orders create, sf procurements create) without the flag to pick a SKU from a list of registered SKUs and their properties.

​
Deprecated and deleted values

Values move through stable, then deprecated, then deleted. Deprecated values stay usable for a grace period and include a migration message. After deletion, new SKUs cannot be registered with that value. SKUs already pinned by existing orders keep matching as long as they’re alive, but the SKU pool drains as inventory turns over. Move workloads to a replacement value before the registry entry is removed.