What makes a backup “immutable,” and why does that one word often double the bill? If you have compared storage quotes lately, you have probably noticed that a locked, tamper-proof copy of your data costs far more than a normal backup. The reasons are not mysterious once you break them down. Immutability pricing comes down to retention rules, minimum storage commitments, and the way vendors charge for data you are not allowed to delete early.
This article walks through how backup immutability is priced, where the hidden costs hide, and how to compare quotes without getting fooled by a low headline number.
What Backup Immutability Actually Means
Backup immutability means a stored copy of your data cannot be altered or deleted during a set period, even by an administrator or an attacker who has stolen admin credentials. It is the last line of defense against ransomware, insider threats, and plain human error.
The concept traces back to WORM storage (write once, read many), a standard that dates to the early days of optical and tape media. Modern cloud providers implement it through object lock and retention policies, which you can read about in the Write once read many overview on Wikipedia.
There are three common mechanisms, and each is priced differently:
- Object Lock / WORM buckets on cloud storage, where a retention date is set per object or per bucket.
- Legal hold, which blocks deletion indefinitely until a person removes the hold.
- Immutable snapshots or air-gapped appliances, where a copy is physically or logically isolated from the production network.
The key pricing insight: immutability is not a feature you buy once. It is a policy you apply, and the policy itself creates cost obligations.
Why Immutable Storage Costs More Than Ordinary Backup
Ordinary backup storage is cheap because vendors assume some data will be deleted early, compressed, or moved to cold tiers. Immutable storage breaks all three assumptions:
- You cannot delete early. Once locked, an object stays until the retention period ends. The vendor bills for the full term.
- You pay a minimum retention commitment. Many providers set a floor, such as 30, 90, or 180 days, and charge for that period whether you need it or not.
- Replication of locked copies costs extra. If you keep a second immutable copy in another region for disaster recovery, you pay storage and transfer fees twice.
That is why a quote for “1 TB of immutable backup” can land three to five times higher than 1 TB of standard object storage. The extra money is not margin alone. It is the cost of a guarantee.
The Main Pricing Models You Will Encounter
Vendors rarely publish one simple rate. Instead, immutability pricing usually combines several meters. The table below shows the models you are most likely to see.
| Pricing model | How it is billed | Typical cost driver | Watch out for |
|---|---|---|---|
| Per-GB-month storage | Flat rate per gigabyte stored each month | Total locked capacity | Minimum retention floors |
| Capacity tier with commit | Discounted rate in exchange for a 1–3 year commitment | Prepaid or committed volume | Overage rates above the commit |
| Per-object fees | Charge per locked object or per lock operation | Object count, not size | Millions of small files inflate cost |
| Appliance-based (air-gapped) | Hardware plus subscription | Appliance size and support term | Refresh cycles and shipping |
| Replication add-on | Per-GB transfer plus storage in a second region | Cross-region copies | Egress and request charges |
Most organizations choose a mix: a committed capacity tier for most data, plus per-request charges for lock and release operations. If you are already comparing storage options for other workloads, the same rule—match tier to access pattern—applies, as with choosing among the best external hard drives for backup for local copies rather than paying for cloud tiers.
The Hidden Line Items That Blow Up Budgets
Headline storage rates are only part of the story. In practice, these line items cause most budget surprises.
Minimum retention periods
A provider might require a 90-day minimum on locked objects. If your policy locks data for 30 days, you still pay for 90. Multiply that by terabytes and the gap adds up fast. Always ask: what is the shortest retention I can set, and what is the billing minimum?
Early deletion charges
Some platforms let you shorten a retention period, but charge a fee for the privilege. Others simply will not allow it. Read the terms carefully, because “you can adjust retention” and “you can adjust retention without penalty” are very different promises.
Request and API costs
Locking, checking, and auditing objects generates API calls. At scale, millions of small requests can cost more than the storage itself. This is especially painful for workloads with many tiny files, such as log archives or email backups.
Cross-region replication of locked copies
The 3-2-1 backup rule recommends multiple copies, and immutability often requires at least one copy to be off-site and locked. That second locked copy doubles your storage bill and adds transfer fees.
Egress during recovery
Restoring from immutable storage is a read operation. Some providers charge egress fees when data leaves their network, which means your worst day (a full restore) is also your most expensive day.
Support and compliance reporting
Auditors increasingly want proof that backups were immutable and untampered. Vendors charge for compliance reports, audit logs, and extended log retention. These are small line items individually but add up across a large estate.
How Cloud Providers Structure Immutability Charges
The three hyperscalers all offer object lock, and their pricing pages are worth reading line by line because the structures differ.
Amazon S3 Object Lock uses a retention mode (governance or compliance) plus a retention period. In compliance mode, nobody, including the root account, can delete the object before the date. Billing follows standard S3 storage classes, so the cost depends heavily on which tier you choose. A locked object in a cold tier is far cheaper than one in a hot tier, but retrieval takes longer.
Azure Immutable Blob Storage offers time-based retention and legal hold policies at the container level. Pricing follows blob storage tiers, with additional charges for operations and for any replication you configure.
Google Cloud Object Retention Lock applies a retention policy to a bucket, and once locked, the policy cannot be removed or shortened. You pay standard Cloud Storage rates plus operation charges.
The pattern is consistent: the lock itself is usually free, but the locked data is billed at full storage rates for the entire retention period, and every operation around it has a price. For a broader look at how cloud vendors structure these layered service charges, the breakdown of Apple private cloud compute and Google cloud in 2026 shows how even privacy-focused cloud offerings price their compute and storage components separately.
A Practical Way to Estimate Your Immutability Bill
You can build a rough estimate in five steps without a vendor call.
- Calculate locked capacity. Take your total backup size and add the growth rate over your longest retention period. If you back up 10 TB and grow 2 TB per month with a 12-month retention, your locked footprint approaches 34 TB, not 10 TB.
- Apply the billing minimum. If the provider’s minimum retention is longer than your policy, use the longer figure.
- Add replication. Double the capacity if you keep a second locked copy off-site.
- Estimate request volume. Count objects, not gigabytes. A million small files generate a million lock operations.
- Add restore egress. Model one full restore per year at your provider’s egress rate.
That five-line model usually lands within 20 to 30 percent of the real quote, which is enough to sanity-check a proposal before signing.
Mistakes That Cost Real Money
A few errors show up again and again when teams adopt immutable backups.
Locking everything at the longest retention. It feels safest, but locking years of data you will never need is the single biggest cost driver. Tier your retention: 30 days for daily backups, 90 days for weekly, and a year or more only for monthly or compliance copies.
Forgetting that immutability is not a backup strategy on its own. A locked copy of corrupted data is still corrupted. You need versioning and validation alongside the lock.
Ignoring object size. Providers that charge per object punish small-file workloads. Consolidating small files into larger archives before locking them can cut request costs dramatically.
Skipping the restore test. Immutability protects data from deletion, not from being unrecoverable. Test a restore at least quarterly, and budget for the egress.
Assuming all “immutable” claims are equal. An air-gapped appliance and a cloud object lock both use the word, but they behave differently under attack and are priced on completely different models. Ask exactly which mechanism is being sold.
Not planning for the exit. If you leave a provider, locked data may need to sit until retention expires. Factor in a migration window and any early-termination charges.
How to Compare Quotes Fairly
When two vendors quote different numbers for “the same” immutable backup, normalize the comparison before deciding. Ask each vendor for:
- The exact retention minimum and whether it can be shortened
- The per-GB-month rate for locked data at your expected volume
- Per-object and per-request charges
- Replication and egress rates
- The cost of compliance reporting and audit logs
- Early termination terms
Then run the same five-step estimate against each quote. The vendor with the lowest headline rate is frequently not the cheapest once retention floors and request charges are included. (NIST Cybersecurity Framework)
It also helps to think in terms of cost per protected terabyte per year rather than cost per gigabyte per month. That single number captures retention, replication, and operations in one figure and makes quotes directly comparable.
Where Immutability Fits in a Wider Backup Budget
Immutability is one line in a larger backup budget that also covers primary storage, local copies, and disaster recovery. If you are building that budget from scratch, it helps to see how other categories are priced. For example, the way best photo backup solutions bundle storage tiers with retention limits mirrors the same trade-offs you see in enterprise immutability plans: cheap unlimited tiers usually come with retention or access restrictions.
The same principle applies across consumer and enterprise products. A Leonardo ai pricing plans and features explained breakdown shows how subscription tiers gate features behind capacity limits, and lease pricing for vehicles works the same way, as you can see in BMW M3 lease deals compared by monthly pricing. In every case, the headline number hides the terms that determine what you actually pay.
Conclusion
Backup immutability pricing is not complicated once you see the structure. You are paying for three things: storage held for a fixed period, a guarantee that nobody can delete it early, and the operations that maintain and replicate that guarantee. The lock is rarely the expensive part. The retention commitment is.
The practical takeaway is to tier your retention, count your objects as carefully as your gigabytes, model replication and egress before signing, and always compare quotes on cost per protected terabyte per year. Do that, and immutable backups become a predictable line item instead of a surprise.
Frequently Asked Questions
Is immutable backup more expensive than regular backup?
Yes, usually. Immutable copies cost more because you commit to storing data for a fixed period and cannot delete it early. Expect two to five times the per-gigabyte cost of standard backup storage, depending on retention length and replication.
What is a retention lock minimum, and why does it matter?
A retention lock minimum is the shortest period a provider will bill you for, even if you set a shorter policy. If the minimum is 90 days and your policy is 30, you still pay for 90. It is one of the most common sources of budget overruns.
Do cloud providers charge extra for object lock itself?
Mostly no. The lock feature is typically free, but the locked data is billed at full storage rates for the entire retention period, and every lock, check, and replication operation may carry a request charge.
Can I change my retention period after data is locked?
It depends on the mode. Governance mode usually allows authorized users to shorten retention, sometimes with a fee. Compliance mode typically prevents anyone, including administrators, from deleting or shortening retention before the date.
How do I estimate my immutable backup cost before getting a quote?
Multiply your backup size by your retention period in months, add your growth rate, apply the provider’s billing minimum, then add replication and egress estimates. This five-step model usually lands within 20 to 30 percent of the real quote.
Is an air-gapped appliance cheaper than cloud immutability?
It depends on volume and term. Appliances have high upfront hardware costs but predictable subscription fees and no egress charges. Cloud immutability has no capital cost but scales with data volume. At large, stable volumes, appliances often win; at small or fast-changing volumes, cloud usually does.
