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

# Pricing

> Learn how Hyperbolic bills GPU instances and storage across On-Demand, Reserved, Private Cloud, and Storage Volumes.

## At a glance

|                        | On-Demand                                              | Reserved                                       | Private Cloud             |
| ---------------------- | ------------------------------------------------------ | ---------------------------------------------- | ------------------------- |
| **Billing**            | Hourly, for the life of the instance                   | Paid up-front, in full, at creation            | Negotiated per contract   |
| **Rate**               | On-demand rate, locked at creation                     | Discounted rate for a fixed period             | Custom, per contract      |
| **Terminate anytime?** | Yes                                                    | No — auto-terminated when the reservation ends | Per contract terms        |
| **Balance required**   | Enough to cover 1 hour of runtime across all instances | Full cost of the reservation period            | N/A — billed per contract |

## On-Demand

New instances you create will be billed at on-demand rates by default. You may terminate on-demand instances at any time. On-demand instances are billed continuously for the lifetime of the instance until they are terminated.

You must have a balance high enough to support at least one hour of instance runtime prior to creating a new on-demand instance, across all of your instances, including the new instance you intend to create. There is no minimum charge for on-demand instances - while you are required to be able to cover at least one hour of instance runtime at instance creation you may terminate your instance at any time, including before it becomes ready.

### When billing starts

An instance becomes ready when it is fully provisioned and SSH-accessible. Billing starts the moment an instance becomes ready — you are only charged for time spent in the ready state.

While rare, full or partial provisioning errors may occur. Any instance that fails to become ready within the provisioning timeout period (\~3 hours) is automatically terminated. You are never charged for instances that never enter a ready state.

### Price lock

The cost per hour per GPU displayed during instance creation is locked in for the duration of the instance, with one exception: in rare circumstances, we may reach out about a price increase if you have had on-demand instances running at significantly below-market rates for a long time.

*Instances may be automatically terminated if your account balance is no longer positive. To prevent termination, configure [Auto Top-Up](/docs/general/auto-top-up) to automatically deposit funds when your balance falls below a set amount.*

<Warning>
  Instance termination is permanent. On-machine data cannot be recovered. Data on attached storage volumes is never lost as a result of instance termination — but after your balance reaches zero, you have a 30-day grace period to recover storage volume data before the volumes themselves are automatically terminated.
</Warning>

## Reserved

When creating an instance, you may choose to reserve it for a fixed period of time at a discounted rate.

* Paid up-front. Reserved instances are paid in full at creation. Your balance must cover the entire cost of the reservation period.
* Reservation starts at ready. The reservation duration begins the moment the instance becomes ready. If a reserved instance fails to become ready within the provisioning timeout period, it is automatically terminated and the full amount is immediately credited back to your account. You are never charged for instances that never enter a ready state.
* No early termination. You may not terminate a reserved instance yourself. It is automatically terminated at the end of the reservation period — before the reservation ends, be sure to close out any work and save all data to storage that does not live on the instance.

<Note>
  Coming soon: Reservation Protection. Customers will soon have the option to enable Reservation Protection, which prevents automatic termination at the end of the reservation period. Instead, the instance converts to an on-demand instance and is billed at current on-demand rates until terminated.
</Note>

## Private Cloud

Private Cloud instances live off-platform and are not displayed on your dashboard. They are not self-serve through your dashboard and are only available via custom contract. These instances are custom-built for you directly in one of our data centers.

Access, management, and payment terms are unique to each contract and are negotiated directly with a sales representative and a technical representative. [Contact your sales representative](mailto:sales@hyperbolic.ai) to learn more about accessing and managing your Private Cloud instances.

<Note>
  Coming soon: You will soon be able to view (but not manage) your Private Cloud instances the same way you do for on-demand and reserved instances.
</Note>

## Storage Volumes

Storage volumes are performant, on-prem network storage volumes that live independently from your instances.

* Billed by size. Volumes are always billed at on-demand rates based on the total volume size, regardless of the capacity actually used or the volume of data transferred.
* Terminate anytime. You may terminate storage volumes at any time.

*Storage volumes may be automatically terminated if your account balance reaches zero. To prevent this, configure [Auto Top-Up](/docs/general/auto-top-up) to automatically deposit funds when your balance falls below a set amount.*

<Warning>
  Storage volume termination is permanent. Data cannot be recovered. Data on instances to which a volume is attached is never lost as a result of volume termination. After your account balance reaches zero, you have a 30-day grace period to recover data on storage volumes before they are automatically terminated.
</Warning>
