Block Storage
NVMe SSD block storage volumes that attach to any cloud compute instance. Pay-as-you-go, hourly billing.
Block Storage (NVMe Volumes)
High-performance NVMe SSD block storage volumes that attach to any cloud compute instance. Scale from 10 GB to 10 TB per volume — billed by the hour with a monthly cap.
Pricing
| Item | Rate |
|---|---|
| Storage | $0.087/GB/month (~₹8/GB/month) — billed hourly |
| Minimum size | 10 GB |
| Maximum size | 10 TB (10,240 GB) per volume |
| Setup fee | Free |
Cost Examples
| Volume Size | Per Hour | Max / Month |
|---|---|---|
| 10 GB | ~$0.0012 | $0.87 |
| 50 GB | ~$0.006 | $4.35 |
| 100 GB | ~$0.012 | $8.70 |
| 500 GB | ~$0.060 | $43.50 |
| 1 TB | ~$0.121 | $87.00 |
| 10 TB | ~$1.208 | $870.00 |
Hourly billing means you only pay for the hours a volume exists. Delete a volume and billing stops immediately. The monthly cap ensures you never pay more than the monthly rate.
Features
- NVMe SSD backed — Enterprise-grade NVMe drives for low-latency, high-IOPS workloads
- Attach / detach — Move volumes between cloud compute instances in the same region
- Expand without downtime — Resize volumes on the fly without rebooting your instance
- Automatic replication — Data is replicated across multiple drives for durability
- Snapshot support — Create point-in-time snapshots for backup or cloning
- Bangalore DC — Volumes are provisioned in our Bangalore datacenter
How It Works
1. Create a Volume
From the cloud dashboard or via API, create a new block storage volume by specifying the size (10 GB – 10 TB).
2. Attach to an Instance
Attach the volume to any running cloud compute instance in the same region. The volume appears as a block device (e.g., /dev/sdb).
3. Format & Mount
# Format the volume (first time only)
sudo mkfs.ext4 /dev/sdb
# Create a mount point
sudo mkdir -p /mnt/data
# Mount the volume
sudo mount /dev/sdb /mnt/data4. Add to fstab (Persistent Mount)
# Get the UUID
sudo blkid /dev/sdb
# Add to /etc/fstab
echo "UUID=<your-uuid> /mnt/data ext4 defaults,nofail 0 2" | sudo tee -a /etc/fstabAlways use nofail in fstab entries for block storage volumes. Without it, your instance may fail to boot if the volume is detached.
Resizing a Volume
- Unmount the volume from your instance
- Resize the volume in the dashboard or via API
- Re-attach and re-mount
- Extend the filesystem:
sudo resize2fs /dev/sdbVolumes can only be expanded, not shrunk. Plan your initial size accordingly, but start small — you can always grow later.
Snapshots
Create point-in-time snapshots of any volume for backup or cloning purposes.
- Creating a snapshot does not require downtime
- Restoring creates a new volume from the snapshot
- Snapshot storage is billed at the same rate as block storage
Use Cases
| Use Case | Why Block Storage |
|---|---|
| Database storage | Low-latency NVMe for MySQL, PostgreSQL, MongoDB |
| Application data | Persistent storage that survives instance rebuilds |
| Media processing | High-throughput for video transcoding, image processing |
| CI/CD artifacts | Fast build artifact storage for Jenkins, GitLab CI |
| Logs & analytics | Expandable storage for Elasticsearch, ClickHouse |
Limits
| Limit | Value |
|---|---|
| Volumes per account | 50 |
| Max size per volume | 10 TB |
| Min size per volume | 10 GB |
| Volumes per instance | 10 |
| Snapshots per volume | 25 |
Next Steps
- Deploy a Cloud Compute instance to attach volumes to
- Review Network & Connectivity for private networking between instances
- Learn about Object Storage for S3-compatible unstructured data storage