> For the complete documentation index, see [llms.txt](https://docs.yottalabs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yottalabs.ai/products/serverless/pricing-and-billing.md).

# Pricing & Billing

Serverless charges are calculated **hourly**, based on the actual compute and storage resources consumed.

$$
Total\ Cost= \sum(GPU\_{rate} \times GPU\_{count} + Storage\_{rate}\times Storage\_{size})
$$

#### Billing Formula

Each hour’s cost includes:

* GPU usage cost
* Storage cost

Note: We don't have extra charge for network bandwidth

#### Example

If a user deploys the following resources:

* **2 Workers**, each configured with:
  * GPU: H100 × 2
  * Disk: 100 GB × 2
* H100 GPU unit price: **$1.85 / GPU / hour**
* Disk unit price: **$0.001 / GB / hour**

**Total hourly cost = (2 × 2 × $1.85) + (200 × $0.001 + 200 × $0.001) = $7.4 + $0.4= $7.8 / hour**

#### Billing Characteristics

* **Pay-as-you-go:** Billing stops immediately once resources are released.
* **Unified multi-region billing:** The system aggregates resource usage across all regions.
* **Transparent reporting:** Detailed per-worker billing breakdowns are available in the **Details** page of each **Serverless**.

#### Deductions and Balance Policy

* Charges are deducted as soon as an Serverless starts running.
* When your **account balance approaches $0**, all running Serverlesss will be automatically terminated.

#### Viewing Billing Details

* Navigate to **Billing** from the left menu.
* The Billing page displays all Serverless usage and cost details, including per-worker hourly charges and historical summaries.

<figure><img src="/files/WHJOwOUcvAdiUE8Dlljc" alt=""><figcaption></figcaption></figure>


---

# 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://docs.yottalabs.ai/products/serverless/pricing-and-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.