Pure FlashArray //C / //E FlashArray Capacity / Entry Maintenance
side by side.

FlashArray //C40

//C40 R1/R2/R3 (entry capacity, from ~250 TB usable)

FlashArray //C60

//C60 R1/R2/R3 (mid-range capacity, ~500 TB–1 PB)

FlashArray //C90

//C90 R3 (high capacity, multiple PB)

FlashArray //E

//E (entry-level, multiple configurations for mid-market and edge)

EOSL status of generations

FlashArray //C and //E have a different workload character than the //X family — capacity over performance, tier-2 over tier-1, backup target over mission-critical DB. Pure Evergreen terms are often hard to justify here because the workload dynamics don't match the subscription model's refresh cycle. Backup targets and archives tend to be used longer than tier-1 platforms — TPM structurally fits better.

For //E in mid-market the pitch is even clearer: mid-market customers typically have neither the budget nor the operational need for Pure Evergreen features like SafeMode subscription or Pure1 predictive analytics. TPM with a clear fixed price and defined SLA is the more economical choice. With OEM original parts, German-speaking support and a single contract for the entire infrastructure.

The full OEM-vs-TPM matrix (spare parts, SLA tiers, language, sub-outsourcing, compliance docs, reporting) is the same for every Pure Storage line — see the Pure Storage battle card.

BAIT/MaRisk documentation package, DORA Art. 28 contract template, ISO 27001 and GDPR-compliant media handling apply identically to every Pure Storage line — details on the Pure Storage battle card.

Same four steps for every Pure Storage line: inventory → fixed-price quote in 48 h → contract (BAIT/MaRisk/DORA hooks) → hand-over with spare-parts provisioning. Details on the Pure Storage battle card.

How does //C differ from //X for maintenance?

//C uses QLC NVMe modules instead of TLC, higher density, different failure patterns. Maintenance is mechanically identical, but we stock QLC-specific modules separately. Slight hardware differences for DRAM cache and controller FRUs — no issue for OEM original parts availability.

Which FlashArray //E configurations do you cover?

All //E variants — entry-level with smaller controller configuration, mid-range capacities. Pure positions //E for DACH mid-market and edge data centers. We know the platform and stock parts for DRAM, NVMe modules and PSUs.

What does TPM cost for a //C60 or //E?

For a //C60 R2 with 24×7×4 (priced higher than //X20 by Pure due to more modules), TechCare is roughly 50–55 % below the Pure price. //E depending on configuration typically 50–60 % below Pure list price. Fixed-price quote within 48 hours of inventory receipt.

Which SLA do you recommend for //C as backup target?

For //C as backup target, 5×9 NBD often suffices — backup jobs tolerate short maintenance windows. For //C as tier-2 storage for active applications we recommend 24×7×4. Mixable SLA levels are no issue, we tier per system.

Do CloudSnap and SafeMode still work on //C?

CloudSnap (to AWS S3) and SafeMode (ransomware protection) are software features in Purity. They continue to work as long as Purity runs — the cloud component requires an active Pure contract or cloud subscription. Hardware maintenance runs separately. For active SafeMode users keep the Pure software subscription.

Can we maintain //C and //X under the same contract?

Yes — that's actually one of our main advantages. A TechCare contract covers //C, //X, //XL, //M, //E and FlashBlade — plus all other vendors in your data center. No need for separate contracts with Pure (tier-1) and a TPM provider (tier-2). Consolidation reduces administrative overhead.