> For the complete documentation index, see [llms.txt](https://ai-docs.fptcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-docs.fptcloud.com/account/billing/tutorials/billing-policy/gpu-container-billing.md).

# GPU Container Billing

### Pricing <a href="#gpuvmbillingpolicyv1-pricing" id="gpuvmbillingpolicyv1-pricing"></a>

For the pricing, please visit our portal at [FPT AI Factory](https://ai.fptcloud.com/pricing/gpu-virtual-machine).

Notes:

* Prices include all applicable taxes and surcharges.
* Prices are displayed based on current exchange rates and are subject to daily fluctuations. They may also change due to stock availability, demand, or market conditions.

### Billing logic <a href="#gpuvmbillingpolicyv1-pricing" id="gpuvmbillingpolicyv1-pricing"></a>

| **Billing Logic**                                                                                                                                                                     | **Minimum billable usage** | **Time to charge** |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------- | ------------------ |
| <ul><li><strong>GPU Instance</strong>: Billed per GPU-second (Running status only).</li><li><strong>Persistent Storage</strong>: Billed per GB-second (Running or Stopped).</li></ul> | 1 second                   | Every 15 minutes   |

**Billing Equation:**

* **Usage duration**: In hours (not rounded up)
* **Storage Volume**: In GB
* **GPU Cost**: Usage duration × GPU price per hour
* **Storage Cost**: Usage duration × GB × storage price per hour
* **Total Cost:** **GPU Cost + Storage Cost**

**Example:**

> You use a container for 30 minutes with:
>
> * one H100 GPU (15 CPUs, 250 GB RAM, 1 GPU) priced at $2.31/hour
> * 1000 GB temporary storage priced at $0.00013/GB/hour

* Usage duration: 30 minutes = 0.5 hours
* GPU Cost: `0.5 × $2.31 = $1.16`
* Storage Cost: `1000 × $0.00013 × 0.5 = $0.0015`
* Total: `$1.16 + $0.0015 = $1.1615`

### **Low Balance:**

When your **account balance is lower than the estimated total cost of using the container for 1 hour**, some actions may be limited such as Create Container, Create Storage Volume, Start Container and Restart Container.&#x20;

You will also receive notification from the system to add credits.

### **Negative Balance:**

Whenever your balance reaches zero or below, your container will be stopped automatically but not destroyed immediately. Data on temporary storage will be deleted and cannot be recovered. Since the data on the persistent storage is still available, you are still billed for persistent storage on stopped container.

**If your balance is negative for 7 consecutive days, we will delete the container and all data will be permanently deleted**. Please plan accordingly.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ai-docs.fptcloud.com/account/billing/tutorials/billing-policy/gpu-container-billing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
