---
title: "Vector Database billing"
description: "Vector Database is billed for compute, disk above 30 GB per node, and snapshots. See what each charge covers and what stops it."
content_type: "concept"
product: "vector-database"
platform: "TIR"
url: "/tir/vector-database/concepts/vector-database-billing/"
---

# Vector Database billing

A Vector Database is billed in three parts: compute, disk and snapshots. For the rates, see
[E2E's pricing page](https://www.e2enetworks.com/pricing), and to estimate a total, use the
[E2E cost calculator](https://calculator.e2enetworks.com). Charges are added to your account
automatically, and **Account Usage** under **Billing & Usage** shows them as **VectorDB Usage**, **VectorDB Disk
Usage** and **VectorDB Snapshot Usage**; see [Analyse usage](/tir/tir-billing/how-to/analyse-usage/).

## Compute

On **E2E Cluster**, compute is billed per node, per hour, at the plan's hourly price. It starts when you create the
database and stops when you [stop](/tir/vector-database/how-to/stop-or-start-a-vector-database/) or
[delete](/tir/vector-database/how-to/delete-a-vector-database/) it. Nodes you add by
[scaling up](/tir/vector-database/how-to/scale-up-a-vector-database/) are charged from the moment you
add them.

On a private cluster you pay for the cluster's nodes, and that covers the database's compute.

## Disk

Every node starts with a 30 GB disk that is part of the node's price. You pay for the disk above 30 GB,
per GB per month, for each node, worked out by the hour. At 30 GB per node, the disk is covered by the node's price. When you
[resize the disk](/tir/vector-database/how-to/resize-the-disk/), the charge follows the new size on
every node. Disk charges continue while the database is stopped.

## Snapshots

A snapshot is charged by its size, for as long as it exists. Delete the snapshots you are done with to stop their charge; see
[how to delete one](/tir/vector-database/how-to/delete-a-snapshot/).

## What stops the charges

| Action              | Compute   | Disk above 30 GB | Snapshots                 |
| ------------------- | --------- | ---------------- | ------------------------- |
| Stop the database   | Stops     | Continues        | Continue                  |
| Delete a snapshot   | Unchanged | Unchanged        | That snapshot stops       |
| Delete the database | Stops     | Stops            | Deleted with the database |

To stop every charge, delete the database. API calls and data transfer within the same region are
included in these charges.

## Keeping the bill small

- Stop a database while it is idle.
- Start with the disk you need, because a disk only grows.
- Delete the snapshots you have finished with.
- Add nodes only when you need them, because the node count only goes up.