> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt
> Use this file to discover all available pages before exploring further.

# October 31, 2025 - CoreWeave AI Object Storage Usage-Based Billing

> Three-tier usage-based billing model for AI Object Storage with Hot, Warm, and Cold pricing tiers

CoreWeave AI Object Storage Usage-Based Billing is now available. This introduces three tiers of storage pricing for AI Object Storage: Hot, Warm, and Cold. Usage-Based Billing is enabled by default starting October 31, 2025.

## Overview

CoreWeave AI Object Storage Usage-Based Billing introduces three tiers of storage pricing for AI Object Storage: Hot, Warm, and Cold. Usage-Based Billing is enabled by default starting October 31, 2025.

Usage-Based Billing classifies objects for pricing only. It does not move data or change an object's storage class, and data billed as Cold has the same performance as Hot or Warm data.

## How it works

When objects are evaluated during hourly billing cycles, they are classified as Hot, Warm, or Cold based on when they were last accessed:

| Pricing Tier | Description                                                                                                                                                                                                 |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Hot          | Objects that are newly uploaded or accessed within the last 7 days.                                                                                                                                         |
| Warm         | Objects that are accessed within the last 7 to 30 days.                                                                                                                                                     |
| Cold         | Objects that haven't been accessed for 30+ days. Specifically, an object is considered Cold if no bytes of the object have been read in the trailing 30 days at the time it is measured for hourly billing. |

### What counts as object access

During hourly billing cycles, the last access time is measured. The following actions reset the timer and bring objects back to the Hot tier:

| Action     | API Method                     | Description                                                                       |
| ---------- | ------------------------------ | --------------------------------------------------------------------------------- |
| **Upload** | `PutObject`, `UploadPart`      | When the object is first uploaded                                                 |
| **Read**   | `GetObject`                    | When the object is downloaded or accessed                                         |
| **Copy**   | `CopyObject`, `UploadPartCopy` | When the object is copied (both source and destination are considered "accessed") |