---
title: Billing
---

# Billing

Private Cluster uses a **fixed-rate billing model** — you are charged per node per hour (or via a committed plan), regardless of how much the GPUs inside the cluster are actually utilized. This provides predictable costs and eliminates per-workload billing.

## 1. Hourly Pricing

Hourly pricing gives you a flexible, pay-as-you-go cluster. You are billed for every node in the cluster for every hour it exists, regardless of whether the GPU is running a workload.

### How Billing Works

| Event | Billing Status |
|-------|----------------|
| Cluster is **created** | Billing starts for all nodes |
| Node is **allocated** to a project | No change in billing |
| Node is **running a workload** | No change in billing |
| Node is **freed** back to the pool | No change in billing |
| Cluster is **deleted** | Billing stops permanently |

> There is no way to pause billing for individual nodes without deleting the cluster. The fixed rate applies to all nodes at all times.

### Example

If the hourly rate is ₹300/hr per node and your cluster has 4 nodes:

```bash
Node Rate  : ₹300/hr per node
Nodes      : 4
Daily Cost : ₹300 × 4 × 24 = ₹28,800/day
```

---

## 2. Committed Billing

Committed billing allows you to reserve your Private Cluster for a fixed duration at a lower per-node rate. The full amount is deducted upfront at the time of cluster creation.

### Available Commitment Periods

Available commitment periods: **30 Days**, **90 Days**, and **365 Days**.

:::info The longer the commitment period, the lower the effective hourly rate per node.
:::

### How Billing Works

| Event | Billing Status |
|-------|----------------|
| Cluster is **created** | Full committed amount deducted upfront |
| Cluster is **running** | No additional compute charges during the period |
| Cluster is **deleted before period ends** | No refund for the remaining period |

:::info Additional nodes added to a committed cluster after creation are billed at **hourly rates**, not at the committed rate.
:::
### Post-Commitment Options

When creating a committed cluster, select what happens when the period ends:

| Option | Behaviour |
|--------|-----------|
| **Auto-Renew** | Automatically renews for the same commitment period |
| **Switch to Hourly Billing** | Cluster transitions to hourly pricing |
| **Auto-Terminate** | Cluster is automatically deleted at period end |

## 3. What is Included

Deploying the following services inside a Private Cluster does **not** incur additional charges:

| Service | Additional Charge |
|---------|-------------------|
| Instances (Nodes) | None |
| Inference Endpoints | None |
| Training Clusters | None |
| Vector Databases | None |

:::info Storage resources (SFS, PFS, Datasets) attached to services inside the cluster are billed independently.
:::

## 4. Storage Billing

Storage resources are billed independently of the cluster and continue to accrue charges even after the cluster is deleted.

| Resource | Billed Independently |
|----------|---------------------|
| Shared File System (SFS) | Yes |
| Parallel File System (PFS) | Yes |
| Datasets | Yes |

:::info Always delete unused storage resources to avoid unexpected charges after cluster deletion.
:::

## 5. What is Not Billed

| Action | Details |
|--------|---------|
| **Allocate / Deallocate Nodes** | Node management within the cluster is free |
| **Security Groups** | Creating and attaching security groups incurs no charge |
| **VPC IP** | Attaching a VPC IP to services in the cluster is free |
| **IAM & RBAC** | Role-based access management has no additional cost |

## Cost Estimation

Use the [E2E Pricing Calculator](https://calculator.e2enetworks.com/) to compare hourly and committed plans, estimate projected costs, and evaluate potential savings based on your cluster size and commitment duration.


---