DigitalOcean Volume Block Storage

Name: DigitalOcean Volume Block Storage
Brand: DigitalOcean
Rating: 4.6 (2562 reviews)

Leader

The comprehensive agentic cloud. ☁️

Est 2012|Valuation $14.3B|Raised $3.5B

LinkedIn 170K|Website|Web traffic 6.9M|FTEs 2,442|HQ Broomfield, CO

MarketsCloud Infrastructure Providers (IaaS/PaaS)

Platform CoversBackup and Data Protection Infrastructure Monitoring Infrastructure as Code (IaC)

DigitalOcean Volume Block Storage screenshot

Published Oct 8, 2026

01Common complaints

Consider alternatives when: 1. Multi-attach/shared storage semantics are required: DigitalOcean volumes attach to a single Droplet; for shared-write semantics, consider managed file services or providers with first-class managed filesystems. 2. Predictable high performance with dedicated tuning knobs is required: If independent IOPS/throughput provisioning is essential, hyperscaler block storage (e.g., AWS EBS with gp3/io2) may be more appropriate. 3. Account quota friction cannot be tolerated: If the rollout cannot wait for support to raise limits, select a provider with clearly surfaced self-service quotas. 4. A single-button backup model for all attached storage is required: Volumes are not included in Droplet backups and must be snapshotted separately. 5. Absolute lowest per‑GB cost is the primary criterion: Some providers may advertise materially lower per‑GB pricing (with differing tradeoffs in support, regions, and contractual assurances).

Deal disqualifiers (poor fit)

Requirements for shared-write access from multiple nodes without an external shared filesystem
Need to provision IOPS/throughput independently of VM class and to use rich native telemetry per volume
Inability to accommodate potential account quota increases via support prior to rollout

Documented constraints

Single-attachment: a volume can attach to only one Droplet at a time
Limits: per documentation, up to 15 volumes per Droplet, up to 5,000 volumes per account, volume sizes of 1 GiB–16 TiB
Volumes are not included in Droplet backups and must be snapshotted separately
Performance characteristics depend on Droplet class and workload pattern

Reported and account-variation constraints

Some accounts may experience initial volume creation limits (for example, community reports indicate cases of initial caps that required support escalation). These thresholds may not always be visible in-product until encountered.

Roadmap signals

No clearly documented public roadmap items specific to Volumes (for example, multi-attach or richer monitoring) were identified in the sources reviewed. Organizations with requirements in these areas should engage provider support or sales for roadmap clarification.

02Why they buy

Observed advantages

Flat per‑GiB pricing that is straightforward to estimate
Integration with Droplets and DOKS using common workflows such as PVCs
An explicit SLA for volume availability (99.99%) with documented service credit terms

Areas where competitors differ

AWS EBS provides a broader set of volume types and more granular performance controls
Some providers (e.g., Hetzner) may offer lower per‑GB pricing in specific regions, with different operational and contractual tradeoffs

03Field reports

Because Volumes is a component of the broader DigitalOcean platform, most public reviews address DigitalOcean overall rather than block storage in isolation. Aggregated review sources provide signals that are useful when considered alongside product documentation and community discussions.

Review platforms (TrustRadius, G2, PeerSpot, Trustpilot)

TrustRadius reports an overall score for the platform and highlights API and documentation strengths.
G2 aggregate material indicates generally favorable ratings for the platform as a whole.
PeerSpot notes positives such as ease of setup and stability in some cases, and calls out areas for improvement including support and monitoring.
Trustpilot shows mixed sentiment with varied comments on support and billing experiences.

Community / social (Reddit + DigitalOcean Community Q&A)

Common neutral or positive themes in community discussion: - Users frequently cite the user interface and developer-oriented APIs as reasons for selecting the platform. - The platform has an active community and public Q&A resources. Common negative themes (Volumes-specific and storage-adjacent): - Reported variance between vendor-published performance figures and observed application-level performance for specific workloads; filesystem choice and workload characteristics can impact results. - The platform supports single-attach volumes only; users seeking shared-write access across multiple nodes must design around this limitation. - Some users have reported quota or limit surprises (for example, modest initial volume creation caps on certain accounts) that required support engagement.

