Skip to content
Go back

The AI Supply Chain Became Part of the Architecture

An AI accelerator is no longer manufactured as one chip.

The finished device joins logic dies from a leading-edge foundry, stacks of high-bandwidth memory, silicon or organic interconnect structures, package substrates, thousands of microscopic connections, thermal materials, assembly processes, and several layers of test. The product ships only when every stage is available, qualified, and yielding together.

That makes the supply chain part of the architecture. Memory bandwidth determines the useful compute rate. Interposer area determines how much logic and HBM can sit in one package. Chiplets change the yield and integration model. Substrate dimensions affect routing and mechanical limits. Packaging and test capacity determine how many complete accelerators can leave the factory.

The fastest logic die is inventory until the serial system around it works.

TL;DR

The product is a dependency chain

A conventional description begins with the compute die and works outward. Manufacturing works in the opposite direction: every upstream component must converge at the package assembly step, and the assembled device must still pass test.

This is a serial dependency with parallel inputs. More logic-wafer output cannot compensate for missing HBM. More HBM cannot compensate for unavailable interposer or substrate capacity. Extra assembly tools do not solve a package that has not completed electrical, thermal, and reliability qualification.

The dependency also runs backward. A package that can hold more HBM changes the memory controller and floor plan. A taller memory stack changes thermal and mechanical constraints. A larger interposer changes package warpage, routing, substrate, and test requirements. Manufacturing is not a procurement step applied after architecture; it constrains the design before tape-out.

Leading-edge logic is only the first factory

Foundry process nodes still matter because transistor density and energy efficiency set the compute die’s starting envelope. But a node announcement is not an accelerator shipment.

TSMC states that its N2 process entered high-volume manufacturing in the fourth quarter of 2025. The same source schedules N2P and A16 volume production for the second half of 2026. Those are foundry production milestones. They do not establish which accelerator products have completed design, packaging, qualification, and customer shipment on each process.

The node boundary is also becoming less useful as a description of the whole device. One package can combine compute chiplets, I/O dies, cache, interface dies, and HBM manufactured on different processes. Advanced logic may need the newest node; analog, I/O, or interface functions may not. The package becomes the place where several manufacturing choices become one system.

TSMC’s SoIC description explicitly supports homogeneous and heterogeneous chiplets and positions the resulting stacked structure for later integration into CoWoS or InFO packaging. That creates another dependency boundary: known-good dies must be bonded with sufficient alignment, connection density, thermal performance, and yield before the larger package can be assembled.

Chiplets can make a large design more manufacturable. A smaller die occupies less wafer area and may lose fewer complete products to an individual defect than one reticle-scale monolith. The architecture can also reuse a qualified I/O or interface die across products.

The trade is added integration. Every partition introduces a die-to-die link, protocol, clocking and power behavior, package routes, test coverage, and another component whose yield affects finished output. The UCIe 3.0 specification standardizes capabilities for die-to-die connectivity and manageability. It does not make chiplets from different processes or suppliers automatically qualified as one package. Electrical interoperability is one condition; thermal, mechanical, manufacturing, firmware, and lifecycle compatibility remain product work.

HBM is part of the compute architecture

The memory beside the accelerator is not a generic capacity pool. HBM places several DRAM dies in a vertical stack connected through through-silicon vias, then joins those stacks to the logic through a wide package-level interface.

That arrangement delivers high bandwidth without driving thousands of long board traces. It also makes memory inseparable from package planning. The accelerator needs a defined number of HBM sites, interface width, stack height, capacity, data rate, power envelope, and cooling path. Changing the HBM generation can change the logic interface and package, not merely the bill of materials.

JEDEC published the HBM4 standard in April 2025 with a 2,048-bit interface—twice the channel count of HBM3—and support for 4-high through 16-high stacks. The standard establishes the interface boundary. Vendors still need to manufacture DRAM dies, assemble and test stacks, qualify them with logic and packaging partners, and ramp complete systems.

The status of HBM4 illustrates why evidence labels matter:

These companies compete in memory, but every HBM stack also passes through packaging and qualification boundaries. A supplier can have DRAM wafer output without equivalent finished-stack output. A customer can receive samples without a qualified production volume. A memory forecast can be directionally useful while saying nothing about how many accelerator packages can ship in a specific quarter.

The interposer became a system component

CoWoS-class packaging solves a physical problem: a compute complex and multiple HBM stacks need far denser, shorter connections than a conventional printed circuit board can provide.

TSMC describes CoWoS as a 2.5D platform integrating logic chiplets and HBM over an interposer. Its CoWoS-S implementation supports silicon interposers up to 3.3 reticle sizes, while larger designs use CoWoS-L or CoWoS-R. TSMC says its first 3.5-reticle CoWoS-L entered volume production in 2024.

The word “package” hides several different structures:

LayerArchitectural jobManufacturing dependency
Logic die or chipletsExecute tensor, vector, control, networking, and I/O functionsFoundry node, masks, wafer yield, wafer sort, known-good die
HBM stacksHold model state, activations, cache, and intermediate data near computeDRAM fabrication, TSV formation, stacking, bonding, stack test, qualification
Interposer or redistribution layersProvide dense logic-to-logic and logic-to-HBM wiringInterposer/RDL fabrication, large-area yield, alignment, routing, power integrity
Package substrateEscape signals and power from the fine-pitch package to the boardLarge substrate availability, layer count, vias, warpage control, supplier qualification
Assembly materialsAttach, underfill, protect, and thermally connect the diesBonding equipment, material availability, process control, thermal-mechanical reliability
Test and burn-inReject defective dies, stacks, packages, and marginal assembliesTest equipment, sockets, probe cards, test time, coverage, repair or scrap policy

