David Davis

On February 23, 2026, Pure Storage stopped being Pure Storage. The company filed a certificate of amendment in Delaware, renamed itself Everpure, Inc., and by March 5 its NYSE listing carried the new name — same PSTG ticker, same FlashArray and FlashBlade product lines, same Evergreen contracts. The same week, it reported its first billion-dollar quarter (roughly $1.06 billion in revenue, up about 20% year over year) and announced an intent to acquire data-intelligence vendor 1touch.

Most rebrands are noise. This one is a strategy document wearing a logo. Below is the verified timeline, what dropping the word “Storage” actually signals about where the array market is headed, and the three things buyers should be watching — none of which is the logo.

What changed

The mechanics were quick and deliberately boring. Under Delaware law, a corporate name change requires no stockholder vote, so the amendment was filed on February 20 and the new name became effective the following Monday. Here is the timeline as it actually happened.

What did not change matters just as much. The ticker is still PSTG. FlashArray, FlashBlade, Portworx, and the Evergreen subscription programs keep their names as of mid-2026. The company has been explicit that customer contracts, certifications, support entitlements, and commercial terms carry over untouched. Your counterparty has a new legal name; your obligations and theirs are identical.

Why it matters

Dropping “Storage” from the nameplate is the entire array market compressed into one word. Capacity has been commoditizing for years — QLC flash economics, hyperscaler design wins, and object storage pricing have squeezed the margin out of selling terabytes. The money is moving up the stack, into the software that catalogs, classifies, protects, and feeds data to AI pipelines. Every major vendor has noticed: NetApp now positions itself as an “intelligent data infrastructure” company, Dell and HPE lead with AI data platform messaging, and VAST Data barely mentions arrays at all. Everpure is simply the first of the established array vendors to change its legal name to match the pitch.

The audience shift is the real story. Storage gets bought by infrastructure directors. Data management gets budgeted by CIOs and, increasingly, chief data and AI officers. A vendor named “Storage” struggles to get that second meeting; a vendor named for durable data has a shot. That is a sales-motion decision, and it will pull the roadmap along behind it.

Context matters too: this is a rebrand from strength, not distress. Companies that rename themselves after a breach or a failed pivot are running from something. A rename announced alongside a record quarter and a double-digit growth rate is running toward something — a bigger total addressable market and a bigger line item in your budget. Expect the renewal conversations to reflect that confidence.

The 1touch acquisition is the tell

If you want to know whether a rebrand is cosmetic, look at where the M&A dollars go the same week. 1touch is a data-intelligence company — discovery and classification of sensitive data across the enterprise, the layer that answers “what data do we actually have, where does it live, and who should touch it.” Terms were not disclosed; management has guided that the deal closes in the second quarter of fiscal 2027 and dilutes operating profit by roughly 1.5% in FY27 before turning accretive within about 24 months.

That is precisely the capability a storage vendor needs to make “data management” more than a slogan. AI projects stall on data readiness far more often than on GPU supply — you cannot govern, stage, or feed what you cannot find and classify. Classification metadata also compounds with security: knowing which volumes hold regulated data is what turns anomaly alerts into prioritized response, a theme we covered in our brief on storage-native ransomware detection.

The honest caution: array vendors have a mixed record of keeping acquired software teams productive. The integration to watch is whether 1touch’s classification engine lands inside the Pure1 and Fusion control plane within a year of closing, or lingers as a separately licensed product with its own console. The first outcome validates the rebrand. The second means you bought a name change.

What happens to Evergreen and product names

As of mid-2026, nothing. FlashArray and FlashBlade keep their names, Evergreen//One and Evergreen//Forever subscriptions renew on existing terms, and certifications remain valid. But corporate rebrands are almost always phase one — portfolio renames typically follow within 12 to 24 months, and packaging changes follow the renames. Three specific things to watch:

• Evergreen renewal terms. Consumption-model SLAs and effective per-tebibyte rates are where a confident vendor tests pricing power. Benchmark every renewal against NetApp Keystone and Dell APEX quotes — our Pure Storage vs. NetApp comparison covers the baseline you should be negotiating from.
• Roadmap emphasis. If your next briefing spends more time on data cataloging, governance, and AI pipeline services than on array software, the R&D budget has moved. That is not bad — but it tells you where the innovation you are paying for will land.
• Bundling. Watch whether 1touch-derived data-intelligence features ship inside existing subscriptions or become a new premium tier. The answer sets the tone for the next three years of renewals.

One thing the name change does not alter: the hardware economics. If you were evaluating all-flash as a backup or restore-speed play last quarter, the math is the same this quarter — see our breakdown of all-flash backup target economics before assuming the rebrand changes any purchasing calculus.

What to do about it

Nothing here is urgent. But five items belong on your list at the next natural touchpoint:

