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

# Capacity advisor for GPU availability in Nebius AI Cloud

export const RolePrerequisite = ({role, defaultGroup}) => {
  return <>
      Make sure that you are in a <a href="/iam/authorization/groups/index">group</a> that has at least the <code>{role}</code> role within your tenant
      {defaultGroup ? <>; for example, the default <code>{defaultGroup}</code> group</> : ""}.
      You can check this in the <a href="https://console.nebius.com/iam">Administration → IAM</a> section of the web console.
    </>;
};

Nebius AI Cloud's *capacity advisor* provides insights into GPU capacity availability for launching virtual machines (VMs) with specific hardware presets. It helps you understand where you can launch VMs based on your [quotas](/compute/resources/quotas-limits) and the current physical capacity in Nebius AI Cloud [regions](/overview/regions).

## Scope

The capacity advisor provides data for the following virtual machines with GPUs:

* **By service**:

  * VMs that you create directly in Compute
  * [Managed Soperator](/slurm-soperator) nodes
  * [Managed Kubernetes®](/kubernetes) nodes
  * VMs launched by [Serverless AI](/serverless) for running jobs and endpoints

* **By type**:

  * [Regular VMs](./manage)
  * [Preemptible VMs](./preemptible)
  * [VMs with reservations](./reservations)
  * [Containers over VMs](./containers)

Data about computing resource availability of [standalone applications](/applications/types) and VMs without GPUs isn't provided.

<Warning>
  Data provided by the capacity advisor is accurate as of a specific timestamp included in the data and doesn't guarantee availability of GPU resources at creation time.
</Warning>

## Prerequisites

<Tabs>
  <Tab title="Web console">
    <RolePrerequisite role="viewer" defaultGroup="viewers" />
  </Tab>

  <Tab title="CLI">
    1. [Install](/cli/install) and [configure](/cli/configure) the Nebius AI Cloud CLI.
    2.     <RolePrerequisite role="viewer" defaultGroup="viewers" />
  </Tab>
</Tabs>

Nebius AI Cloud provider for Terraform doesn't support the capacity advisor.

## How to get data from the capacity advisor

<Tabs>
  <Tab title="Web console">
    In the sidebar, go to <Icon icon="https://mintcdn.com/nebius-ai-cloud/EIxDXldANKp8tKfA/_assets/sidebar/capacity-dashboard.svg?fit=max&auto=format&n=EIxDXldANKp8tKfA&q=85&s=15f7370fbf5b5f722ab8354617924a1d" width="16" height="16" data-path="_assets/sidebar/capacity-dashboard.svg" /> **Capacity dashboard** under **Manage**.

    For each VM platform, preset, region, InfiniBand™ fabric and VM type (regular, preemptible or with reservations), the capacity advisor shows:

    * How many VMs you can launch, based on your quotas and the current physical capacity (for regular and [preemptible](/compute/virtual-machines/preemptible) VMs) or on your active [capacity reservations](/compute/virtual-machines/reservations) (for VMs with reservations).
    * How likely you are to be able to launch the displayed number of regular or preemptible VMs.

      > For example, if your quota for a certain kind of VMs is 10 VMs, you have a high chance of launching them all when the overall capacity is in the hundreds, but a low chance when the capacity is less than 10 VMs.

      As reservations guarantee you a certain number of GPUs that aren't subject to quotas, the chance of launch isn't displayed for VMs with reservations.
  </Tab>

  <Tab title="CLI">
    1. Get the tenant ID.

       To get the tenant ID, go to the [web console](https://console.nebius.com) and expand the top-left list of tenants. Next to the tenant’s name, click <Icon icon="https://mintcdn.com/nebius-ai-cloud/1Ha0sWR6e1mnIaHS/_assets/button-vellipsis.svg?fit=max&auto=format&n=1Ha0sWR6e1mnIaHS&q=85&s=e80b8e57c43bfd117679262e6a1334ad" width="12" height="24" data-path="_assets/button-vellipsis.svg" /> → **Copy tenant ID**.

    2. Run `nebius capacity resource-advice list` to get the capacity advisor data:

       ```bash theme={null}
       nebius capacity resource-advice list --parent-id <tenant_ID>
       ```

    In the output, each list item contains data for a single combination of VM platform, preset, region, InfiniBand fabric and VM type:

    ```yaml highlight={3-8,15-16,19-22,25-28} theme={null}
    items:
      - spec:
          region: eu-north1
          fabric: fabric-2
          compute_instance:
            platform: gpu-h100-sxm
            preset:
              name: 1gpu-16vcpu-200gb
              resources:
                vcpu_count: 16
                memory_gibibytes: 200
                gpu_count: 1
            gpu_memory_gigabytes: 80
        status:
          reserved:
            availability_level: AVAILABILITY_LEVEL_LIMIT_REACHED
            data_state: DATA_STATE_FRESH
            effective_at: "2026-03-27T11:25:55.695087Z"
          on_demand:
            available: 24
            limit: 32
            availability_level: AVAILABILITY_LEVEL_HIGH
            data_state: DATA_STATE_FRESH
            effective_at: "2026-03-27T11:08:07.360Z"
          preemptible:
            available: 22
            limit: 128
            availability_level: AVAILABILITY_LEVEL_MEDIUM
            data_state: DATA_STATE_FRESH
            effective_at: "2026-03-27T11:08:07.360Z"
      ...
    ```

    In the `.items[*].status` fields, `on_demand`, `preemptible` and `reserved` contain data about regular VMs, preemptible VMs and VMs with reservations, respectively. Each of these fields contains the following data:

    * `available`: Maximum number of VMs that you can launch, based on your quotas and the current physical capacity.

    * `limit`: Your current quota.

    * `availability_level`: Level of resource availability. Possible values:

      * `AVAILABILITY_LEVEL_LOW`: **Low chance of launch** — Available capacity is significantly lower than your quota. Creating resources might not be possible.
      * `AVAILABILITY_LEVEL_MEDIUM`: **Medium chance of launch** — Available capacity is lower than your quota. Creating resources is possible, but may fail.
      * `AVAILABILITY_LEVEL_HIGH`: **High chance of launch** — Available capacity is enough to fully satisfy your quota.
      * `AVAILABILITY_LEVEL_LIMIT_REACHED`: **Launch impossible** — No available capacity.

    * `data_state`: State of the data. Possible values:

      * `DATA_STATE_FRESH`: Data is up to date (fetched recently).
      * `DATA_STATE_STALE`: Data is stale (fetched a long time ago).
      * `DATA_STATE_UNKNOWN`: Capacity advisor failed to fetch data.

    * `effective_at`: Timestamp of the last update.
  </Tab>
</Tabs>