Why Do Hyperscalers Design Their Own CPUs?
By Sally Ward-Foxton, EETimes | April 10, 2025
SAN JOSE, Calif. – U.S. hyperscalers like AWS, Google and Microsoft have designed their own CPUs for the data center in recent years, investing hundreds of millions of dollars into their own chip designs. All these CPUs are based on Arm. But with other options on the market, what motivates these companies to spend the time and money on building their own silicon?
Arm’s infrastructure chief, Mohamed Awad, told EE Times that while cutting out the middle man and dealing directly with foundries does mean hyperscalers can cut out chipmakers’ margins, this is not the whole picture.
To read the full article, click here
Related Semiconductor IP
- Multi-core capable 64-bit RISC-V CPU with vector extensions
- Highly configurable HW PQC acceleration with RISC-V processor for full CPU offload
- RISC-V CPU IP
- Data Movement Engine - Best in class multi-core high-performance AI-enabled RISC-V Automotive CPU for ADAS, AVs and SDVs
- Multi-core capable 32-bit RISC-V CPU with vector extensions
Related News
- Why Do Big Companies Make Their Own Sensors?
- Why ASIC Design Makes Sense for LLM-On-Device
- Dolphin Design unveils the final piece of their platform offer with BAT, an audio solution for high quality AIoT applications
- SigmaSense Teams Up with Dolphin Design to Deliver Power Efficiency in their Advanced SDC300 Touch Controller
Latest News
- EnSilica to develop quantum-resilient secure processor chip for critical national infrastructure applications backed by £5m UK Government ‘Contract for Innovation’
- CAST Introduces JPEG XL Encoder IP Core for High- Quality, On-Camera Still-Image Compression
- PGC Strengthens Cloud and AI ASIC Acceleration with Synopsys’ Next-Generation Interface and Memory IP on Advanced Nodes
- IntelPro Licenses Ceva Wi-Fi 6 and Bluetooth 5 IPs to Launch AIoT Matter-Ready SoCs
- VeriSilicon and Google Jointly Launch Open-Source Coral NPU IP