As interposers and substrates grow, the package faces more than an area problem. Longer routes affect signal and power integrity. More active silicon increases power delivery and heat flux. Large thin structures can warp during processing. One defective input can reduce the economic yield of a package containing several expensive known-good components.

This is why advanced packaging capacity cannot be represented as one interchangeable number. CoWoS-S, CoWoS-L, fan-out-on-substrate, flip-chip ball-grid array, hybrid bonding, memory stacking, and final test use different equipment, materials, process flows, package sizes, and qualifications.

Assembly and test are not the final commodity step

Outsourced semiconductor assembly and test providers sit at a critical boundary between fabricated dies and usable systems.

ASE’s fan-out technology includes FOCoS configurations that combine fine-pitch redistribution layers with package substrates for high-performance applications. In May 2026, ASE and WUS announced a planned Kaohsiung facility focused on FOCoS and flip-chip BGA processes. ASE separately broke ground on two buildings scheduled for completion in the second quarter of 2028, including expanded packaging and high-frequency, high-power, high-parallelism test capability.

Those facilities are announced future capacity. They are not available 2026 output.

Amkor’s 2025 annual report describes advanced SiP, flip-chip, wafer-level, and test services across its manufacturing network. Its planned Peoria, Arizona advanced packaging and test campus remains a construction and startup program. Amkor’s May 2026 update says the planned investment expanded to $7 billion; that figure describes project scope, not installed or qualified production capacity.

Test becomes harder as integration rises. Wafer sort attempts to avoid placing a defective logic die into an expensive package. HBM stack testing attempts the same for memory. Package test then validates an assembly with many high-speed interfaces, power domains, thermal behaviors, and repair limits. System qualification adds boards, firmware, cooling, and workload stress.

Test time is therefore capacity. A more complex coverage plan can reduce the number of units passing through the same equipment per day. Weak coverage can increase downstream failures after more value has been added. The economic objective is not maximum test speed; it is finding defects at the earliest stage where they can still be isolated cheaply.

Three evidence classes, not one supply number

Supply-chain claims become misleading when construction plans and demand forecasts are added to shipping output.

Evidence classWhat it establishesCurrent examplesWhat it does not establish
Shipping or volume productionA named process or product has entered production or shipmentTSMC N2 high-volume manufacturing; Samsung and Micron HBM4 production claims; TSMC 3.5-reticle CoWoS-L volume productionCustomer-wide availability, yield, allocation, price, or finished accelerator volume
Announced capacityCapital, site, technology, and target timing have been disclosedMicron’s Singapore HBM packaging facility; ASE’s Kaohsiung expansion; Amkor’s Arizona campus; SK hynix’s Indiana HBM packaging projectTools installed, process qualification, customer qualification, usable output, or on-time completion
Forecast or guidanceA company states its expected demand, revenue, ramp, or future salesSamsung’s forecast for 2026 HBM sales; vendor statements about future AI demandPhysical capacity, shipment, independent demand validation, or a finished-system delivery date

Micron’s Singapore HBM packaging facility shows the timing gap clearly: construction began in 2025, operations were scheduled to start in 2026, and meaningful expansion of total advanced packaging capacity was expected beginning in 2027. SK hynix’s Indiana project similarly announced investment and a future advanced HBM packaging facility. Neither announcement should be counted as current finished-stack supply before operations and qualification are confirmed.

The clean unit of evidence is a qualified output at a named boundary: logic wafers, known-good dies, tested HBM stacks, assembled packages, accelerator modules, or deployed systems. Moving between those units requires another yield, capacity, and qualification assumption.

What’s missing

Public disclosures identify technologies, investments, production milestones, and selected product shipments. They rarely expose the full conversion funnel.

A complete supply model would need wafer starts by relevant node, die area, wafer yield, known-good die inventory, HBM stack yield, interposer and substrate availability, package assembly yield, test duration, rework rate, customer qualification status, allocation, and the number of finished accelerators produced. The companies in this chain do not publish that shared dataset.

That makes precise bottleneck claims difficult. “HBM constrained” can mean DRAM wafer output, stack assembly, base-die availability, test, customer qualification, or package integration. “Packaging constrained” can refer to interposers, redistribution layers, substrates, bonding tools, materials, assembly cycle time, or test. The label names a layer, not the failing operation.

So what

Architecture reviews need a manufacturing column.

For every accelerator, ask which foundry process is shipping, how many logic dies and HBM stacks enter the package, what interposer or fan-out structure connects them, which substrate and assembly flow it requires, where known-good-die testing occurs, and which capacity claims describe output rather than future investment.

The architectural frontier is no longer the compute die alone. It is the ability to manufacture a large heterogeneous system with enough bandwidth, acceptable power, controlled thermals, qualified yield, and repeatable test.

The open question is where the next constraint migrates as HBM and advanced packaging investment comes online. Does supply become limited by logic wafers again—or do larger chiplet systems move the bottleneck into substrates, hybrid bonding, thermal materials, and test faster than the industry can qualify the next process?


Part of the AI Compute Landscape — an ongoing exploration of accelerator architectures, software stacks, and data-center systems.


Share this post on:


Previous Post
When the Platform Operator Designs the Chip
Next Post
There Is No Universal AI Runtime—So Build a Portable Control Plane