Skip to main content

Volume Storage Classes

Storage Classes

One class is offered today: gp1, SSD-backed, at 7,000 IOPS per 100 GiB provisioned. It is what a volume gets when you don't name a class, and there is nothing to decide yet.

Volumes attach directly to Compute instances in our open-beta region, and pricing is per provisioned GiB per month. Two further classes are designed and named but not yet offered. Asking for one is refused when you create the volume, rather than quietly giving you something else:

  • General Purpose (gp1): for boot volumes and typical application storage. Offered today.
  • Latency Optimized (io1): for IOPS-intensive, latency-sensitive workloads. Planned.
  • Capacity Optimized (st1): for cost-efficient, infrequently accessed data. Planned.

Rather than taking this page's word for it, the API reports what it will accept: the pvs.storageClasses query returns each offered class and which one is the default. Storage classes in the documentation covers it.

General Purpose (gp1) Open Beta

SSD-backed volume with 7,000 IOPS per 100 GiB provisioned. The volume class Origin Cloud offers today, for boot disks and general application storage.

Features

  • 7K IOPS per 100 GiB
  • Throughput per 100 GiB: 20,6 MB/s
  • Consistent latency for small and medium random I/O

Use Cases

  • Virtual machine boot disks
  • Web servers and app servers
  • Development environments
  • Medium-sized databases (Postgres, MySQL)

Choose If

  • You need an SSD volume for boot disks or general application storage
  • You need consistent IOPS and low latency
  • You want 7K IOPS per 100 GiB at 0,0700 € per GiB/month

Avoid If

  • Your workload requires extremely high IOPS or throughput
  • You run write-heavy databases or real-time analytics at a scale one volume cannot serve

Latency Optimized (io1) Planned

Replicated SSD volume at 14,000 IOPS per 100 GiB - double gp1 - for workloads where latency must hold under sustained load.

Features

  • 14K IOPS per 100 GiB
  • Throughput per 100 GiB: 41,3 MB/s
  • Consistent low-latency access

Use Cases

  • Databases under write-heavy load (Postgres, Cassandra, Elasticsearch)
  • Financial or transactional workloads
  • Real-time analytics
  • Message brokers and event stores

Capacity Optimized (st1) Planned

Archival-optimized volume for cost-effective, infrequent access. Ideal for backups and cold data with low IOPS requirements.

Features

  • Ideal for sequential access patterns

Use Cases

  • Backup storage
  • Archive and cold data
  • Long-term logs or observability data
  • Container image or software repositories