• Update vendor-master records, procurement systems, and MSA references to Everpure, Inc. at the next contract event. The legal entity changed names; no novation is required.
• At your next QBR, ask one direct question: what share of R&D goes to array software versus data services next fiscal year? The answer measures how real the rebrand is.
• If the 1touch deal closes, ask how classification metadata exports to your existing security and governance stack. Insist on open APIs before it becomes a lock-in surface.
• Treat Evergreen renewals as competitive events. A vendor rebranding from strength has pricing confidence; counter it with live alternatives on the table.
• Ignore the logo. Track the roadmap, the packaging, and the renewal quote. Those three tell the truth.

The takeaway a VP can repeat: Everpure is the array market admitting that capacity is a commodity and data management is the product. Buy accordingly.

Frequently asked questions

Why did Pure Storage change its name to Everpure?

Management says the new name reflects a strategic shift from selling storage to providing AI-era enterprise data management. Practically, it repositions the company to sell to CIOs and data leaders rather than only to infrastructure teams, and it landed alongside the 1touch data-intelligence acquisition and the company’s first billion-dollar quarter.

Did the PSTG ticker symbol change?

No. Everpure began trading under its new corporate name on the NYSE on March 5, 2026, but kept the existing PSTG ticker. No shareholder action was required for the name change under Delaware law.

Does the rebrand affect existing Pure Storage contracts, support, or certifications?

No. Contracts, Evergreen subscriptions, support entitlements, certifications, and commercial terms carry over unchanged. Product names including FlashArray and FlashBlade remain in place as of mid-2026, though buyers should expect portfolio naming to evolve over the next year or two.

What is 1touch and why is Everpure acquiring it?

1touch is a data-intelligence vendor focused on discovering and classifying sensitive data across enterprise environments. The acquisition gives Everpure the metadata layer needed to back its data-management positioning — knowing what data exists, where it lives, and how it should be governed for AI and compliance use cases. The deal is expected to close in Q2 of fiscal 2027.

Is Everpure related to the water filtration brand of the same name?

No. The enterprise data company Everpure, Inc. (formerly Pure Storage) is unrelated to the Everpure water filtration product line owned by Pentair. They operate in entirely different industries.

Enterprise Techie publishes vendor-honest analysis like this daily — get the brief by email, free.

Every VCF 9 core you buy from Broadcom now carries 1 TiB of vSAN capacity entitlement, pooled across your clusters. That single licensing detail has quietly rewritten enterprise storage strategy: vSAN is no longer a product you evaluate — it’s a sunk entitlement you either consume or waste. I’ve sat in three renewal meetings this quarter where the storage decision and the hypervisor decision collapsed into one line item, and teams discovered they were arguing about both at once without realizing it.

This brief maps the realistic vSAN alternatives in 2026: staying HCI on vSAN or Nutanix, or decoupling storage onto external arrays from Pure Storage, NetApp, or Dell — arrays that, as of this year, finally speak more than one hypervisor’s language. The core argument: pick storage for data gravity and exit optionality, not for whichever hypervisor you happen to run this year.

What changed

Broadcom’s VCF 9 bundling made vSAN capacity a per-core entitlement rather than a separate purchase. Each VCF core includes 1 TiB of vSAN entitlement; vSphere Foundation (VVF) includes 0.25 TiB per core. The entitlement pools across clusters, and you buy add-on TiBs only above the included amount. Note that entitlement TiBs are raw licensing capacity — usable capacity after FTT and RAID overhead lands meaningfully lower, so budget accordingly.

Meanwhile, the external-storage vendors stopped being VMware-only citizens. Nutanix shipped its Pure Storage FlashArray integration to general availability in December 2025 and extended it to more FlashArray models at .NEXT 2026, announced an NFS-based alliance with NetApp for AFF and select FAS systems, and already supported Dell PowerFlex for compute-only nodes. NetApp and Pure have both pushed integrations toward Proxmox and OpenShift as well. External arrays are now multi-hypervisor assets in practice, not just on the roadmap slide. And the clock is real: vSphere 8’s 2027 end of support means most shops must land somewhere new within roughly 15 months.

Why it matters

Storage is where the switching costs actually live. Compute is stateless — you can vMotion, rebuild, or re-image your way off a hypervisor in a quarter. Petabytes are not. If your data sits inside vSAN datastores, your data follows your VMware licensing decision whether you like it or not. If it sits on an external array with multi-hypervisor support, the hypervisor becomes a two-year decision instead of a ten-year one.

The entitlement math cuts both ways. If you’re staying on VCF at your current core count, the included vSAN TiBs make external arrays look expensive — you’d be paying twice for capacity you already own. If you’re shrinking your VMware footprint, every TiB stranded in vSAN is a hostage in the renewal negotiation. The takeaway a VP can repeat: vSAN’s price is now a function of your Broadcom relationship, not of storage economics.

Path 1: Stay HCI — vSAN under VCF, or Nutanix

