Topicscustom-hbm

When Memory Became a Logic Chip

A sourced reference collection on the change that reframed high-bandwidth memory — the die at the bottom of the stack moving off a memory process onto a foundry logic process, which turned memory makers into foundry customers, made the stack customisable per buyer, and let vendors ship parts far faster than the standard they are built to.

Assertions
8
Sources consulted
20
Read in full
5/20
Cited as evidence
5

20 sources sit behind this page — including any that arrive with a concept this page shares with another collection. 5 were retrieved and read in full, and only those can back an assertion. 2 could not be retrieved, and 13 were surfaced and deliberately set aside. Every one of them is named in the register below, with the reason in view. How we source this.

Background

Our own synthesis, written to orient you — not evidence. Every factual statement here is asserted and sourced further down this page.

An HBM stack has always had a die at the bottom that is not memory. It carries the memory controller, power delivery, refresh and the protocol conversion between the stack and the processor. Through HBM3E it was fabricated on a memory maker's own process, and nobody outside the industry had reason to think about it.

In April 2024 SK hynix and TSMC signed a memorandum of understanding to build the HBM4 base die on TSMC's advanced logic foundry process instead, stating the purpose plainly: to pack additional functionality into limited space, and to produce customised HBM for varying customer performance and power requirements. Samsung reached the same place by a different route, putting its HBM4 base die on a 4nm logic process alongside a 1c DRAM process for the memory, and saying it took that leap rather than the conventional path of proven designs in order to secure performance headroom.

That is a structural change, not an incremental one. A memory manufacturer needing a leading-edge logic die becomes a foundry customer or must run a foundry itself. The base die's process now moves with the logic roadmap rather than the DRAM roadmap. And because logic is where you put the things that differ between customers, the memory stack stops being a catalogue part.

The clearest evidence of what that bought is the gap between the standard and the parts. JEDEC published JESD270-4 on 16 April 2025 specifying HBM4 at up to 8 Gb/s across a 2048-bit interface for total bandwidth up to 2 TB/s, doubling channels per stack from 16 to 32, and — the clause that shows what a standard is for — staying backwards compatible with existing HBM3 controllers. Ten months later Samsung began mass production at 11.7 Gbps, describing that in its own announcement as roughly 46% above the 8 Gbps industry standard, reaching a maximum 3.3 TB/s per stack against a specified 2. Micron, meanwhile, is reported working to a pin speed set by revised NVIDIA specifications rather than by JEDEC.

So the published standard functions as a floor and an interoperability contract while the real target is set by the largest customer — and the logic base die is the part of the stack where a vendor can exceed the floor and a buyer can ask for something the standard never contemplated. Samsung puts HBM4E sampling in the second half of 2026 and custom HBM samples with customers in 2027, tied explicitly to hyperscaler ASIC development.

Where it goes next was set out at Hot Chips in 2026 in three phases: first the memory controller, a defect-remapping table and a custom die-to-die interface move onto the logic die; then sensors, test blocks, external memory PHYs and in-memory compute; then HBM stacked directly on the compute chip, which would abolish the distinction between memory and processor package. The independent account carrying that roadmap also carried the two objections that would stop it — thermals, by analogy with stacked-cache processors that clock lower than their flat equivalents, and doubt that processing elements on a base die can hold enough cache to be useful.

What is reported rather than announced is marked as such throughout. Process nodes for the generation after HBM4, named hyperscaler qualifications, yield percentages and the claim that a foundry has turned over half a leading-edge node's capacity to memory base dies all circulate widely; none of them is asserted here.

Figures

Every number below is asserted and sourced elsewhere on this page.

The standard, and what shipped

HBM pin speed: the previous generation's maximum, the HBM4 standard's ceiling, and the part in mass production. The middle bar is the specification, not the limit.

Pin speed, gigabits per second

9.6 Gbps

HBM3E maximum

8 Gb/s

HBM4 standard ceiling

11.7 Gbps

Shipped HBM4

HBM3E maximum pin speed of 9.6 Gbps and shipped HBM4 at 11.7 Gbps (capable of 13) from Samsung's own February 2026 announcement; the 8 Gb/s figure from JEDEC's April 2025 announcement of JESD270-4. Samsung itself states the 11.7 figure exceeds the 8 Gbps standard by approximately 46%.

