Storage classes
Vultr tiers are bundles and performance, not access frequency
A five-tier Vultr comparison that declines false retrieval crossovers for four performance tiers, keeps Archive retrieval not published, shows a partial 22.22-day restored-copy threshold, and makes bandwidth overage part of the restore decision.
Put your own numbers through the calculator to see what this meter does to a normal month and to the day you restore.
Four online tiers are capability choices, not cheaper retrieval classes
Standard, Premium, Performance, and Accelerated each bundle 1,000 GB of storage and 1,000 GB of outbound transfer, then charge different storage overage rates and fixed monthly fees. Retrieval is not charged for all four. Because the tiers sell different performance capability and have no retrieval meter to offset, an access-frequency crossover among them is not comparable. [1]
Archive is a separate $6 monthly bundle with 1,000 GB of archive storage, 100 GB of unarchived storage, and 1,000 GB of outbound transfer. The dataset records no per-GB retrieval rate, and records restored copies at the Standard storage rate. A complete Archive access-frequency crossover is therefore not published. [2] [1]
| Tier | Base bundle | Additional storage | Retrieval state | Access-frequency result | Source ref |
|---|---|---|---|---|---|
| Standard | $18/month with 1,000 GB storage and 1,000 GB outbound | $0.018/GB-month | not charged | does not apply; online capability baseline | [1] |
| Premium | $36/month with 1,000 GB storage and 1,000 GB outbound | $0.036/GB-month | not charged | not comparable; capability changes without a retrieval crossover | [1] |
| Performance | $50/month with 1,000 GB storage and 1,000 GB outbound | $0.05/GB-month | not charged | not comparable; capability changes without a retrieval crossover | [1] |
| Accelerated | $100/month with 1,000 GB storage and 1,000 GB outbound | $0.10/GB-month | not charged | not comparable; capability changes without a retrieval crossover | [1] |
| Archive | $6/month with 1,000 GB archive, 100 GB unarchived, and 1,000 GB outbound | $0.006/GB-month archive; restored copies $0.018/GB-month | not published | not published; temporary-copy storage is known but the retrieval meter is incomplete | [2] [1] |
Visible restored-copy storage erases the 1,000 GB bundle saving after 22.22 days
At exactly 1,000 GB stored, the Archive base fee is $12 per month below Standard. Archive includes 100 GB of unarchived storage, so a full 1,000 GB readable copy leaves 900 GB billed at $0.018 per GB-month. That copy costs 900 x $0.018 / 30 = $0.54 per day, and $12 / $0.54 = 22.22 days erases the visible base-fee saving. [2] [1]
This is a partial breakpoint, not a complete restore break-even. The dataset's retrieval rate is not published, request prices are not published, minimum storage duration is not published, and the result changes with stored capacity and readable-copy size. None of those states is treated as zero. [2] [1]
| 1,000 GB Archive versus Standard input | Arithmetic | Result | Source ref |
|---|---|---|---|
| Monthly base-fee saving | $18 Standard - $6 Archive | $12.00 | [1] [2] |
| Billable restored copy | 1,000 GB restored - 100 GB unarchived included | 900 GB | [2] |
| Readable-copy cost per day | 900 GB x $0.018/GB-month / 30 | $0.54/day | [2] [1] |
| Visible storage breakpoint | $12.00 / $0.54 per day | 22.22 restored-copy days per month | [2] [1] |
| Per-GB retrieval | Dataset meter | not published | [2] |
| Complete Archive break-even | Visible storage plus unpriced retrieval, requests, and capacity-dependent bundle effects | not published | [2] [1] |
A 2,200 GB public restore consumes the whole $12 Archive base-fee saving in egress
Every captured Vultr tier includes 1,000 GB of monthly outbound transfer and charges $0.01 per additional GB. A 2,200 GB public restore therefore costs (2,200 - 1,000) x $0.01 = $12.00 in egress, equal to the Archive-versus-Standard base-fee gap before temporary-copy storage and the not published retrieval line. [1] [2]
A read-only Archive restore does not create an early-deletion charge. The dataset does not publish any minimum storage duration or early-deletion method, so those mutation fields remain not published rather than becoming zero. [2]
| 2,200 GB Archive restore line | Arithmetic | Charge or state | Source ref |
|---|---|---|---|
| Included outbound transfer | min(2,200 GB, 1,000 GB) | 1,000 GB not charged | [1] [2] |
| Additional outbound transfer | (2,200 GB - 1,000 GB) x $0.01/GB | $12.00 | [1] [2] |
| Archive retrieval | Per-GB meter | not published | [2] |
| Restored-copy storage | $0.018/GB-month beyond included unarchived capacity for the readable duration | conditional | [2] [1] |
| Class A and Class B operations | Rates not captured | not published | [1] |
| Early deletion | Read-only source | does not apply for this restore; mutation method otherwise not published | [2] |
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 ledger2 sources
- 1Vultr documentation: How is object storage billeddocs.vultr.com · checked 2026-07-25 15:34:44+00:00
- 2Vultr documentation: Limitsdocs.vultr.com · checked 2026-07-25 15:34:44+00:00