Skip to main content
High-performance computing (HPC) workloads, especially those involving AI and ML applications, typically use large training datasets, require data sharing between Nodes, and need fast, temporary storage for caching and logging purposes. CoreWeave offers a variety of storage solutions designed to meet the demands of these intensive applications. Choose a storage product below to get started, or continue reading to compare the options based on your workload’s requirements.

CoreWeave AI Object Storage

Purpose-built, S3-compatible object storage for training datasets, model weights, checkpoints, and other distributed bulk data.

Distributed File Storage

POSIX-compliant shared filesystem with high throughput and low latency for multi-Node access.

Dedicated VAST Storage

Single-tenant VAST clusters co-located with your GPU infrastructure for petabyte-scale capacity and full cluster control.

Local Storage

High-performance, Node-local NVMe storage for temporary scratch space, caching, and logs.

CoreWeave Database

Managed, PostgreSQL-compatible database service that runs inside your CKS cluster.

​
Choose the right storage

Most workloads use more than one storage type. Choose storage based on data class and I/O profile: keep the active temporary working set on Local Storage, durable portable artifacts in Object Storage, and POSIX-active data in DFS. Does your data need to outlive the Pod or Node? If not, use Local Storage. Local Storage provides NVMe-backed scratch space for caches, logs, and intermediate artifacts, but it does not survive Pod deletion or Node reboots. If yes, continue. What interface and I/O pattern does your application use? Use CoreWeave AI Object Storage when your application uses an S3-compatible API and primarily reads or writes large objects with parallel, contiguous access, such as training datasets, model weights, checkpoints, backups, or data that must be accessible across clusters or availability zones. Use LOTA from within CoreWeave clusters to cache hot objects on local Node NVMe. Use Distributed File Storage when your application requires a POSIX filesystem, such as persistent home directories, shared workspaces, frequent file updates or directory listing, or small and random I/O.
DFS cannot be mounted from another cluster, availability zone, or region. If an application requires both POSIX access and multi-cluster data sharing, use Object Storage as the durable source of truth and stage data to DFS or Local Storage within each cluster.
The following table summarizes the three self-serve storage options: Need petabyte-scale capacity or full cluster control? Dedicated VAST Storage provides a single-tenant VAST cluster co-located with your GPU infrastructure, with multi-protocol access (NFS, S3, NVMe/TCP, and SQL) and petabyte-scale capacity. Dedicated VAST is not self-serve: provisioning requires coordination with CoreWeave. Contact Sales to discuss sizing and availability.
Last modified on August 13, 2026