vSAN ESA remains a genuinely good storage product — strong NVMe performance, mature operations, and effectively “free” up to your pooled entitlement if you’re committed to VCF anyway. For a shop that has made peace with Broadcom pricing and runs a stable, VMware-standardized estate, consuming the entitlement is the rational move. The risk isn’t technical; it’s that your storage exit cost compounds every year you deepen the dependency.

Nutanix is the other HCI answer, and 2026’s twist is that it’s no longer HCI-only. AHV plus AOS gives you a vSAN-like operational model with a different licensing counterparty — and Nutanix now lets you attach external storage rather than forcing everything into its own distributed fabric. We analyzed that shift in depth in our brief on Nutanix external storage as a VMware exit ramp. Nutanix fits shops that want the HCI operating model without the Broadcom invoice; it does not fit shops with heavy vSphere-specific tooling they aren’t ready to rewrite, and its migration still consumes real project quarters.

Path 2: Decouple onto external arrays

The decoupling case rests on one 2026 fact: the major array vendors now integrate with the hypervisors people are actually migrating to.

Pure Storage (now Everpure) FlashArray is the most aggressive mover. The Nutanix integration — GA since December 2025 — maps every AHV virtual disk to its own array volume, so per-VM snapshots, QoS, and replication work at array speed, and .NEXT 2026 extended support beyond the //X and //XL models. Evergreen subscriptions mean the array outlives multiple hypervisor generations. Strong fit: shops that want one storage platform under vSphere today and AHV or OpenShift tomorrow. Weak spot: file services lag NetApp’s, and FlashArray pricing sits at the premium end — list pricing varies, but you’re paying for the operational model.

NetApp AFF and ASA counter with breadth. ONTAP speaks NFS, iSCSI, NVMe-oF, and SMB from one system, the new Nutanix alliance runs over NFS to AFF A-series and select FAS, and NetApp’s Proxmox and OpenShift tooling is credible. If your estate mixes VM storage with large file workloads, NetApp consolidates what Pure would split across products. The cost is complexity: ONTAP’s flexibility comes with a learning curve that flat-out annoys teams accustomed to FlashArray’s minimalism. Our Pure vs NetApp comparison breaks down where each wins.

Dell PowerFlex is the scale-out option — software-defined block storage that disaggregates compute from capacity and was the first external storage Nutanix certified for compute-only nodes. It shines at large scale (hundreds of nodes, mixed hypervisors, database-heavy estates) and inside Dell-standardized shops. Below roughly a half-petabyte, its operational overhead outweighs the benefit, and Dell’s broader portfolio (PowerStore, PowerMax) can make the sizing conversation feel like a menu with no prices.

Side-by-side: the three storage paths

The honest downsides of each path

Staying on vSAN means accepting that your storage exit cost grows with every TiB you land there, and that Broadcom — not you — controls the future price of that capacity. It also means your DR and data-protection tooling stays vSphere-shaped.

Decoupling isn’t free either. If you hold a VCF subscription, external arrays mean paying for storage twice until the next renewal. Array-based estates need SAN or dedicated Ethernet fabric skills that many HCI-era teams let atrophy. And multi-hypervisor integrations are young: the Nutanix–NetApp path is NFS-only today, and the FlashArray–AHV integration, while GA, has fewer production miles than a decade of vSphere plugins. Nutanix as a middle path carries its own migration tax. Nobody exits this decision clean; you’re choosing which costs you can live with.

What to do about it

Three rules of thumb I’d defend in any architecture review:

• If you’re renewing VCF at flat or growing core counts: consume the vSAN entitlement, but keep new data-heavy workloads (databases, file shares, analytics) off vSAN so the hostage doesn’t grow.
• If you’re shrinking VMware by 30% or more: move storage first. Land data on an external array with AHV and Proxmox support before you migrate compute — data gravity is the exit blocker, not the hypervisor.
• If you’re undecided: refuse any storage purchase that locks to a single hypervisor. As of mid-2026, multi-hypervisor support costs little to demand and preserves the negotiating leverage you’ll want at the next Broadcom renewal.

The one-liner for the steering committee: storage decisions now outlive hypervisor decisions, so make the storage call for the estate you’ll run in 2030, not the one you licensed in 2024.

Frequently asked questions

Is vSAN included with VCF 9?

Yes. VCF 9 includes 1 TiB of vSAN capacity entitlement per licensed core, pooled across clusters and VCF Operations instances. VVF includes 0.25 TiB per core. Capacity beyond the entitlement is a paid add-on, and entitlement TiBs are raw — usable capacity depends on FTT and RAID choices.

What is the best alternative to vSAN in 2026?

It depends on your exit posture. Committed VCF shops should usually consume the entitlement. Shops leaving VMware lean toward Nutanix AOS for a like-for-like HCI model, or external arrays — Pure FlashArray, NetApp AFF/ASA, Dell PowerFlex — when data gravity and multi-hypervisor flexibility matter more than operational simplicity.

