Veeam Immutable Storage Estimator
Model what immutable object storage costs. See what the number depends on.
Veeam immutable storage cost is not capacity multiplied by a price. Locked objects stay billable until their lock periods end, Veeam extends locks on data that is still live, and each provider adds its own minimum durations, minimum object sizes and request charges. This estimator simulates the repository day by day and reports retained capacity, billed capacity and request charges separately, with provider minimums applied to billed capacity, so you can see which part of the number is driving it.
A single capacity-times-price figure hides what it assumed. This estimator labels every result three ways: whether the pricing behind it is verified, how much of the behavior is modeled versus estimated, and how old the evidence is. It does not tell you which backup strategy is cheaper or safer. It computes the cost of the inputs you give it and compares two scenarios as arithmetic. Whether a retention design is the right one for your recovery requirements is a Data Protection architecture decision, and the cost of that design is only one input to it.
What the Veeam Immutable Storage Estimator Surfaces
01 — WORKLOAD AND GROWTH
Source size, monthly growth, daily change rate, data reduction ratio and Veeam block size set how many objects exist and how large each stored object is. The reduction ratio is a planning assumption, and the tool labels it as one.
02 — VEEAM REPOSITORY BEHAVIOR
Direct-to-object repositories for Veeam 12.1.2 and 13. Block generation, the immutability period, first expiry and lock extension are modeled per version, and each behavior carries an evidence status. Where Veeam documents a default, the tool uses it and lets you override it.
03 — PROVIDER PRICING PROFILES
AWS S3 Standard and Standard-IA, Azure Blob Hot and Cool (LRS), and Wasabi pay-as-you-go. Each profile records its rates, sources, retrieval date and verification status, and the Assumptions panel shows them.
04 — DAY-LEVEL LIFECYCLE
Changed blocks supersede the oldest data, only data still live at a generation boundary is extended, GFS points hold references, and provider minimum durations, minimum object sizes and account minimums apply to billed capacity rather than retained capacity.
05 — RECOVERY, PRICED SEPARATELY
A recovery scenario prices the reads and egress of a restore. It is never added to the storage total.
06 — ANALYSIS AND EXPORT
A two-scenario compare, a sensitivity ranking, an exact attribution of the difference between scenarios, a crossover search, an assumptions panel with sources, and CSV, JSON and print-to-PDF export.

How to Read a Result: Three Independent Labels
Every Veeam immutable storage result carries three labels. They are not combined into one severity, because they answer different questions.
| Label | Values | What it tells you |
|---|---|---|
| Pricing status | Pricing verified; Unverified pricing; Incomplete | Whether every rate behind the total is backed by recorded evidence. Unverified pricing means every line is priced and the arithmetic is complete, but at least one rate has an open verification gate. Incomplete means a required price is missing, so no total is shown. |
| Behavior confidence | Modeled; Estimate; Override-dependent | How the behavior behind a line was derived: a documented rule, a planning estimate, or a value you set yourself. |
| Evidence freshness | Current; Stale; No date | How old the pricing evidence is, measured against a 90-day window. A recent date does not make a price verified. |
A verified price can rest on an estimated behavior, and an unverified price can still produce an arithmetically complete total. The labels carry through compare, sensitivity, attribution, crossover, the recovery view and every export, so a number never leaves the tool without them.
What Is Not in the Number
The Veeam immutable storage total covers storage only. Recovery reads and egress are priced in a separate scenario, and background list and read traffic is listed as not modeled instead of being counted as zero. For restore-time cost across regions and providers, use the Universal Cloud Restore Calculator.
Immutability is a storage property. Whether the vault holds when an attacker has your credentials is an isolation question, covered in Cyber Vault Architecture, and the estimator does not price it. The same limit applies to retention policy: Object Lock is a feature, not a recovery design, and a lock period that costs more storage is not wrong for that reason.
The compare view reports the difference in cost and capacity between Scenario A and Scenario B. The attribution view splits that difference across the inputs that changed, and the crossover view shows where two scenarios trade places as one input moves. None of them concludes that either scenario is better.
Pricing coverage by profile:
| Profile | Pricing status |
|---|---|
| Azure Blob Hot (LRS) | Verified |
| Azure Blob Cool (LRS) | Verified |
| Wasabi pay-as-you-go | Verified |
| AWS S3 Standard | Unverified pricing |
| AWS S3 Standard-IA | Unverified pricing |
Unverified pricing does not mean the rates are known to be wrong. It means the evidence is not yet sufficient to call them verified. If this table and the tool differ, the tool is correct: it shows the status, open gates, sources and retrieval date for the profile you selected.

