Volumes
High-performance NVMe block storage that attaches to VMs and containers.
Pricing
Plans price by the gigabyte provisioned. Choose a tier based on your database size, log retention requirements, and expected growth rate.
Loading SKUs...
Block storage that
moves with your workloads.
Databases, queues, search indexes, and file-heavy apps all need durable disks that survive software deploys and restarts. Ephemeral instance storage is the wrong place for that state.
Tower Volumes are network-attached block disks you bind to Virtual Machines and Container Instances through the same billing and API model as the rest of the platform—no manual SAN tickets.
The trade-off is classic block economics: you pay for capacity you provision, whether every gigabyte is full or not, and each volume is intended for a single writer at a time—exactly what relational engines expect.
Replicated block service,
predictable performance.
Data is striped across a distributed storage plane with automatic healing—designed so a single drive or node loss does not take your database with it.
Latency and throughput scale with the size you purchase, keeping headroom proportional as tables and media libraries grow.
Capacity can grow online where your workload supports it, so midnight resize windows become the exception instead of the rule.
What you get on Day One
Attach durable disks to VMs and containers, grow them when needed, and manage everything from the Tower APIs.
Built for databases
Low-latency replicated block storage suited to MySQL, PostgreSQL, MongoDB, WordPress, and other write-heavy services—not toy file shares.
Grow in place
Increase provisioned size through Tower when your dataset outgrows the original disk—without standing up a parallel volume migration project.
API-first attach
Attach and detach disks to supported workloads from the portal or API so automation and humans stay in sync.
Single-writer semantics
Each volume attaches to one instance at a time—matching how relational databases and many stateful services expect storage to behave.
Configuration & Platform Details
A concise reference for architecture reviews, security questionnaires, and capacity planning.
Platform specifications
Values reflect the Volumes product line; exact limits may vary by region and account tier.
- Durability model
- Replicated block storage with automatic healing across the regional storage plane—not a single attached USB disk.
- Access pattern
- Single-writer volumes suited to relational databases and other services that expect exclusive access to a disk.
- Performance
- IOPS and throughput scale with provisioned capacity; pick a size that leaves headroom for growth bursts and maintenance tasks.
- Attachment
- Supported attach targets include Tower Virtual Machines and Container Instances. Mount orchestration is handled by Tower—no direct hypervisor access required.
- Resize
- Online capacity growth where the guest OS and filesystem support extending a live volume.
- Pricing
- Per GB provisioned. Routine attach and detach operations are part of normal use, not a surprise per-call fee.