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

# Rent compute

> Live availability by GPU model, whole nodes, assigned on the spot.

Renting is self-service. Your console shows **live availability by GPU model**
from **your provider's own capacity pool** — their machines, never a shared
marketplace, and never another provider's hardware.

## How renting works

<CardGroup cols={2}>
  <Card title="What you see" icon="list">
    Nodes available, GPUs per node, and total GPUs — counting only machines
    **online right now**.
  </Card>

  <Card title="What you get" icon="server">
    **Whole nodes** — full servers, typically 8 GPUs each. 1–8 nodes per
    request. MIG slices are on the roadmap.
  </Card>
</CardGroup>

Press **Rent** and the machines are assigned to your tenant on the spot.

## What happens next

* Each machine appears in your console **immediately**.
* Telemetry starts **from the moment of assignment** — utilization, VRAM,
  thermals, power, and faults at 15-second resolution.
* **Partial fulfillment is reported honestly**: you see exactly how many nodes
  were assigned and any shortfall — never a silent gap.
* You verify what you got: models, VRAM, MIG mode, and interconnect topology are
  all inspectable per node.

<Note>
  **Verify before you pay for it.** The console shows each GPU's UUID, model,
  VRAM, and MIG mode, plus lifetime ECC and Xid fault counters. A MIG slice is
  never presented as a full GPU, and unhealthy silicon shows up in the numbers.
</Note>

## Scaling up, down, or moving off

More capacity is the same loop — check availability, rent.

Done with a machine? **Release** it from your console. It leaves your fleet
immediately and returns to your provider's pool, where only their customers can
rent it.

Your historical telemetry **stays yours** — history is never rewritten.

## Data residency

Residency follows your provider's deployment. On sovereign deployments, your
telemetry and logs live in their dedicated cloud account and region — never a
shared control plane. See [Data residency](/platform/data-residency).

## When to go through your provider

Your provider contact is still the path for anything the pool does not answer:

* GPU models not showing in availability
* Reserved or committed terms
* MIG slices
* Site or region constraints

They can also assign machines to your tenant directly — those appear in your
console the same way.

## Coming next

The sidebar previews what is rolling out, each as a visible **SOON** item:

| Feature       | What it will do                                              |
| ------------- | ------------------------------------------------------------ |
| **Instances** | Launch on-demand, reserved, and capacity blocks as workloads |
| **Notebooks** | JupyterLab on your rented GPUs                               |
| **Inference** | An OpenAI-compatible API on managed model endpoints          |
| **Billing**   | Invoices, usage detail, and payment methods                  |