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

# Reservations

> Reserve exclusive, topology-aware bare-metal GPU capacity for a project, then launch workloads onto it with placements.

A reservation ring-fences one or more contiguous **NVLink domains** of bare-metal GPU capacity for a single project in a region. The capacity is exclusively yours for the life of the reservation, with no noisy neighbors and no rescheduling. It is the foundation you build [placements](https://docs.nscale.com/docs/compute/placements.md) on top of to launch servers.

> [!NOTE]
>
> **Reservations work for GB300 NVL72 and B200.** Reserved capacity is not available through the standard [instance creation](https://docs.nscale.com/docs/compute/create-new-instances.md) flow. To run on it, you reserve capacity first, then create a [placement](https://docs.nscale.com/docs/compute/placements.md) inside the reservation.

## Summary

This page walks you through working with **reservations** in the Nscale Console, the capacity model for bare-metal GPU regions. You'll learn how reservations are structured, how to reserve contiguous capacity, how to read a reservation's capacity, and how to delete one.

Use this guide if you:

* Need **guaranteed, exclusive GPU capacity** for a project rather than best-effort placement
* Are preparing to run **tightly coupled training or large-scale inference** on reserved GPU capacity
* Want a repeatable, UI-driven process for reserving and managing bare-metal GPU capacity

## How reservations fit together

Reservations sit at the top of a four-level hierarchy. Each level builds on the one above it:

| Concept | What it is |
| - | - |
| **Reservation unit** | The capacity shape you reserve. One unit is **one NVLink domain**. Hosts per unit depend on the flavour: a GB300 NVL72 unit is a rack of 18 hosts; a B200 unit is a single host. |
| **Reservation** | One or more contiguous units, ring-fenced for a project in a region. Exclusive, and fixed in size after creation. |
| **Placement** | A scheduled block of hosts carved out of a reservation, governed by a Pack or Spread policy. See [Placements](https://docs.nscale.com/docs/compute/placements.md). |
| **Server** | An individual bare-metal host launched by a placement. |

A single reservation can host **multiple placements**, for example a production training cluster and a smaller development cluster on the same reserved capacity. The total number of servers across all placements can never exceed the reservation's capacity.

> [!NOTE]
>
> **Capacity is shown in the console.** Each reservation unit reports its per-unit totals (hosts, GPUs, CPUs, and memory) in the creation wizard and via the [reservation-units API](https://docs.nscale.com/api-reference/reservation-units/list-reservation-units.md). Per-unit totals vary by flavour.

## Availability

Reservations are the capacity model for **bare-metal GPU regions**, currently GB300 NVL72 and B200. Capacity is contracted and region-specific, so a reservation can only be created in a region that has enough **contiguous** capacity to satisfy the full request.

## Key properties

Reservations behave differently from on-demand instances. Three properties matter most:

* **Exclusive.** Reserved capacity belongs to your project alone for the life of the reservation.
* **Contiguous and atomic.** A reservation is all-or-nothing. Either the exact contiguous capacity is delivered, or the request fails cleanly—fragmented capacity is never silently combined.
* **Fixed size.** A reservation can't be grown after creation. You can add or remove placements, release unused units through the API, or delete the reservation entirely.

> [!NOTE]
>
> **Naming rules:** Reservation names are **3–50 characters** of **lowercase letters, digits, and dashes**.

## Reservation lifecycle

A reservation moves through the following provisioning states:

| State | Description |
| - | - |
| **Pending** | The reservation has been accepted and is waiting for provisioning to start |
| **Provisioning** | Capacity is being claimed and the NVLink domains are being ring-fenced |
| **Provisioned** | The reservation is ready and you can create placements |
| **Error** | Provisioning failed, or a provisioned reservation's capacity became invalid. For example, the requested contiguous capacity could not be claimed |
| **Deprovisioning** | The reservation is being torn down following a delete |
| **Unknown** | The reservation's state can't be determined right now |

**Actions you can take:**

* **Create a placement** to start launching servers from the reservation
* **Delete a reservation** to release its capacity (this also deletes every placement in it)

## Reserve capacity

Reserving capacity is a three-step wizard. You can't proceed to the next step until the current one is valid.

**1. Open the create flow**

In the Console, open your project, then go to **Compute → Reservations** and click **Reserve Capacity**.

You can also start from **Reservations** in the organization sidebar, which lists reservations across every project in the organization. There, **Reserve Capacity** first asks you to choose the project to reserve in. See [Reserve capacity from the organization page](https://docs.nscale.com/docs/compute/topology-view.md#reserve-capacity-from-the-organization-page).

![Reservations list view](https://mintcdn.com/nscale/nIcjBCbNvFHc262C/images/reservations/reservations-list.png?fit=max\&auto=format\&n=nIcjBCbNvFHc262C\&q=85\&s=85c6ab96cbad26c0e7516246232090c7)

**2. Set up your reservation**

Give the reservation a name under **Reservation Name**. Names are 3–50 characters of lowercase letters, digits, and dashes.

Click **Configuration** to continue.

**3. Configure your reservation**

Choose how much capacity to reserve and where:

* **Flavour** selects the reserved capacity type. The per-unit breakdown updates with your choice.
* **Number of units** sets how many NVLink domains to reserve. The wizard shows the per-unit breakdown (hosts, GPUs, and CPUs) as you adjust the count.
* **Select available region** lists only the regions with enough **contiguous** capacity for your request, with the **Max contiguous** units available in each.

> [!WARNING]
>
> **Domains must be contiguous.** If no single region can satisfy the full request from contiguous capacity, the wizard shows *"Insufficient contiguous capacity"*. Fragmented capacity across a region can't be combined—reduce the unit count or choose another region.

Click **Review your reservation** to continue.

![Configure your reservation](https://mintcdn.com/nscale/nIcjBCbNvFHc262C/images/reservations/create-reservation-step-2-configure.png?fit=max\&auto=format\&n=nIcjBCbNvFHc262C\&q=85\&s=0a760e82192df3abc6c33633b7a7f99d)

**4. Review and reserve**

Review the summary: name, unit count, GPU and CPU totals, and region. Reserved capacity is exclusive to your project and **can't be grown after creation**.

Click **Reserve Capacity** to submit. The reservation begins provisioning and appears in your reservations list.

> [!TIP]
>
> Capacity is claimed asynchronously. A reservation starts in **Pending**, moves to **Provisioning** while capacity is claimed, and reaches **Provisioned** once all its NVLink domains are ring-fenced. That typically takes around a minute. You can create placements as soon as it is provisioned.

## View a reservation

Open a reservation from the list to see its detail view. The **Overview** tab brings together everything about the reservation:

* **Placements** — the placements running in this reservation, with a shortcut to create a new one.
* **Capacity** — how many of the reservation's hosts are allocated to placements versus free, alongside units reserved, total placements, and per-host CPU and GPU counts. Click **See topology** to jump to the **Topology View** tab.
* **Configuration** — the region, creation date, flavour, who created it, and the reservation ID.

Switch to the **Placements** tab for the full list of placements in the reservation, with their host count, policy, network, status, and region.

The **Topology View** tab shows where the reservation's hosts sit across pods and NVLink domains, colored by placement. See [Topology View](https://docs.nscale.com/docs/compute/topology-view.md).

![Reservation detail overview](https://mintcdn.com/nscale/nIcjBCbNvFHc262C/images/reservations/reservation-detail-overview.png?fit=max\&auto=format\&n=nIcjBCbNvFHc262C\&q=85\&s=454b24b72c843c25643275b0254ffa9d)

> [!NOTE]
>
> **See all your reserved capacity on one map.** The **Reservations** pages for the organization and for each project also have a **Topology View** tab, which shows every reservation's hosts in one grid. It needs organization-level topology access. See [Topology View](https://docs.nscale.com/docs/compute/topology-view.md).

## Delete a reservation

Deleting a reservation releases its capacity back to the region so it can be reserved again.

> [!WARNING]
>
> **Deleting a reservation cascades.** It deletes every [placement](https://docs.nscale.com/docs/compute/placements.md) in the reservation, and each placement deletes all of its servers. This is permanent and can't be undone—any data on those servers is lost.

**1. Open the reservation**

Go to the reservation's detail view and review its placements—deleting the reservation will remove all of them.

**2. Delete the reservation**

Open the actions menu and choose **Delete Reservation**, then confirm. The reservation, its placements, and their servers are deleted, and the reserved capacity is released.

## Next steps

* [Create a placement](https://docs.nscale.com/docs/compute/placements.md) to launch servers from your reservation.
* See where your reserved hosts sit in the [Topology View](https://docs.nscale.com/docs/compute/topology-view.md).
* Manage reservations from the command line with the [CLI](https://docs.nscale.com/docs/cli/overview.md).
* Explore the full [Reservation API reference](https://docs.nscale.com/api-reference/reservations/list-reservations.md).