Can Nutanix use external storage instead of its own HCI storage?

Yes, as of late 2025. Nutanix supports Pure Storage FlashArray (GA December 2025, expanded at .NEXT 2026), NetApp AFF and select FAS over NFS, and Dell PowerFlex for compute-only nodes. That breaks the old rule that choosing Nutanix meant choosing Nutanix storage.

Is HCI still cheaper than a SAN?

Not reliably, and the question has changed. With vSAN bundled into VCF cores, its cost is a licensing artifact rather than a market price. External arrays cost more upfront but decouple storage refresh cycles from hypervisor licensing — which is where the money actually moves over a five-to-seven-year horizon.

Enterprise Techie publishes vendor-honest analysis like this daily — get the brief by email, free.

Every backup storage quote you will see this year leads with the same number — dollars per terabyte per month at rest. It is the wrong number. The bill that ends careers arrives after the ransomware event, when a 500TB full restore from S3 Standard runs roughly $45,000 in egress fees alone, before you have recovered a single VM. Meanwhile the same restore from Wasabi or a flat-rate vault costs nothing beyond what you were already paying.

This brief lays out verified mid-2026 list pricing for the four options enterprise buyers actually shortlist — Backblaze B2, Wasabi, AWS S3, and Veeam Data Cloud Vault — then does the math that matters: what the disaster costs, not what the idle copy costs.

The 2026 price table

List pricing as of mid-2026, US regions, pay-as-you-go unless noted. The last column is the one your CFO will remember.

What changed

The commodity tier got a repricing this spring. Backblaze moved B2 pay-as-you-go from $6 to $6.95/TB/month effective May 2026, dropping API transaction fees in the same change. Wasabi followed on July 1, raising pay-as-you-go from $6.99 to $7.99/TB/month across all regions, citing hardware, energy, and data-center costs. The era of sub-$7 object storage quietly ended this quarter, and nobody sent a press release worth reading.

Veeam, meanwhile, split Data Cloud Vault into Foundation and Advanced editions, starting around $14/TB/month with region choice and unlimited restores reserved for the higher tier. AWS list pricing for S3 Standard is essentially unchanged — roughly $23/TB/month for the first tier — which means the gap between hyperscaler and commodity object storage is still about 3x at rest and far wider once data moves.

The takeaway for a budget meeting: commodity backup storage went up 10–14 percent this year, but it is still the cheapest tier by a wide margin. If your renewal quote went up more than 15 percent, that is your vendor’s margin expanding, not the market.

Model the disaster, not the invoice

At-rest price is a comfort metric. The number that belongs in your business case is total cost across one full-scale restore, because that is the event the storage exists for. Run the scenario: 500TB of backup data, complete restore over the internet after a site loss or ransomware detonation.

• S3 Standard: 500,000GB at roughly $0.09/GB is about $45,000 in egress, plus per-request charges on millions of GET calls. An unbudgeted invoice, arriving in the worst week of your career.
• Wasabi: $0, provided your monthly egress stays within the 1:1 fair-use ratio — and a one-time full restore of what you store does.
• Backblaze B2: $0 in practice; the free allowance of 3x average monthly storage covers even a complete restore with room to spare.
• Veeam Vault: $0 beyond the flat rate you already committed to. That is the entire pitch.

The restore penalty compounds when recovery time matters, which is the same reason DR economics have shifted toward flat-rate models — we broke down the full recovery-cost picture in our DRaaS pricing analysis for 2026. Verdict: any backup storage decision made on at-rest price alone is a decision to self-insure against a five-figure egress bill.

Wasabi and Backblaze: same aisle, different fine print

Both are S3-compatible, both support object lock for immutability, and both undercut hyperscalers by roughly two-thirds at rest. The difference is retention math. Wasabi bills every object for a minimum of 90 days. For long-retention monthly and yearly backup points, that clause is irrelevant and Wasabi’s zero-egress model is clean and predictable — which is why it has become the default for MSPs. For short-lived data, it bites hard: a daily backup chain deleted after 30 days is still billed for 90, tripling the effective rate to roughly $24/TB/month — hyperscaler money for commodity storage.

Backblaze B2 has no minimum retention, which makes it the stronger fit for aggressive grandfather-father-son schemes with fast-expiring increments. Its weaknesses are the flip side of its price: fewer regions than Wasabi or the hyperscalers, and a smaller enterprise support organization — acceptable for a third copy, worth scrutiny if B2 is your only off-site tier. Both vendors’ immutability implementations differ in ways that matter for compliance; our immutable backup storage comparison covers the object-lock specifics.

Rule of thumb: retention under 90 days, Backblaze wins. Retention over 90 days, the two are within a rounding error, so pick on regions and support.

Veeam Vault: paying for predictability