Bandwidth per stack, specified against shipped

Total bandwidth from one HBM4 stack. The standard says up to two terabytes a second; the part in production reaches three point three.

Bandwidth per stack, terabytes per second

2 TB/s

JESD270-4 specified maximum

3.3 TB/s

Samsung HBM4 in production

Up to 2 TB/s from JEDEC's April 2025 announcement of JESD270-4; a maximum of 3.3 TB/s per single stack, stated as 2.7x HBM3E, from Samsung's February 2026 announcement. SK hynix is separately reported at bandwidth exceeding 2 TB/s, which is not plotted because it is a floor rather than a figure.

Concepts

The vocabulary this subject is built from, and what we can show about each.

CoWoS (Chip-on-Wafer-on-Substrate)

packaging technologyshared from another collection — see its own page for what it asserts

Custom AI ASIC

componentshared from another collection — see its own page for what it asserts

Custom HBM

memory technology

Because the base die is a logic die, memory stops being a catalogue part: SK hynix stated customisation as the purpose of the foundry shift, and Samsung puts HBM4E sampling in the second half of 2026 and custom HBM samples with customers in 2027, tied to hyperscaler ASIC development.

ReportedSupported by the sources below, not yet editor-reviewed.
2 sources2 retrieved & read

DRAM Process Node

processshared from another collection — see its own page for what it asserts

HBM Base Die (Buffer Die)

component

Samsung's stated base-die roadmap has three phases — memory controller, remapping table and custom die-to-die interface; then sensors, test blocks, external memory PHYs and in-memory compute; then stacking HBM directly on compute — against which the independent account raises thermals, citing AMD 3D cache parts clocking lower, and doubts near-memory compute on cache-capacity grounds.

ReportedSupported by the sources below, not yet editor-reviewed.
1 source1 retrieved & read

The HBM base die moved off a memory process onto a foundry logic process — SK hynix adopting TSMC's logic process for HBM4 under an April 2024 memorandum, Samsung using a 4nm logic die alongside 1c DRAM — which makes a memory maker a foundry customer and makes the stack customisable per buyer.

ReportedSupported by the sources below, not yet editor-reviewed.
3 sources3 retrieved & read

High Bandwidth Memory (HBM)

memory technologyshared from another collection — see its own page for what it asserts

The HBM4 Standard, and Shipping Past It

memory technology

JEDEC's JESD270-4, published 16 April 2025, specifies HBM4 at up to 8 Gb/s across a 2048-bit interface for up to 2 TB/s, doubles channels per stack from 16 to 32 with two pseudo-channels each, adds Directed Refresh Management for row-hammer mitigation, supports 4- to 16-high stacks at 24 or 32 Gb dies for up to 64GB, and stays backwards compatible with HBM3 controllers.

ReportedSupported by the sources below, not yet editor-reviewed.
1 source1 retrieved & read

Samsung ships HBM4 at 11.7 Gbps — by its own statement about 46% above the 8 Gbps standard — reaching 3.3 TB/s per stack against a specified 2 TB/s, while Micron is reported working to a pin speed set by revised NVIDIA specifications rather than by JEDEC: the standard is a floor, and the largest customer sets the target.

ReportedSupported by the sources below, not yet editor-reviewed.
3 sources3 retrieved & read

Through-Silicon Via (TSV)

interconnectshared from another collection — see its own page for what it asserts

Timeline

What actually happened, in order, with sources.

Coverage
  • 2 South Korea
  • 1 United States
  • 1 Unattributed