Veeam Immutable Storage Estimator: Key Features
- Deterministic Veeam immutable storage modeling: the same inputs produce the same result. There is no AI inference, and the simulation runs at day resolution.
- Retained versus billed capacity: the tool reports both, so you can see where a minimum duration, a minimum object size or an unexpired lock separates them.
- Three result labels: pricing status, behavior confidence and evidence freshness stay separate on every result and every export.
- Two-scenario analysis: compare, sensitivity, exact attribution and crossover, with deltas shown only when both scenarios are complete.
- Client-Side Only: No data leaves the browser. No telemetry, no server-side logging, no account required.
THE ESTIMATOR PRICES THE RETENTION POLICY.
A REVIEW TESTS WHAT IT PROTECTS.
The estimate says what a repository design costs. It cannot say whether the design recovers under attack: that needs the restore path, the credentials and the isolation boundary reviewed together.
|
>_ Architectural Guidance
Infrastructure Architecture ReviewA vendor-agnostic review of the repository design against your recovery requirements, using the estimator output as the cost baseline.
|
>_ The Dispatch
Architecture Playbooks. Field-Tested Blueprints.Playbooks on immutable backup, recovery design and the cost of getting either one wrong.
Zero spam. Unsubscribe anytime. |
Frequently Asked Questions
Q: What does the Veeam Immutable Storage Estimator actually measure?
A: It simulates a Veeam direct-to-object repository day by day and reports storage cost over 12 or 36 months as separate lines: billed storage after provider billing rules (minimum durations, minimum object sizes, account minimums), object PUT requests and immutability extension requests. Early-deletion exposure is reported where it applies, and background list and read traffic is listed as not modeled. It reports retained capacity and billed capacity separately, because they differ whenever a minimum duration, a minimum object size or an unexpired lock applies. Recovery is modeled as a separate scenario and is not part of the storage total.
Q: How is this different from a provider pricing calculator?
A: A provider calculator prices the capacity and requests you specify. It does not know how Veeam writes blocks, when it extends locks, or which data is still live at a generation boundary. The estimator models that behavior, labels each part of it as modeled, estimated or set by you, and prices the result against a recorded rate profile. It is not a quote: provider invoices depend on your account terms.
Q: What scenarios does the Veeam immutable storage estimator cover?
A: Veeam 12.1.2 and 13 direct-to-object repositories, with AWS S3 Standard and Standard-IA, Azure Blob Hot and Cool (LRS), and Wasabi pay-as-you-go, over a 12- or 36-month horizon. It supports GFS points, scheduled active fulls and existing storage in the same account. It does not model other repository types.
Q: Why can a result say Unverified pricing?
A: Verified means every rate used is backed by evidence recorded in the tool. Unverified pricing means every line is priced and the arithmetic is complete, but at least one rate has an open verification gate, for example a rate that could be confirmed only in rounded form. It does not mean the rates are known to be wrong. A recent retrieval date is not verification, which is why evidence freshness is a separate label.
Q: Does it tell me which backup strategy to choose?
A: No. The estimator computes the cost of the inputs you give it. Compare shows the difference between two scenarios, and attribution and sensitivity show which inputs drive it. None of them say which design is cheaper in general or safer. That depends on the workload, the retention requirement and the recovery objectives, which are architecture decisions outside the tool.
Q: Is any data sent to a server or stored?
A: No. The tool runs in your browser and makes no network requests beyond loading its own page and fonts. Inputs are not transmitted, no cookies are set, there is no analytics, and nothing is stored between sessions. Exports are generated locally.
Additional Resources
🔒 Privacy Architecture: No cookies. No tracking pixels. No server-side database.
This logic runs entirely in your local browser session.