Veeam Data Cloud Vault is Azure-backed object storage sold as a flat per-TB rate — $14 to $24/TB/month depending on edition, as of mid-2026 — with API calls, immutability, and restore egress folded into the price. That is 2–3x the commodity clouds at rest, and Veeam is not embarrassed by the comparison. The product exists for the buyer who has watched an S3 bill spike from API overhead during backup verification jobs and wants a number that never moves.

Where it is strong: zero bill-shock risk, immutable by default, and no finger-pointing between backup vendor and storage vendor when a restore goes sideways. Where it is not: it only makes sense inside a Veeam estate, it is billed annually upfront, and you are paying a meaningful premium over Wasabi or B2 for convenience you may not need if your team already manages object storage competently. For a Veeam shop with a lean ops team, the premium is defensible. For anyone else, it is not on the shortlist.

Where S3 still makes sense

Writing AWS off as the expensive option misses the cases where it is the rational one. If your production workloads run in AWS, restoring within the region avoids internet egress entirely, and the data-gravity argument is real. S3’s lifecycle tiering into Glacier Instant Retrieval and Deep Archive can push at-rest cost below $4/TB/month for compliance archives — cheaper than anything else in this table — as long as you price the retrieval fees and hours-long thaw times into your recovery plan.

The honest downside: complexity is the product. Between storage classes, request charges, retrieval tiers, and egress waivers, an accurate S3 backup TCO takes a spreadsheet and an afternoon. Most of the S3 backup bills we see in the field are 20–40 percent higher than the team estimated, and API charges from verification and synthetic-full operations are the usual culprit.

What to do about it

• Price the restore, not the rest. Add a “full restore cost” line to every storage comparison. If a vendor cannot give you that number in one email, that is your answer.
• Compute effective $/TB. Multiply list price by (minimum retention ÷ actual retention, floor of 1). Wasabi at 30-day retention is a $24 product, not an $8 one.
• Above $15/TB/month for commodity object storage without included egress, renegotiate or move. The 2026 market does not support that price.
• Test a 10 percent restore annually and capture the real invoice. Extrapolate it in your DR runbook so the $45,000 surprise is a budgeted line, not a career event.
• Benchmark cloud against on-prem before renewing. At sustained 500TB+ with fast-restore requirements, an on-site target can beat cloud economics — see our analysis of all-flash backup target economics before you sign a three-year cloud commit.

Frequently asked questions

How much does backup storage cost per TB in 2026?

As of mid-2026, commodity cloud object storage lists at $6.95/TB/month (Backblaze B2) to $7.99/TB/month (Wasabi). Flat-rate managed vaults such as Veeam Data Cloud Vault run $14–24/TB/month with egress included, and hyperscaler storage like AWS S3 Standard is roughly $23/TB/month before egress and request charges.

Is Wasabi cheaper than Amazon S3 for backups?

At rest, yes — roughly a third of S3 Standard’s list price, with no egress fees. The exception is short-retention data: Wasabi’s 90-day minimum storage duration means backups deleted within 30 days are billed at an effective rate near S3’s. For retention beyond 90 days, Wasabi is decisively cheaper, especially once restore egress is counted.

What are egress fees and why do they matter for backup?

Egress fees are per-gigabyte charges for moving data out of a cloud. For backup they matter because the entire dataset may leave at once during a disaster recovery — a 500TB restore from AWS S3 costs about $45,000 in egress at ~$0.09/GB, while zero-egress providers charge nothing for the same event.

Is Veeam Data Cloud Vault worth the premium over Wasabi or Backblaze?

For Veeam customers who value a single predictable invoice — with API calls, immutability, and restores included — the $14–24/TB/month flat rate can be worth 2–3x commodity pricing. Teams comfortable managing S3-compatible storage directly will usually save meaningful money with Wasabi or Backblaze B2 instead.

Enterprise Techie publishes vendor-honest analysis like this daily — get the brief by email, free.

Run the math on a petabyte-scale ransomware recovery and the backup repository — not the backup software, not the network — is almost always the choke point. A dedupe disk appliance that happily ingests 40TB an hour can crawl at a fraction of that when it has to rehydrate and stream data back out, and at petabyte scale the difference is measured in days of downtime. That is the decision moment this brief is about: QLC flash has pulled all-flash backup targets down to roughly disk-level acquisition cost, and that changes who should still be buying spinning disk for their repository tier.

Below: what changed in the QLC economics, why restore throughput is now the ransomware SLA that matters, honest numbers on where dedupe disk still wins, and vendor-by-vendor reads on Pure Storage, NetApp, and Veeam.

What changed

