- Company sizes or stages where this product is overkill or insufficient
- Very small hobby projects should consider object storage or local disk options to avoid recurring provisioned-capacity charges for unmanaged block volumes.
- Industries or use cases where competitors are clearly superior
- If independently scalable performance controls (IOPS/throughput) at low capacity are required, evaluate Hyperdisk on GCP or comparable AWS/Azure disk types.
- Technical requirements that this product cannot meet
- True multi-host read-write shared disk at scale for generic file systems without clustered filesystem tooling.
- Budget constraints that make alternatives more appropriate
- If cost is driven by performance rather than capacity, PD may force provisioning of larger disks than needed; consider alternatives with separate performance pricing.
- Specific workflows or integrations where the product falls short
- Large multi-tenant GKE clusters using a disk-per-application pattern may encounter attachment and operational limits and should evaluate consolidation or alternative storage patterns.
- Red flags in the buying process
- Stopped VMs do not automatically stop disk charges; disks continue to bill until deleted.
- Regional disk capabilities do not imply active-active simultaneous attachments for typical setups; confirm attachment semantics for an intended HA design.
- Current limitations acknowledged by the vendor
- PD is network-attached block storage; performance depends on disk type, disk size, and VM vCPU/network caps.
- Max disk size: up to 64 TiB per PD volume; total attached PD capacity per VM can reach platform limits (for example, documented caps such as ~257 TiB total attached capacity per VM are relevant; consult latest docs for exact numbers by machine series).
- Attachment limits and multi-attach constraints exist (number of disks per VM, read-only multi-attach limits).
- Multi-writer mode (for PD-SSD) is in preview and limited; vendor guidance cautions that many common file systems are not designed for shared block storage without clustered coordination.
- Features on the roadmap (not yet available)
- No formal PD roadmap was collected in this research session; Google’s platform direction emphasizes Hyperdisk for newer performance and multi-attach capabilities.
- Scale limitations (at what volume/size does it break down?)
- Common scaling friction points include disk attachment count limits in large Kubernetes clusters and cost/performance trade-offs when more throughput is required than capacity provides.
- Security or compliance gaps
- No PD-specific compliance gaps were identified in public sources. Procurement teams should obtain platform-level SOC/ISO reports through Google Cloud compliance channels to confirm scope for PD in their controls matrix.
- API limitations or integration constraints
- Encryption key management options have operational implications (CMEK rotation/change constraints and key revocation behaviors should be evaluated in the context of VM lifecycle and recovery procedures).