docs: Add High-Performance Storage documentation

docs.json

@@ -218,6 +218,7 @@
             "group": "Storage",
             "pages": [
               "storage/network-volumes",
+              "storage/high-performance-storage",
               "storage/s3-api"
             ]
           },

get-started/concepts.mdx

@@ -29,7 +29,7 @@ A managed compute cluster with high-speed networking for multi-node distributed
 
 ## [Network volume](/storage/network-volumes)
 
-Persistent storage that exists independently of your other compute resources and can be attached to multiple Pods or Serverless endpoints to share data between machines.
+Persistent storage that exists independently of your other compute resources and can be attached to multiple Pods or Serverless endpoints to share data between machines. Available in Standard and [High-Performance](/storage/high-performance-storage) tiers.
 
 ## [S3-compatible API](/storage/s3-api)
 

pods/storage/types.mdx

@@ -46,6 +46,10 @@ Encryption applies only to volume disk. Container disk and network volumes canno
 
 Network volumes provide permanent storage that exists independently from any Pod. You can attach a network volume to multiple Pods, transfer it between machines, and retain your data even after deleting a Pod. This makes network volumes ideal for shared datasets, collaborative workflows, and portable storage.
 
+Network volumes are available in two tiers:
+- **Standard Storage**: Cost-effective for general-purpose work.
+- **[High-Performance Storage](/storage/high-performance-storage)**: Premium tier with up to 3x throughput and 4x IOPS for demanding workloads.
+
 [Learn more about network volumes](/storage/network-volumes).
 
 <Note>

serverless/storage/overview.mdx

@@ -15,7 +15,7 @@ All data saved by a worker's [handler function](/serverless/workers/handler-func
 
 ### Network volume
 