For a decade the objection to flash as a backup target was one word: price. QLC NAND ended that argument at the acquisition line. Pure Storage’s FlashBlade//E — its capacity-optimized, QLC-based file and object platform — is positioned explicitly as an unstructured data repository priced comparably to disk-based systems, with Pure claiming operating costs around 60% lower than disk once power, space, and admin time are counted. NetApp answered from the other direction: its AFF C-Series (C250, C400, C800) puts cost-optimized QLC flash under the full ONTAP stack and aims it squarely at secondary storage, backup targets, and capacity workloads, with NetApp citing petabyte-range capacities per cluster.

Meanwhile the density curve keeps working in flash’s favor — Pure has publicly targeted 300TB DirectFlash modules on its 2026 roadmap, densities hard-drive vendors cannot answer. The verdict: as of mid-2026, “flash costs too much for backup” is no longer automatically true. It is a workload-by-workload calculation, and that is new.

Why it matters: restore throughput is the new ransomware SLA

Backup windows stopped being the constraint years ago — incremental-forever chains and changed-block tracking saw to that. The constraint that boards now ask about is the clean-room recovery: how fast can you restore everything, from a known-good copy, after an encryption event. That is a full-fidelity, sequential-read-at-scale problem, and it is exactly where dedupe disk architectures are weakest, because every restored block has to be rehydrated from deduplicated segments scattered across spindles.

Flash targets invert that. Pure has claimed restore rates up to 270TB per hour on large FlashBlade configurations — vendor-published and scale-dependent, so treat it as a ceiling, not a promise. But even discounting heavily, the gap against a rehydrating disk appliance is not 20%; it is often an order of magnitude on mass restores. If your recovery SLA math prices a day of downtime in the millions — and for most enterprises above a few thousand employees it does — the repository’s read path is the SLA. Our 2026 RTO/RPO benchmark data makes the same point from the other end: the enterprises missing recovery targets are overwhelmingly bottlenecked on restore reads, not on backup software.

The economics, honestly

Here is the honest counterweight: purpose-built dedupe appliances still win raw $/TB at rest, and it is not close when dedupe ratios run high. Backup data dedupes exceptionally well, and an appliance built around inline dedupe can land effective cost per terabyte well below any all-flash system. If your repository exists to satisfy retention policy and restores are rare, small, and non-urgent, dedupe disk remains the rational buy.

The takeaway a VP can repeat: dedupe disk optimizes the cost of keeping data; flash optimizes the cost of getting it back. Price your downtime and the spreadsheet picks the tier for you. For the fuller cost model, see our backup storage cost-per-TB analysis for 2026.

Vendor read: Pure Storage

Pure made the aggressive bet here. FlashBlade//E is a purpose-built play for exactly this tier — scale-out file and object, QLC DirectFlash modules, and a pricing posture designed to kill the disk comparison at the quote stage. Strengths: genuine restore performance at scale, the Evergreen subscription model that takes forklift refreshes off the table, and operational simplicity that shows up in real admin-hours savings. Where it is weaker: Pure’s economics depend on its density roadmap holding, the entry configuration is sized for petabyte-class estates rather than mid-market ones, and buyers should pressure-test the claimed TCO deltas against their own power and facilities costs rather than accepting vendor math. Pure fits the enterprise that has decided recovery speed is a board-level requirement and wants a dedicated repository platform to deliver it.

Vendor read: NetApp

NetApp’s C-Series is the incumbent-friendly path. You get QLC economics under ONTAP, which means the tooling, SnapMirror replication, and SnapLock immutability your team already runs — a real advantage when the backup target must slot into an existing compliance and replication fabric. Strengths: one operating environment across primary and secondary tiers, mature immutability, and strong effective-capacity claims once ONTAP’s dedupe and compression are applied. Where it is weaker: ONTAP is a primary-storage OS carried into a capacity tier, so you pay some complexity tax a purpose-built repository avoids, and C-Series is rarely the cheapest option in a bake-off at rest. NetApp fits the ONTAP shop that wants flash-speed restores without introducing a new vendor or a new operational model. Our Pure Storage vs. NetApp head-to-head goes deeper on where each platform earns its premium.

Where Veeam fits

Veeam does not sell the target, which is precisely why its read matters — the software layer is where flash repositories either pay off or get wasted. Veeam Data Platform’s Scale-out Backup Repository lets you tier a flash performance extent in front of cheaper capacity, so you do not have to buy flash for every retention point — only for the restore-critical window, typically the most recent 14 to 30 days. Its instant-recovery features are the other half of the argument: live-mounting dozens of VMs directly from the repository is a flash-class workload, and it is where disk targets visibly fall over. Veeam’s ONTAP integration also gives NetApp shops snapshot-orchestrated workflows the generic targets do not get. The caution: Veeam’s hardened Linux repository immutability and its fast-clone efficiencies work on any target, so do not let a storage vendor imply flash is required for safe backups. Flash buys speed, not safety — immutability is a software and configuration decision.

What to do about it

