Issue 02 · Week of Aug 24–29, 2026Weekly Storage & memory infrastructure for AI

Areal Density

Weekly signal for the people building and buying AI infrastructure — what moved, why it matters, what's next.

This is the first weekly issue, and it's a different animal on purpose. Issue 01 tried to cover the whole AI storage market in one sitting: every vendor, every roadmap, every failure-rate table. That's not something worth attempting every seven days, so it becomes an occasional Field Report instead. Most weeks will look like this one: what actually happened, why it matters if you're the one keeping GPUs fed, and what to watch next.

01 — The pulse

This week in four numbers

+30% Bandwidth gain from Nvidia's NVHBM memory-controller-in-stack design
~280 NAND layers in Samsung's V9, now ramping at its Xi'an fab
180x Faster disaster-recovery replay claimed by WarehousePG (avg. 16 min restore)
$5B Target raise for YMTC's planned Shanghai IPO
02 — Signal

What moved, and why it matters

Seven things that happened this week, and why I'd pay attention to each one.

DDN lands a sovereign AI deal in Australia DDN · Blocks & Files

DDN's object storage will sit underneath SCX.ai's inference infrastructure for Australian enterprise and government customers. The deal itself isn't the story, DDN wins deals.

Worth noting"Sovereign AI" is turning into its own procurement category, with requirements like data residency and inference locality that have nothing to do with raw throughput. Expect more vendors to start citing sovereign wins as their own line item.
Nvidia moves the memory controller inside the HBM stack Nvidia · StorageNewsletter

NVHBM claims up to 30% more bandwidth by pulling what used to be separate silicon directly into the stack, freeing up die space on the compute side.

If it shipsThis is a real architectural change, not a spec bump — it raises how much of the memory problem HBM4-class parts can absorb without anyone else having to redesign around it.
SK Hynix is using Intel's packaging for its next HBM generation SK Hynix

Specifically Intel's EMIB advanced packaging technology, for SK Hynix's next generation of HBM memory chips.

Read on itThe HBM leader going outside its own fabs for packaging is a bigger deal than it sounds. Either it's smart supply-chain diversification, or a sign SK Hynix needed help hitting HBM4 timelines on its own. Probably too early to say which.
Marvell says CXL is now shipping at "extremely high volumes" Marvell earnings call

That's CEO Matt Murphy's phrase, from the earnings call, describing deployments across hyperscalers for both memory expansion and AI inferencing.

TranslationCXL-attached memory stopped being a roadmap slide sometime in the last year and turned into something you can actually plan an inference cluster's capacity around.
Gartner put lakeFS on its "Coolest Vendor Innovations" list Gartner · lakeFS

The recognition is for AI-driven data engineering automation — Git-style branching and versioning applied to datasets.

If this is youIf your team is still versioning training datasets by renaming folders, take this as your semi-annual nudge to look at something built for it instead.
Amazon bought DuckLabs, the company behind DuckDB Amazon

DuckDB shows up in a lot of local and edge AI data-prep tooling, so the acquisition matters less than Amazon's stated commitment to keep it free and MIT-licensed.

What to watchThat license commitment is the thing worth tracking over the next year, not the deal itself.
YMTC is targeting a $5B IPO in Shanghai YMTC

The explicit goal: become the world's largest NAND manufacturer by the end of 2027.

Why it mattersA serious fourth NAND supplier changes pricing leverage for everyone buying flash for AI storage tiers, whichever side of that trade you're on.
03 — Deep cut

Why Pure Storage is now called Everpure

A story instead of seven headlines, since this one deserves the room. It's also the reason Issue 01 had a mistake in it.

Pure Storage renamed itself Everpure, effective February 23, 2026. If you searched "Pure Storage" this week and ended up on everpuredata.com, that's not a phishing redirect. That's just where the company lives now. The ticker stays PSTG on the NYSE for the moment, though Barchart has reported plans to shorten it later this year.

Effective dateFeb 23, 2026
Corporate structureUnchanged
Contracts & SKUsUnchanged
Product renameRolling through 2026
PortworxKeeps its name — "by Everpure"
Action requiredNone, per the company

The company's own explanation is that it's "gone beyond storage to become a storage and data management company," and that Everpure fits a portfolio that now includes Pure Fusion and an Enterprise Data Cloud pitch, not just arrays. Outside coverage is less generous about it: this reads like a B2B infrastructure vendor renaming itself on the way upmarket, betting that owning "data primacy" — the layer AI systems actually reason over, not just the disks underneath — is a bigger and more defensible business than selling storage hardware. Whether that bet pays off against NetApp's AI Data Engine or Dell's AI-attach push is the thing actually worth watching, not the new name.

Correction, from Issue 01 We listed "Everpure" (IDC's #3-ranked vendor) and "Pure Storage" (FlashBlade, 10TB/s+ throughput) as two different companies. They're the same company, before and after the rename. Issue 01 published five months after the rebrand and we missed it. Fixed now.
04 — Uplevel highlight

This week's term: KV cache

One piece of storage or memory vocabulary, explained properly, every week.

KV Cache

In plain English: it's the model's short-term memory of everything it's already "read" in your conversation, kept around so it doesn't have to reprocess that text token by token.

When a model generates text, it computes a "key" and a "value" vector for every token it processes. The KV cache is just those vectors, stored so the model can reuse them instead of recalculating them from scratch for every new token. Model weights are a fixed size. The KV cache is not — it grows with context length and with how many people you're serving at once. Feed a 128K-token context into Llama 3 70B for a single user and the cache alone runs around 40GB, roughly half of one H100's memory, before you've served a second person.

That's the whole reason KV cache management turned into a storage problem instead of a pure GPU problem. When the cache doesn't fit, you have two choices: evict it and recompute later, which costs latency, or push it somewhere else and pull it back when needed — CPU RAM first, then NVMe, then further out if you have to. The second option only pays off if fetching the cache back beats just recomputing it, which comes down to context length, model size, and how fast your fabric actually is.

Nvidia made this official at CES 2026 with ICMSP (Inference Context Memory Storage Platform), a standard for offloading KV cache straight to NVMe over RDMA using GPUDirect Storage, claiming up to 5x better power efficiency and up to 5x more tokens per second under the right conditions. The partner list reads like a rerun of Issue 01's vendor section: Dell, HPE, IBM, VAST Data, WEKA, Everpure, DDN, and Supermicro. In one benchmark, a 128K context over 400Gbps RDMA took time-to-first-token from 11 seconds down to 1.5.

Why it's in this newsletterKV cache just became a storage tier. Every enterprise storage vendor is now also, whether it markets itself that way or not, an inference memory vendor.
05 — On the radar

What's coming up

SEP 15–17

AI Infra Summit 2026, Santa Clara. About as close as this space gets to a dedicated conference. Expect vendors to time announcements around it.

SEP–OCT

Q3 earnings season for storage and memory vendors (Samsung, SK Hynix, Western Digital, Seagate). Watch for capex guidance updates and anything on HBM4 qualification.

NOV 15–20

SC26, Chicago. The HPC/storage world's biggest annual gathering. Parallel file system and interconnect announcements tend to cluster here.