> For the complete documentation index, see [llms.txt](https://docs.cloud.olakrutrim.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloud.olakrutrim.com/basics/core-infrastructure/compute/billing-for-compute.md).

# Billing for Compute

Krutrim Cloud offers transparent and usage-based pricing for all compute services, including **VMs, AI Pods, and GPU Baremetals**. This guide will help you understand how billing is calculated and what to expect on your invoices when using our compute infrastructure.

***

### Billing Overview

Compute resources are billed **based on actual usage**, with rates displayed on an **hourly basis**. However, Krutrim applies **fine-grained metering**, ensuring you're only charged for what you use, in **15-minute billing intervals**.

{% hint style="warning" %}
You are only billed while your resources are in an **active** state (running or initialising). Stopped or terminated resources do not incur compute charges, although associated storage or IPs may continue to incur costs.
{% endhint %}

***

### Metering and Billing Logic

Even though prices are shown as per-hour rates, the actual metering happens in **15-minute increments**. The minimum billable unit is 15 minutes.

#### Example Billing Scenarios:

| Usage Duration    | Billed Duration      |
| ----------------- | -------------------- |
| 1 hour 40 minutes | 1 hour 45 minutes    |
| 2 hours 5 minutes | 2 hours 15 minutes   |
| 35 minutes        | 45 minutes           |
| 14 minutes        | 15 minutes (minimum) |

This granularity ensures that you are billed fairly and precisely, with charges rounded **up** to the nearest 15-minute mark.

{% hint style="info" %}
Taking the first case as an example, if a user uses an **A100-80GB-NVLINK-1x**, which is priced at **₹189/hour**, and the user runs the VM for **1 hour 40 minutes**, the billed duration will be **1 hour 45 minutes**. Hence, the final bill will be **189 + 189 × (45/60) = ₹330.75**.
{% endhint %}

***

### Billing by Compute Type

#### Virtual Machines (VMs)

Please refer to our [Pricing page.](broken://pages/VJjxSml8oHCwP7uqIXxi)

***

#### GPU Baremetals

GPU Baremetal servers provide exclusive access to full GPUs for high-performance workloads. These are **custom-configured deployments** and require you to **contact our sales team** for pricing and provisioning.

To request GPU Baremetal pricing, please reach out to our Sales team at **<sales@olakrutrim.com>**

***

### Billing

Our Billing cycle happens every **15 minutes**, but you will be charged for the duration during which you used the pod during those 15 minutes.

**Example**:\
Let’s say you started a pod at 10:00 and you terminated the pod at 10:10.\
➡️ You will only be charged for **10 minutes**.

### Other Considerations

* **Attached Storage**: Any block storage volumes attached to compute instances will be billed separately based on the size and duration of attachment.
* **Elastic IPs**: IPs assigned to stopped or unattached VMs may incur additional costs.
* **Snapshots and Backups**: Charged independently based on size and retention period.
* **Overage or Quota Breach**: Exceeding free-tier or reserved quota (if applicable) will automatically incur standard pricing.

***

### Where to View Usage

You can track your ongoing usage and estimated billing:

* In the **Billing Dashboard** on the Krutrim Console
* Via **API** or SDK for programmatic access to usage summaries
* Through **alerts and usage reports**, which can be configured by account or project


---

# 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:

```
GET https://docs.cloud.olakrutrim.com/basics/core-infrastructure/compute/billing-for-compute.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.