• Do the throughput math first. Divide the terabytes you must restore in a clean-room scenario by the hours your business case allows. If the answer exceeds roughly 10TB/hour sustained, test your current appliance’s real restore rate — most disk-era buyers have never measured it.
• Tier, don’t replace. Put flash under the restore-critical window (14–30 days) and keep dedupe disk or object storage for deep retention. Veeam’s SOBR and equivalent constructs make this a configuration exercise, not a migration.
• Price downtime into the TCO. If one avoided day of outage exceeds the 5-year cost delta between flash and disk tiers, the flash target is the conservative buy, not the extravagant one.
• Make vendors prove restore rates on your data. Ingest benchmarks are marketing; demand a proof-of-concept restore of your actual workload mix before signing.

Frequently asked questions

Is all-flash storage good for backups?

Yes, with a caveat. All-flash targets excel when restore speed matters — ransomware recovery, instant VM recovery, aggressive RTOs. For long-retention data that is rarely restored, dedupe disk or object storage still delivers lower cost per terabyte at rest. Most enterprises should tier: flash for the recent restore window, cheaper media behind it.

Is QLC flash reliable enough for backup workloads?

For this workload profile, yes. QLC’s lower write endurance is a poor match for write-intensive primary workloads, but backup targets are sequential-write, read-heavy-on-demand — close to the ideal QLC pattern. Both Pure and NetApp warranty their QLC platforms for these use cases, and media management in the array masks endurance concerns in practice.

What restore speed do I need for ransomware recovery?

Work backward from your tolerable outage. A 500TB critical estate with a 24-hour recovery target needs roughly 21TB/hour sustained — beyond what most dedupe appliances deliver on rehydrated restores. At petabyte scale with a one-to-two-day target, you are in flash-target territory almost by definition.

Does an all-flash backup target replace immutability?

No. Immutability comes from software and configuration — Veeam hardened repositories, NetApp SnapLock, object lock on S3-compatible targets — not from the media type. Flash changes how fast you recover; immutability determines whether you have anything clean to recover from. You need both, and they are separate line items in the design.

Enterprise Techie publishes vendor-honest analysis like this daily — get the brief by email, free.

Veeam closed the loop in January. After Object First posted 183% bookings growth in 2025 — and another 118% year-over-year in Q1 2026 — Veeam confirmed it was acquiring the appliance company its own co-founders built. The immutable backup target appliance is no longer a third-party accessory; it is first-party Veeam strategy now. That changes the buying calculus for anyone shopping for the immutable “+1” copy in a 3-2-1-1-0 design.

This brief compares the three realistic paths as of mid-2026: Object First’s Ootbi appliances, Scality’s ARTESCA+ Veeam HA integrated appliance, and cloud object lock through Wasabi or Veeam Vault. Who each fits, what each costs you in operational overhead, and where the restore-speed economics break.

The verdict

If your estate is Veeam-only and you want the fastest path to a hardened on-prem target, buy Ootbi. If you want backup software and immutable storage collapsed into one highly available appliance — and a vendor willing to write a check if immutability fails — Scality’s ARTESCA+ Veeam HA is the more ambitious engineering. If your recovery-time tolerance is measured in days rather than hours, cloud object lock is the cheapest ticket in the room. Most mid-size enterprises should land on one on-prem immutable tier plus one cloud copy. The argument is over which appliance, not whether.

What changed

Two dates moved this market in 2026. On January 14, Veeam confirmed it was acquiring Object First, the company Ratmir Timashev and Andrei Baronov — Veeam’s original co-founders — started in 2022 to build a Veeam-only immutable target. The deal resolved an awkward overlap: Veeam had begun shipping its own software appliance while its founders’ side venture sold the hardware target everyone actually wanted. Ootbi is now the first-party answer when a Veeam customer asks “what do I point my backups at?”

Scality answered on April 29 with ARTESCA+ Veeam HA — the first complete high-availability build around Veeam Data Platform v13’s appliance capabilities. It runs the backup software and the immutable object store on one platform with failover across three layers, scales from 50 TB to 10 PB, and carries a $100,000 cyber guarantee paid to any customer whose immutably stored data is compromised by an external attack — no premium support contract required. That guarantee is a first, and it reframes immutability from a checkbox into a warranted claim.

Object First Ootbi: the default for Veeam-only shops

Ootbi — “out-of-the-box immutability” — is deliberately narrow. It presents S3 with Object Lock enabled by default, runs a hardened Linux with no root access, and talks to exactly one backup product: Veeam. That narrowness is the feature. There is no storage tuning, no security hardening project, no separate object-storage skillset to hire for. Appliances span roughly 20 TB to 432 TB per node, cluster into the low-petabyte range with multi-GB/s ingest on larger configurations, and the Ootbi Mini extends the same model to edge and ROBO sites where nobody on staff owns storage.