Where this topic’s events took place, as far as our sources establish it. Events with no single location — a standards publication, say — and events we have not yet attributed are both counted as unattributed rather than omitted.

  1. Feb 12, 2026

    A Part Ships Well Past Its Own Standard

    production milestoneSouth Korea

    Samsung began HBM4 mass production on 12 February 2026 at a consistent 11.7 Gbps — by its own statement about 46% above the 8 Gbps standard — with up to 3.3 TB/s per stack, 12-layer 24-36GB parts on a 4nm logic base die and 1c DRAM, and claimed 40% better power efficiency than HBM3E.

    ReportedSupported by the sources below, not yet editor-reviewed.
    2 sources2 retrieved & read
  2. Apr 16, 2025

    JEDEC Publishes the HBM4 Standard

    standards milestoneUnited States

  3. Apr 2025

    JEDEC Releases the HBM4 Standard (JESD270-4)

    standards milestone

    JEDEC published JESD270-4 on 16 April 2025 specifying HBM4 at up to 8 Gb/s over a 2048-bit interface for up to 2 TB/s, 32 channels per stack with two pseudo-channels each, Directed Refresh Management, 4- to 16-high stacks at 24 or 32 Gb dies for up to 64GB, and backwards compatibility with HBM3 controllers.

    ReportedSupported by the sources below, not yet editor-reviewed.
    1 source1 retrieved & read
  4. Apr 19, 2024

    A Memory Maker Becomes a Foundry Customer

    partnershipSouth Korea

    SK hynix announced on 19 April 2024 a memorandum of understanding under which it would build the HBM4 base die on TSMC's advanced logic foundry process rather than its own, to add functionality in limited space and produce customised HBM, alongside CoWoS integration work, with HBM4 mass production from 2026.

    ReportedSupported by the sources below, not yet editor-reviewed.
    1 source1 retrieved & read

Source register

All 20 sources behind this page — what we read, what we tried to read and could not, and what we looked at and set aside, with the reason in view for each. A concept shared with another collection brings its own references with it, so some entries here were surfaced for a neighbouring topic rather than this one.

Cited as evidence
5
Tried, could not read
2
Surfaced, set aside
13
Cited sources 5 distinct links

Original publisher links. Files open on the publisher’s site; we do not host copies. A linked document is not an additional source or an independent verification.

Tried, could not read2

We attempted these and were refused or served nothing. Nothing on this page rests on them; they are published so the gaps are checkable rather than invisible.

Surfaced, set aside13

These came up while researching and were deliberately not used. We do not claim to have read them — each is listed with why it was passed over, so the shape of the survey is visible and not just its conclusions.

Coverage & limits

What this page does and does not claim.

Eleventh packet, and the first that extends a concept another collection already defined rather than restating it: the HBM packet describes what a base die does, and this one records that it stopped being made like memory. Ten sources were consulted: five were retrieved and read, and five were surfaced and set aside with a stated reason. Two of the reads did not come back to the automated fetcher — one returned HTTP 403, one timed out — and were opened in a browser instead; no paywall, registration wall or challenge was circumvented anywhere in this collection. The source base is unusually solid for a subject this heavily speculated about: a standards body's own announcement, two memory manufacturers' own releases, and two independent technical reports. The central finding is measurable from primaries on both sides — JEDEC specifies 8 Gb/s and up to 2 TB/s, Samsung ships 11.7 Gbps and 3.3 TB/s and itself describes that as about 46% above the standard — which is why it is asserted rather than characterised. Everything reported rather than announced is attributed as a report in the text: SK hynix's 12nm base-die node appears in trade coverage and not in its own release; a mass-production yield percentage and a system-in-package qualification for a hyperscaler's accelerator are reported, not confirmed by the parties; and process nodes for the generation after HBM4 are set aside entirely. Named gaps, in order of value: reports that a foundry has directed more than half of a leading-edge node's capacity to memory base dies, which if verified would be the most consequential second-order effect of this whole shift and is the largest hole here; Micron's own HBM4 disclosure, whose absence means the third of the three suppliers appears only through a trade report and its base-die process choice is not established at all; the JESD270-4 document itself, available on registration and not downloaded, so the standard's figures come from JEDEC's summary of it rather than its clauses; and the Hot Chips presentation behind the three-phase base-die roadmap, which reaches this page through an independent write-up whose author's scepticism is carried alongside it. Not yet editor-reviewed; every assertion reads as reported.

Source check, 2026-09-17. Numeric-presence checks passed for 8 assertions using available source text, which may be cached. This is not verification of their meaning. What this check does and does not prove →

  • Not editor-reviewed unless labelled. Assertions marked Reported are assembled from the sources shown and have not yet been checked by an editor. Only Primary source and Corroborated mean a human verified them.
  • Disagreements are preserved, not resolved. Where sources conflict, both accounts appear and the assertion is marked Disputed.
  • Retrieval status is disclosed per source. A source we could not open is never counted as evidence for an assertion.

This page is also available as structured data: /api/v1/topics/custom-hbm