-Persistent storage that can be attached to multiple workers. Ideal for sharing datasets, storing large models, and preserving data beyond individual worker sessions.
+Persistent storage that can be attached to multiple workers. Ideal for sharing datasets, storing large models, and preserving data beyond individual worker sessions. Available in Standard and [High-Performance](/storage/high-performance-storage) tiers.
 
 See [Network volumes for Serverless](/storage/network-volumes#network-volumes-for-serverless).
 

storage/high-performance-storage.mdx

@@ -0,0 +1,106 @@
+---
+title: "High-Performance Storage"
+description: "Premium storage tier for demanding AI workloads with up to 3x throughput and 4x IOPS."
+---
+
+import { PodsTooltip, ServerlessTooltip, WorkersTooltip, InstantClusterTooltip } from "/snippets/tooltips.jsx";
+
+High-Performance Storage is a network volume tier designed for data-intensive AI workloads. Its parallel storage architecture delivers high throughput and low latency under heavy concurrent load, even when thousands of processes access it simultaneously.
+
+The storage uses [Solidigm](https://www.solidigm.com/) high-density SSDs optimized for AI data pipelines.
+
+## Performance comparison
+
+In internal benchmarks, High-Performance Storage delivers up to 3x the throughput and 4x the IOPS of Standard Storage on parallel operations.
+
+|                  | Standard Storage                                      | High-Performance Storage                          |
+|------------------|-------------------------------------------------------|---------------------------------------------------|
+| Best for         | General-purpose work, development, cost-sensitive jobs | Training, fine-tuning, latency-sensitive inference |
+| Throughput       | High                                                  | Up to 3x higher                                    |
+| IOPS             | High                                                  | Up to 4x higher                                    |
+| Concurrency      | Moderate                                              | Optimized for massive parallelism                  |
+| Relative cost    | Lower                                                 | Premium                                            |
+
+Both tiers are fully supported. Choose based on whether storage performance sits on the critical path of your workload.
+
+## When to choose High-Performance Storage
+
+If your GPUs ever sit idle waiting on data (slow dataloaders, long checkpoint writes, sluggish model loads) you're a candidate for High-Performance Storage. If storage isn't your bottleneck, Standard Storage is the cost-effective choice.
+
+| Use case                     | Why it helps                                                                                          |
+|------------------------------|-------------------------------------------------------------------------------------------------------|
+| Training                     | Feeds GPUs at the rate they can consume data, preventing I/O bottlenecks and reducing training time.  |
+| Fine-tuning and checkpointing | Speeds up write-heavy operations like checkpoints, so jobs spend more time computing.                 |
+| Inference                    | Cuts model load time from a central volume, lowering endpoint cold-start latency.                     |
+
+## Create a High-Performance volume
+
+High-Performance Storage is available as a network volume type in select data centers.
+
+<Tabs>
+  <Tab title="Web console">
+    1. Navigate to **Storage** > **Network Volumes** in the [Runpod console](https://console.runpod.io).
+    2. Click **New Network Volume**.
+    3. Select a data center. Data centers that support High-Performance Storage display a purple diamond icon.
+    4. Under **Storage Type**, select **High-Performance**.
+    5. Enter a name and set the volume size in GB. The console displays per-GB and total monthly cost as you adjust.
+    6. Click **Create Network Volume**.
+  </Tab>
+  <Tab title="REST API">
+    ```bash
+    curl --request POST \
+      --url https://rest.runpod.io/v1/networkvolumes \
+      --header 'Authorization: Bearer RUNPOD_API_KEY' \
+      --header 'Content-Type: application/json' \
+      --data '{
+      "name": "my-hps-volume",
+      "size": 100,
+      "dataCenterId": "US-KS-2",
+      "storageType": "high-performance"
+    }'
+    ```
+
+    See the [network volumes API reference](/api-reference/network-volumes/POST/networkvolumes) for details.
+  </Tab>
+</Tabs>
+
+## Attach to your workloads
+
+High-Performance volumes work across the platform like standard network volumes.
+
+- **<PodsTooltip />**: Attach during Pod creation, or from the volume manager for existing setups.
+- **<ServerlessTooltip />**: Attach to an endpoint to speed up model loading and reduce cold-start latency. See [Network volumes for Serverless](/storage/network-volumes#network-volumes-for-serverless).
+- **<InstantClusterTooltip />s**: New clusters can be provisioned with High-Performance Storage by default.
+
+## Pricing
+
+High-Performance Storage is priced per-GB at a premium to Standard Storage. The console displays per-GB and total monthly cost as you configure a volume.
+
+<Note>
+Exact pricing varies by data center. Check the volume creation flow in the console for current rates.
+</Note>
+
+## FAQ
+
+**Is Standard Storage going away?**
+
+No. Standard Storage remains fully supported and is the recommended choice for general-purpose work. High-Performance Storage is an additional tier for performance-sensitive workloads.
+
+**Which data centers support High-Performance Storage?**
+
+Multiple US and European data centers support High-Performance Storage, with more rolling out over time. Supported data centers display a purple diamond icon in the network volume creation flow.
+
+**Can I migrate an existing Standard volume to High-Performance?**
+
+Direct migration is not currently supported. To move data to a High-Performance volume, create a new High-Performance volume and transfer your data using the [S3-compatible API](/storage/s3-api) or [runpodctl](/storage/network-volumes#using-runpodctl).
+
+## Next steps
+
+<CardGroup cols={2}>
+  <Card title="Network volumes" href="/storage/network-volumes" icon="hard-drive" horizontal>
+    Learn more about network volume management and features.
+  </Card>
+  <Card title="S3-compatible API" href="/storage/s3-api" icon="cloud" horizontal>
+    Manage files without launching compute resources.
+  </Card>
+</CardGroup>

storage/network-volumes.mdx

@@ -9,11 +9,23 @@ Network volumes provide persistent storage that exists independently of your com
 
 Network volumes are backed by high-performance NVMe SSDs with transfer speeds of 200-400 MB/s (up to 10 GB/s peak).
 
+## Storage tiers
+
+Network volumes are available in two tiers:
+
+- **Standard Storage**: Cost-effective storage for general-purpose work, development, and workloads where storage isn't the bottleneck.
+- **[High-Performance Storage](/storage/high-performance-storage)**: Premium tier with up to 3x throughput and 4x IOPS, optimized for training, fine-tuning, and latency-sensitive inference.
+
+Select the storage tier when creating a network volume. For details on choosing between tiers, see [High-Performance Storage](/storage/high-performance-storage).
+
 ## Pricing
 
+**Standard Storage:**
 - **First 1 TB**: \$0.07/GB/month
 - **Beyond 1 TB**: \$0.05/GB/month
 
+**High-Performance Storage** is priced at a premium. See the [High-Performance Storage](/storage/high-performance-storage#pricing) page for details.
+
 <Warning>
 If your account lacks funds to cover storage costs, your network volume may be terminated, after which data cannot be recovered.
 </Warning>
@@ -28,8 +40,9 @@ Volume size can be increased later but cannot be decreased. For volumes beyond 4
   <Tab title="Web console">
     1. Navigate to the [Storage page](https://www.console.runpod.io/user/storage).
     2. Click **New Network Volume**.
-    3. Select a datacenter, enter a name, and specify size in GB.
-    4. Click **Create Network Volume**.
+    3. Select a data center, enter a name, and specify size in GB.
+    4. Select a storage tier: **Standard** or **High-Performance** (available in select data centers).
+    5. Click **Create Network Volume**.
   </Tab>
   <Tab title="REST API">
     ```bash