The growth numbers explain the acquisition: 183% bookings growth in 2025 followed by 118% year-over-year in Q1 2026. Customers voted for simplicity. The open question is what first-party ownership does to pricing leverage — when the appliance and the backup software come from the same vendor, the discount conversation gets harder. Negotiate them together, and get roadmap commitments in writing.

Scality ARTESCA+ Veeam HA: one appliance, two jobs, a guarantee

Scality comes at the problem from the opposite direction. ARTESCA is a general-purpose S3 object store that happens to be excellent as a backup target; the April 2026 appliance collapses Veeam Data Platform v13 and ARTESCA into a single box with automated failover at the application, data, and node layers. If a node dies mid-backup-window, the system keeps running — a claim Ootbi’s standalone appliances do not make. Object Lock runs in compliance mode, meaning no administrator, vendor, or attacker can shorten retention once data is written.

The 50 TB to 10 PB range covers everything from a regional hospital to a multi-datacenter enterprise, and because ARTESCA is a real S3 platform, it can serve other workloads — analytics archives, a second backup product, general object storage — which matters if your estate is not Veeam-monogamous. If you are weighing that broader play, our on-prem S3 object storage guide covers the field. The trade: it is a bigger system with more moving parts than Ootbi, and the HA appliance is still a Veeam-centric product at its core.

Cloud object lock: Wasabi and Veeam Vault

The cloud path is the cheapest per terabyte and the slowest per restore. Wasabi remains the value leader for lock-enabled buckets: flat list pricing that has hovered around $7 per TB per month as of mid-2026, with no egress or API request fees — though watch the minimum storage-duration policies, which can make short-retention tiers cost more than the sticker suggests. Veeam Vault is Veeam’s own managed alternative: pre-configured, immutable, and priced flat per terabyte with egress bundled in, which removes the two classic cloud-bill surprises. Our cost-per-TB benchmark runs the current numbers across both.

The economics break on restore speed, not storage price. Pulling 100 TB across a 10 Gbps link takes roughly a day at theoretical line rate; in practice, plan for two to four. The rule of thumb: if your largest credible single restore exceeds 20–30 TB and your RTO is under 24 hours, cloud object lock cannot be your primary restore tier. It is the offsite copy and the deep archive. It is not the thing you restore production from on a Tuesday morning.

The honest downsides — all three of them

• Ootbi: Veeam-only by design, so a future backup-vendor change strands the hardware. Per-cluster capacity tops out in the low petabytes, and post-acquisition pricing power now sits entirely with Veeam.
• ARTESCA+ Veeam HA: more capable, more complex. You are operating an object-storage platform, not just racking a target, and the integrated appliance is new as of April 2026 — early-adopter risk applies until reference deployments accumulate.
• Cloud object lock: restore bandwidth is the hard ceiling, retention minimums and lock misconfiguration are the quiet costs, and a bucket you configured wrong is not immutable at all. Governance mode, in particular, is theater against an attacker holding admin credentials.

What to do about it

Decision rules a VP can repeat. Veeam-only estate under about 1.5 PB of backup data: Ootbi, negotiated alongside your Veeam renewal. Mid-size enterprise that wants backup software, immutable storage, and high availability in one procurement — or that values a written $100K guarantee when the board asks about ransomware: ARTESCA+ Veeam HA. Heterogeneous estate running more than one backup product: a general-purpose on-prem S3 store beats a captive appliance. Everyone, regardless: one cloud object-lock copy offsite, sized against your realistic restore bandwidth, per the 3-2-1-1-0 rule.

And test the zero. Immutability guarantees your data survives; only a timed, full-scale restore drill proves you can get it back inside your RTO. Run one this quarter, with the WAN numbers, before you sign anything.

Frequently asked questions

What is immutable backup storage?

Storage where backup data cannot be modified or deleted for a defined retention period — by anyone, including administrators. In practice that means S3 Object Lock in compliance mode, a hardened appliance like Ootbi, or both. It is the control that keeps ransomware operators from encrypting your backups before they encrypt production.

Did Veeam buy Object First?

Yes. Veeam confirmed the acquisition in January 2026, bringing the Ootbi appliance line in-house. Object First was founded in 2022 by Veeam co-founders Ratmir Timashev and Andrei Baronov, so the deal formalized a relationship that was always close.

Is S3 Object Lock really immutable?

Only in compliance mode. Governance mode allows privileged users to override retention, which means an attacker with stolen admin credentials can too. If a vendor says “immutable,” ask which mode, who holds the keys, and whether retention can be shortened after write. Compliance mode with a locked-down time source is the bar.

Is Wasabi good enough for enterprise backup?

As the offsite immutable copy, yes — the flat pricing with no egress fees makes restore economics predictable, which most hyperscaler tiers cannot claim. As the primary restore tier for large estates, no; WAN bandwidth caps how fast you can pull data back, and days-long restores fail most enterprise RTOs.

Enterprise Techie publishes vendor-honest analysis like this daily — get the brief by email, free.