Direct quotes (selected, presented with context)

Positive (platform-level, includes storage among used services): - A community user commented that they use Droplets, block storage, and object storage on the platform and that those services have been reliable in their experience. Negative (Volumes performance vs AWS EBS, user report): - A community Q&A thread described a migration scenario in which a task that previously completed in seconds on one provider took several minutes on a DigitalOcean volume; the user reported improvement after changing the filesystem. Negative (limits/quota friction, user report): - A community post reported an initial account restriction to a modest amount of volume storage and requested clearer documentation on limits.

Why customers choose DigitalOcean/Volumes vs alternatives

Common reasons cited include:

Capacity-based pricing that is straightforward to estimate
A user interface and workflow that some teams find simpler than major hyperscalers
Integration with Droplets and DigitalOcean Kubernetes (DOKS)

Why some customers consider competitors or migrate away

Common considerations include:

Need for advanced storage tuning (provisioned IOPS, multiple volume types, multi-attach) not available in the same way on DigitalOcean
Observed performance differences for certain IO patterns relative to hyperscaler block storage
Support and billing process concerns reported by some users

Vendor-published example (vendor article)

A vendor-published article describes a customer using Droplets and Volumes to scale to a large user base. Vendor-published success narratives provide useful context about potential architectures but typically lack independent validation of metrics, methodology, and boundary conditions.

Critical evaluation: Treat marketing-case outcomes as illustrative rather than independently verified. Validate capacity, latency, and cost assumptions against internal benchmarks.

Vendor-commissioned economic study

A vendor-hosted Total Economic Impact (TEI) report is available. Vendor-commissioned TEI studies can provide useful modeling inputs but should be supplemented with customer-specific cost and labor models.

Community-reported negative example (micro-case)

A community thread describing an rsync workload that ran much slower after migration illustrates how application-level IO behavior can differ across providers and how filesystem selection and tuning can materially affect results.

What it tells buyers: Benchmark workloads and incorporate filesystem and tuning considerations into migration plans.

04Best fit

Best-fit company profile

Company size: typically small to mid-sized organizations (individual developers through SMB engineering teams). Larger enterprises may use DigitalOcean for specific workloads but often require additional compliance evidence and advanced storage controls.

Strong-fit industries and workloads

SaaS applications hosted on Droplets that separate data volumes (e.g., logs, uploads)
Web applications that need predictable storage expansion without frequent compute resizes
Kubernetes workloads on DOKS using PVCs for stateful services with appropriate architecture

Buyer personas

DevOps and platform engineers
Full-stack developers operating self-managed infrastructure
Technical founders and CTOs evaluating cost and operational simplicity for early-stage infrastructure

Qualification criteria (good fit)

Ability to accept or design around single-attach volumes
Workloads that are not extremely latency-sensitive, or where teams will perform workload-specific benchmarking and tuning
Preference for predictable capacity-based billing without selecting among multiple volume-type options

05The pitch

What the product does (core value proposition)

DigitalOcean Volumes Block Storage is a network-attached block device that can be attached to DigitalOcean Droplets (virtual machines) and used as additional disk capacity independent of CPU/RAM. The product uses flat per‑GiB pricing and is intended for teams that require expandable block storage without resizing compute. Key functional capabilities (as described by DigitalOcean): - Provision volumes from small GiB sizes up to multiterabyte volumes - Resize volumes, move them between Droplets, and create snapshots - Use with DigitalOcean Kubernetes (DOKS) via persistent volume claims (PVCs) - SLA-backed uptime (high-availability SLA)

Target market and market positioning

DigitalOcean targets developers, startups, and small-to-midsize businesses (SMBs) that prioritize straightforward infrastructure and a simplified user interface relative to major cloud hyperscalers. Volumes Block Storage presents fewer exposed configuration options than some hyperscaler block storage products (for example, explicit IOPS/throughput provisioning is not surfaced in the same way) and uses a flat per‑GiB pricing model.

Get a comprehensive analysis of DigitalOcean Volume Block Storage including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →