Backup Storage Prices

Checked

Storage classes

Where each OVHcloud class stops being the cheaper option

A five-class OVHcloud comparison with a 361.85% Infrequent Access crossover, a 49.00% Active Archive crossover, an unresolved Cold Archive retrieval conflict, and free public egress kept explicit.

Put your own numbers through the calculator to see what this meter does to a normal month and to the day you restore.

OVHcloud needs two warmer baselines because the captured classes are not all in one Region

The captured High Performance and Infrequent Access records are both in GRA, so they form one compatible byte comparison. High Performance costs $0.0202794 per GiB-month, Infrequent Access costs $0.0043581 per GiB-month, and retrieval costs $0.0044 per GiB. The crossover is 361.85% read per month. [1]

The captured Standard 3-AZ, Active Archive, and Cold Archive records are in EU-WEST-PAR. Active Archive costs $0.0053217 per GiB-month and retrieval costs $0.0212 per GiB. Against the first Standard 3-AZ storage band at $0.0157096, the crossover is 49.00% per month. [1]

OVHcloud needs two warmer baselines because the captured classes are not all in one Region
Comparable pairArithmeticAccess breakpointMinimum-duration treatmentSource ref
GRA High Performance versus Infrequent Access($0.0202794 - $0.0043581) / $0.0044361.85% per month3.6185 full reads during Infrequent Access's 30-day minimum[1]
EU-WEST-PAR Standard 3-AZ first band versus Active Archive($0.0157096 - $0.0053217) / $0.021249.00% per monthMinimum duration not published, so minimum-window access count is not published[1] [2]
EU-WEST-PAR Standard 3-AZ versus Cold ArchiveRetrieval rate not published in the datasetnot published180 days[1] [3]
Standard 3-AZ versus High PerformanceDifferent captured Regions and different service capabilitynot comparabledoes not apply[1] [2]

Every class has a breakpoint or an explicit refusal to invent one

The Standard 3-AZ record uses graduated storage bands. Its first band is the compatible baseline for the captured Active Archive result, so higher-volume workloads require the applicable Standard band to be substituted before the crossover is recomputed. [1]

The dataset records incoming, internal, and public outgoing traffic as included for all five classes, and records Class A and Class B operations as not charged. Retrieval and minimum duration are therefore the class-changing byte meters, except where a missing retrieval rate blocks the result. [1]

Every class has a breakpoint or an explicit refusal to invent one
Class and RegionStorage and retrievalMinimum durationBreak-even access frequencyWrong access patternSource ref
Standard 3-AZ, EU-WEST-PAR$0.0157096/GiB-month in the first band; retrieval not chargeddoes not applydoes not apply; warmer baseline for the Paris archive recordsA workload whose required Region or capability is represented only by another captured record[1] [2]
High Performance, GRA$0.0202794/GiB-month; retrieval not chargeddoes not applydoes not apply; warmer baseline for GRA Infrequent AccessA workload that does not need the performance capability and reads below the Infrequent Access crossover[1] [2]
Infrequent Access, GRA$0.0043581/GiB-month + $0.0044/GiB retrieved30 days361.85% per month; 3.6185 full reads during the minimumMore than 361.85% read per month or delete, overwrite, move, or transition before day 30[1] [2]
Active Archive, EU-WEST-PAR$0.0053217/GiB-month + $0.0212/GiB retrievednot published49.00% per month versus the first Standard 3-AZ band; minimum-window result not publishedMore than 49.00% read per month or any retention plan that needs a published minimum duration[1] [2]
Cold Archive, EU-WEST-PARStarting at $0.002/GiB-month; retrieval rate not published in the dataset180 daysnot publishedAny restore plan that requires a complete price, plus mutation before day 180[1] [3]

Public egress is not charged, but archive retrieval can still dominate

The captured worldwide price list includes public outgoing traffic for every OVHcloud class. A public restore therefore keeps egress as not charged rather than dropping the line, while Infrequent Access and Active Archive retain their per-GiB retrieval charges. [1]

Restoring without mutating the source does not incur an early-deletion remainder. Add that meter only when the workflow also deletes, overwrites, moves, or transitions the source before a published minimum. Cold Archive has a 180-day minimum; Active Archive's minimum remains not published in the dataset. [2] [3]

Public egress is not charged, but archive retrieval can still dominate
Restore lineStandard and High PerformanceInfrequent AccessActive ArchiveCold ArchiveSource ref
Retrievalnot charged$0.0044/GiB$0.0212/GiBnot published in the dataset[1] [3]
Public egressnot chargednot chargednot chargednot charged[1]
Class A and Class B operationsnot chargednot chargednot chargednot charged[1]
Early deletion on read-only sourcedoes not applydoes not applydoes not applydoes not apply[2] [3]

The current price list exposes a Cold Archive retrieval rate that the dataset omits

A live check on 2026-07-26 found a $0.011 per GiB Cold Archive retrieval rate on OVHcloud's official public-cloud price list. The July 25 provider record says the rate is not published because the checked product text stated only that retrieval fees apply. [4] [3]

The live rate is not imported into the break-even because the project contract requires rates to come from providers.json. Cold Archive therefore remains stale with a not published crossover until the dataset is refreshed and its dataset-to-source mismatch is resolved. [4] [3]

The current price list exposes a Cold Archive retrieval rate that the dataset omits
PropertyJuly 25 datasetOfficial price list checked July 26Page treatmentSource ref
Cold Archive retrievalnot published$0.011/GiBstale; excluded from the crossover[3] [4]
Cold Archive storageStarting at $0.002/GiB-month$0.0000027/GiB-hour on the current price listDataset rate retained; no silent replacement[3] [4]
Cold Archive minimum180 days180 daysNo disagreement[3] [4]

Sources

Every figure above comes from one of these pages, on the date shown. Each numbered reference in the text links to its entry here. Vendors change prices; if a date looks old, check the source. Three vendors publish a machine-readable feed and the rest are re-checked by hand, which is why the dates are not uniform.

The source ledger4 sources
  1. 1OVHcloud: Public cloud priceswww.ovhcloud.com · checked 2026-07-25 15:34:44+00:00
  2. 2OVHcloud documentationdocs.ovhcloud.com · checked 2026-07-25 15:34:44+00:00
  3. 3OVHcloud: Cold archivewww.ovhcloud.com · checked 2026-07-25 15:34:44+00:00
  4. 4OVHcloud: Public cloud priceswww.ovhcloud.com · checked 2026-07-26