Google’s demand for advanced chip packaging has pushed Intel to accelerate its EMIB-T technology, now pulling in two additional Taiwanese manufacturers to meet growing TPU production needs. The shift comes as TSMC’s CoWoS process faces increasing strain, raising questions about whether Intel can fill the gap without disrupting its own roadmap.
Intel’s EMIB-T, designed for high-performance computing, is being adopted by Google for its next-generation TPU chips. Unlike traditional multi-chip packages, EMIB-T uses a hybrid approach that combines silicon interposers with advanced routing layers, improving thermal efficiency and signal integrity. This is not Intel’s first foray into packaging for AI workloads—it has already supplied similar solutions for other high-end data center chips—but the expansion of suppliers signals a deliberate push to scale production.
The two new Taiwanese manufacturers, which have been working with Intel on EMIB-T for over a year, represent a strategic diversification. Historically, TSMC’s CoWoS has been the go-to choice for Google and other hyperscale players due to its mature process node advantages and higher yield rates. However, reports suggest that TSMC is now prioritizing its own advanced packaging needs, leaving room for alternatives like Intel’s EMIB-T to gain traction.
For IT teams evaluating upgrade paths, the timing of this shift matters. Google’s TPU chips are critical for large-scale AI training and inference, and any delay in packaging availability could push out deployment timelines. While Intel’s move is a positive development, it remains unclear whether EMIB-T can match CoWoS in terms of yield consistency or cost efficiency at scale. Early benchmarks suggest performance parity, but real-world reliability data is still limited.
The bigger question is whether this will lead to broader industry adoption or remain niche. Intel’s packaging technology has yet to prove itself outside Google’s ecosystem, and competition from TSMC, Samsung, and others continues to intensify. For now, IT teams should treat this as a supplementary option rather than a replacement for CoWoS, at least in the near term.
