CoreWeave AI Object Storage Usage-Based Billing is now available. This introduces a third tier of storage pricing for AI Object Storage: Hot, Warm, and Cold. Usage-Based Billing replaces the previous Automated Archive feature, and is enabled by default starting October 31, 2025. CoreWeave AI Object Storage Automated Archive is now available. This feature automatically archives inactive objects after 30 days.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.
Overview
CoreWeave AI Object Storage Automated Archive automatically archives inactive objects after 30 days. This feature is useful for reducing storage costs by archiving infrequently accessed objects. Learn more about pricing. Data billed as Automated Archive has the same performance as non-archived data.This feature was enabled by default starting October 1, 2025, and then replaced by Usage-Based Billing starting October 31, 2025.
How it works
When objects are evaluated for archiving during hourly billing cycles, they are classified as either active or inactive:- Objects that are newly uploaded or accessed within the last 30 days are considered active.
- Objects that haven’t been accessed for 30+ days are considered inactive. Specifically, an object is inactive 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
Objects are evaluated for archiving during hourly billing cycles. The 30-day period is measured from the last access time. The following actions reset the 30-day timer and keep objects active:| 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”) |