Google Cloud Next '26 AI Announcements

The most consequential hardware decision in Next '26 is not that Google shipped a new TPU — it's that Google shipped two of them. TPU 8t (codename 'Sunfish') is a training monster: 9,600 chips per superpod, 2 petabytes of HBM, 121 exaflops of FP4, 3x the processing power of last year's Ironwood, and double Ironwood's interchip bandwidth. TPU 8i is a different animal entirely — 1,152 chips per pod, 11.6 exaflops FP8, 3x more on-chip SRAM than Ironwood, 19.2 Tbps bidirectional scale-up bandwidth per chip, and 80% better performance per dollar for LLM inference. The architectural split says the quiet part out loud: training and inference have diverged enough as workloads that one chip can no longer be optimal for both.

The contrast with Nvidia is structural, not marketing. Nvidia's Rubin NVL72 caps its NVLink coherence domain at 576 accelerators; TPU 8t goes to 9,600. Google is trading per-chip peak performance for system-scale bandwidth, betting that frontier training runs are now bottlenecked by how many chips can share memory at speed, not by what a single chip can do. On the inference side, the 8i's enlarged SRAM cache and higher-capacity memory pool specifically target the memory-bandwidth wall that agent inference hits — long context windows, multi-step tool calls, and the kind of always-on reasoning fleets Pichai described when he said the industry has gone from 'Can we build an agent?' to 'How do we manage thousands of them?' The 8t/8i split is what 'managing thousands' looks like in silicon.

Pretty much every product recap of Next '26 buries the number that actually matters. Google Cloud ended 2025 with a $240 billion backlog — up roughly 160% year-over-year. Q4 2025 cloud revenue hit $17.7B, up 48% YoY. Alphabet guided 2026 capex to $175-185B. Those numbers reframe the keynote from a product showcase into a capital-allocation story: Google has already sold the capacity it's now building, and the event's job was to convince enterprises to convert signed commitments into live, recurring agent workloads. JPMorgan's Doug Anmuth caught this explicitly when he wrote, 'While Cloud Next has not been a major catalyst for GOOG/L shares in the past, we believe the event carries more weight this year' — not because the chips are flashier but because agentic deployments are 'recurring & much harder for customers to rip out.'

The stickiness is the point. An enterprise that runs its sales ops, code migration, and SOC on Gemini Enterprise agents — grounded in a Knowledge Catalog over an Apache Iceberg lakehouse and governed by Google's four-pillar agent platform — is not switching clouds on a pricing page comparison. It's switching operational substrate. That's why the $750M partner fund (widely misreported as $7.5B) is structured to subsidize the proof-of-concept phase: Gemini POC credits, Google forward-deployed engineers, cloud credits, and deployment rebates. Google is paying to remove the adoption friction because every enterprise that converts becomes a compound interest machine for the backlog. The announcements are downstream of the balance sheet, not the other way around.

Every major outlet has run some version of 'Google vs Nvidia' this week, and Futurum's Daniel Newman pushed back hard and early: 'I strongly suggest not spinning wheels on the TPU versus GPU debate. Right now all capacity is good capacity because we don't have close to enough compute.' The point is worth taking seriously. Google is still positioned to be among the first clouds to offer Nvidia's Vera Rubin NVL72 systems in the second half of 2026, and its own multi-vendor ASIC supply chain — Broadcom, MediaTek, Marvell, Intel — reads less like an anti-Nvidia play and more like de-risking single-vendor dependency while the entire industry is compute-starved. Supply-chain analyst Dan Nystedt has flagged the TPU v8 split as a strategic capacity move as much as a technical one.

The more interesting competitive frame comes from SiliconANGLE's John Furrier: 'Models are becoming a commodity. Inference is getting cheaper by the month. The leverage is moving up the stack.' If that's right, the Next '26 fight isn't silicon-versus-silicon at all — it's control-plane-versus-control-plane. The Gemini Enterprise Agent Platform, Workspace Intelligence as a semantic layer across Gmail/Docs/Sheets/Slides/Drive/Chat, BigQuery reframed as a reasoning surface rather than a storage surface, and the Agentic Defense fusion with Wiz are all bids for the layer where enterprise execution actually happens. Nvidia doesn't compete there; Microsoft, AWS, Salesforce, and ServiceNow do. Reading Next '26 as a hardware keynote misses which fight Google is actually picking.

Fortune's Big Technology column named the subtext no one on the keynote stage said out loud: 'AI's abilities have outpaced humans' capability to implement them.' The headline stats from Google itself are almost too on-the-nose — 75% of new Google code is AI-generated and engineer-approved (up from 50%), code-migration tasks run 6x faster with agentic workflows, SOC agents cut threat mitigation time by more than 90%. Google has already eaten its own dog food; most of its customers haven't. The entire Next '26 product surface — the four-pillar agent platform (Build, Scale & Orchestrate, Govern, Optimize), the Data Agent Kit, the Deep Research Agent, the $750M partner fund — is engineered against that implementation gap. If Google can close it for enterprises, Fortune argues, 'the payoff could be further gains against Amazon Web Services and Microsoft's Azure.'

The second-order effect is the business-model reshuffle Furrier flagged bluntly: 'The app is no longer the product. The agent is.' If cross-app agents run the workflow and the SaaS vendor becomes a tool call, the per-seat licensing model that powers Salesforce, ServiceNow, and Workday starts looking structurally soft. The human cost of the pivot is visible on r/googlecloud, where a Xoogler-run LLM classifier found that 89% of Next '26's 1,052 sessions are AI-focused — only 119 are not. Practitioners are asking, in u/netcommah's phrasing, whether the event has become 'Gemini Next' at the expense of the boring infrastructure work (IAM, networking, GKE tail latency) enterprises actually need. The discontent is real, but it's also the sound of a conference catching up to a capital allocation that has already chosen a side.