> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sfcompute.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SKUs

> Pick the hardware your orders run on

A SKU (stock keeping unit) is a unique combination of [instance](https://docs.sfcompute.com/preview/instances.md) properties such
as `accelerator` and `rdma_type`.

Each SKU has a stable `id` and a human-readable `alias` that SF Compute assigns at registration.
Both the API and the CLI identify a SKU by its `sku_...` id.

A SKU is the boundary of fungibility. Two instances with the same SKU run on the same hardware and
are interchangeable. The market prices and allocates them as one supply, and you cannot pin a
specific machine within a SKU. Hardware differences that matter, such as the accelerator, the remote
direct memory access (RDMA) network, the zone, and the machine shape, place nodes in different SKUs.

Each SKU has its own [orderbook](https://docs.sfcompute.com/preview/orderbook.md) and its own allocation. An
[order](https://docs.sfcompute.com/preview/orders.md) fills only against orders on the same SKU. A [pool](https://docs.sfcompute.com/preview/pools.md) records
its allocation as a node-count schedule per SKU.

A SKU identifies hardware, not how you buy it, so spot and non-spot orders for the same hardware
share one SKU. Some guarantees depend on staying on the same hardware, such as buying more capacity
and keeping your instances running. These hold within one SKU, not across SKUs. An instance pins to
its SKU at create time and never moves to another.

## SKU properties

Every SKU has an `id` and an `alias`. Its other properties, such as `region`, `accelerator`, and
`memory_bytes`, describe the hardware, and the API omits any that are unset. For the full list, read
the [SKU API reference](https://docs.sfcompute.com/api-reference/skus/get-sku.md#response-id).

In the API, each property other than `id` and `alias` is an object with a machine-readable `value`
and a human-readable `display_value`, which the console and `sf` show. For example, a SKU with 2,016
GiB of memory returns:

```json theme={null}
"memory_bytes": { "value": 2164663517184, "display_value": "2,016 GiB" }
```

## List SKUs

List the registered SKUs and their ids.

```bash theme={null}
sf skus list
```

```text theme={null}
  NAME         ACCELERATOR           MEMORY     STORAGE  VCPUS  ID
  sea-3-h100   8 x H100 80GB HBM3    2,016 GiB  1.5 TiB  56     sku_4UpxzQw7A8N
  iad-12-h200  8 x H200 141GB HBM3e  2,016 GiB  1.5 TiB  56     sku_NWhD6SrbjcXstGRvgl0eC
```

Add `--verbose` to include the region, zone, form factor, RDMA type, and public IPv4 columns.

## Get details for one SKU

Get the full property set for a single SKU.

```bash theme={null}
sf skus get sku_4UpxzQw7A8N
```

## Use a SKU

[Orders](https://docs.sfcompute.com/preview/orders.md), [pool transfers](https://docs.sfcompute.com/preview/pools.md), [procurements](https://docs.sfcompute.com/preview/procurements.md),
and [instances](https://docs.sfcompute.com/preview/instances.md) each pin to a single SKU.
Pass its id with `--sku`.

```bash theme={null}
sf orders create --side buy --pool dev --count 1 --start now --duration 1h \
  --max-rate 20.00 \
  --sku sku_4UpxzQw7A8N
```

## Pick a SKU interactively

On commands that pin a SKU (for example, `sf orders create`), omit `--sku`. You then pick
from a list of registered SKUs and their properties.

## API reference

See the [SKUs API](https://docs.sfcompute.com/api-reference/skus/list-skus.md) for programmatic access.
