Apple chose Google Cloud to run Private Cloud Compute outside its own data centers for the first time, using NVIDIA Blackwell GPUs, Intel TDX, and Google's Titan chip. Apple maintains an independent append-only hardware ledger and dual-vendor attestation roots. AWS and Azure are not part of the collaboration. By Steef-Jan Wiggers
Apple is expanding its private cloud compute capability to meet increasing demand for its services while maintaining stringent privacy and security standards, leveraging external infrastructure. The advancements in secure computing hardware and cloud provider capabilities make this expansion feasible at this moment.
This move by Apple signifies a new paradigm in how major tech companies might leverage public cloud infrastructure for sensitive workloads, emphasizing security and privacy-by-design. It sets a precedent for hybrid and multi-cloud strategies focused on privacy and control, potentially influencing future cloud architecture decisions across industries.
Apple is now utilizing a third-party cloud provider, Google Cloud, for its Private Cloud Compute, departing from its historical reliance solely on its own data centers for such sensitive operations. This indicates a potential shift in Apple's infrastructure strategy and a validation of Google Cloud's security capabilities.
- · Google Cloud
- · NVIDIA
- · Intel
- · Cloud Security Providers
- · AWS
- · Microsoft Azure
- · Proprietary Data Center Hardware Vendors
Apple expands its high-security private cloud infrastructure without building more of its own data centers.
Other companies with stringent data privacy requirements may explore similar hybrid cloud models, increasing demand for secure hardware and attestable cloud services.
This could lead to a 'race to the top' among cloud providers to offer even more robust confidential computing and verifiable privacy solutions, segmenting the cloud market further.
This signal links to a primary source. Continuum Brief monitors and indexes it as part of the live intelligence stream — we do not republish source content.
Read at InfoQ