Apple's Private Cloud Compute (PCC) platform is expanding beyond Apple-operated hardware, with Google Cloud confirmed as a hosting partner during WWDC 2026. The two companies, working alongside Intel and NVIDIA, have built a serving platform designed to satisfy PCC's security, confidentiality, and auditability requirements.
Background: Private Cloud Compute is Apple's architecture for offloading sensitive on-device AI tasks to cloud infrastructure while preserving user privacy. The system is designed so that neither Apple nor its cloud partners can access the plaintext of user requests.
How the stack is constructed
The foundation of the deployment is Google Cloud's Confidential Computing portfolio. Hardware-based Trusted Execution Environments (TEEs) keep workload data encrypted while it is actively being processed — a property distinct from encryption at rest or in transit. Google pairs this with its Titanium security architecture, which centers on the custom-designed Titan chip. That chip establishes a hardware root of trust from the point a server boots, giving downstream software a verifiable foundation to build upon.
For AI inference specifically, the implementation uses Intel Trust Domain Extensions (TDX) on the CPU side and NVIDIA Confidential Computing on the GPU side, with NVIDIA Blackwell hardware cited as the GPU platform. The intent is that the entire compute path — from initial CPU processing through GPU inference — remains inside a protected boundary, reducing the attack surface for any actor attempting to inspect or intercept workload data.
Beyond hardware, Apple and Google co-engineered an open-source host stack expressly to support PCC's transparency requirements. Because the software is publicly available for inspection, third parties can independently verify the security properties of the system rather than relying solely on vendor assertions. Google describes the design goal as providing enforceable protections with no privileged runtime access — meaning even Google Cloud operators cannot reach into running PCC workloads.
Relevance to cloud and infrastructure professionals
For providers and engineers working in confidential computing, the collaboration is a large-scale production deployment of a multi-vendor TEE stack: Intel TDX for CPU isolation, NVIDIA's confidential GPU mode for accelerator-side protection, and a silicon root of trust via a proprietary chip — all in a single pipeline. That combination has been discussed in the industry for some time; this deployment gives it a high-profile, externally auditable reference architecture.
The open-source host stack component is notable for managed-service and sovereign-cloud operators. Customers with strict audit requirements increasingly ask for verifiable transparency rather than contractual guarantees alone. An open, inspectable software layer that sits beneath a confidential workload could become a template for other regulated or privacy-sensitive deployments.
Google states that the engineering work done for the Apple collaboration will flow into its general Confidential Computing offering, meaning features developed to meet Apple's requirements will eventually be accessible to other Google Cloud customers. That trajectory is relevant for product teams evaluating whether confidential computing can support their own sensitive AI inference workloads without requiring a bespoke arrangement.
For professionals: Operators considering confidential AI inference should note that this deployment uses Intel TDX and NVIDIA Blackwell together as a validated combination for end-to-end TEE coverage. The open-source host stack published as part of the collaboration provides a concrete reference for teams designing auditable, no-operator-access infrastructure. Google's indication that these capabilities will be generally available means procurement timelines for similar architectures may be shorter than anticipated.
Automated pipeline · Cloud & Infrastructure
Synthesized from 1 industry feed on 13 Jun 2026. Passed independent editor verification before publication. Style guide v1.1.
Sources
Decision trail
- Checking for duplicates — New story Google Cloud partners with Apple on Private Cloud Compute for confidential AI workloads.
- Writing the article — Draft created article_id=13 slug=apple-expands-private-cloud-compute-onto-google-cloud-infrastructure
-
Editor review — Approved
- Factual grounding: Minor: The standfirst describes the inference as 'cryptographically verifiable AI inference.' The source mentions 'cryptographic assurances' and 'verifiable transparency/integrity' but does not use the phrase 'cryptographically verifiable AI inference' as a unified descriptor. This is a reasonable synthesis but slightly collapses distinct properties
- not materially wrong.
- Factual grounding: Minor: The body states Google 'describes the design goal as providing enforceable protections with no privileged runtime access.' The source says 'enforceable protections, no privileged runtime access, and verifiable transparency.' The article omits 'verifiable transparency' from this list, which is a minor omission but does not invent anything.
- Factual grounding: Minor: The article states 'Google states that the engineering work done for the Apple collaboration will flow into its general Confidential Computing offering.' The source says 'The advancements built through this collaboration will benefit all Google Cloud customers' and commits to 'more transparent, secure, resilient platforms.' The article's characterisation is a reasonable paraphrase but slightly stronger in specificity than the source wording.
- No copied phrasing: Minor: 'the entire compute path — from CPU to GPU — is protected' in the article closely echoes the source's 'the entire compute path – from CPU to GPU – is protected.' The em-dash substitution and minor rephrasing are insufficient to constitute independent rewriting of this phrase.
- Style compliance: Minor: Body word count is approximately 620-640 words, which is at or just above the 620-word soft target but below the 750-word hard maximum. Borderline but not a hard violation.
- Sanity: Minor: Only one source is cited. The style guide requires synthesising from ALL provided sources, which here is only one source, so this is satisfied. No issue in practice.
- Linking related stories — Linked 0 relations from 0 candidates
- Assigning hero image — Pexels pexels_id=37730211
- Linking related stories — Linked 0 relations from 0 candidates
- Linking related stories — Linked 1 relations from 4 candidates
- Linking related stories — Linked 1 relations from 4 candidates
- Linking related stories — Linked 1 relations from 8 candidates
- Linking related stories — Linked 1 relations from 8 candidates
- Linking related stories — Linked 1 relations from 8 candidates
- Publishing — Published apple-expands-private-cloud-compute-onto-google-cloud-infrastructure

Discussion · coming soon
Be the first to join the thread when community discussion launches.