Google Joins Amazon's Attack On Nvidia's PyTorch Grip

Google released TorchTPU, its PyTorch fork for Tensor Processing Units, one day after Amazon's TorchNeuron -- a two-hyperscaler push against Nvidia's roughly 85% grip on the framework most AI apps use.

Google Joins Amazon's Attack On Nvidia's PyTorch Grip: key figures
ShareXLinkedInEmail

THE RUNDOWN

1

Google's TorchTPU lets existing PyTorch apps move to TPUs and Google Cloud via a config change, directly targeting the ~85% of AI apps built on PyTorch.

2

Amazon is submitting code upstream to decouple PyTorch from Nvidia-specific optimizations, a structural attack on switching costs, not just a one-off tool.

3

Meta created PyTorch in 2016 and handed it to the Linux Foundation in 2022; Google and Amazon are now shaping a framework they don't own toward their own silicon.

4

Developers won't abandon Nvidia just because switching got easier, making this a multi-year infrastructure bet, not an immediate share shift.

The VC Read

Value Add VC analysis

The tell is Amazon submitting code upstream to the main PyTorch project rather than just shipping its own fork -- that's an attempt to change the default, not just offer an alternative. Watch Nvidia's response at its next developer conference; a framework-level attack on CUDA lock-in is the one thing that's dented Nvidia's moat before, and AMD's ROCm effort never got this kind of coordinated two-hyperscaler push.

Analysis

Google released TorchTPU, an open-source version of PyTorch built for its own Tensor Processing Units, the company said Tuesday via a Google Cloud blog post covered by TechCrunch. The move comes one day after Amazon shipped its own PyTorch fork, TorchNeuron, which Pulse covered Monday as a direct challenge to Nvidia's roughly 85% grip on the framework most AI apps are built with.

What's new since that coverage: Google is now making the same kind of move, not just Amazon. TorchTPU lets existing PyTorch applications move to Google's TPUs and Google Cloud through a configuration change rather than a rewrite, and Google says it worked directly with Meta, Hugging Face, and the makers of vLLM and SGLang to keep compatibility with popular AI tooling intact. Google also launched a TPU agent suite to help developers migrate and debug that move, and updated LiteRT, its on-device AI runtime, to work better with PyTorch apps.

“What's new since that coverage: Google is now making the same kind of move, not just Amazon.”

Together, the two moves amount to a two-hyperscaler push against Nvidia's default position inside PyTorch, which Meta built in 2016 and handed to the Linux Foundation in 2022. Amazon's version goes further structurally: it's submitting code upstream to the main PyTorch project that decouples features from Nvidia-specific optimizations, an attempt to change the framework's defaults rather than just offer an alternative alongside it.

However, easier switching doesn't guarantee switching happens. Developers have built years of tooling, debugging habits and performance tuning around Nvidia's CUDA stack, and neither fork removes that inertia overnight -- AMD's ROCm effort has spent years trying to loosen Nvidia's grip with limited success. The real test is whether either hyperscaler's internal AI teams move meaningfully off Nvidia for their own workloads first; outside developers will likely follow proof, not announcements.

ShareXLinkedInEmail

Key Sources

1 source

Reported by TechCrunch · Analysis by Value Add Pulse.

← Back to Pulse

THE WIRE in your inbox— Tech, startup & VC news with The VC Read, a few times a week. Free to subscribe, no spam.

No spam, unsubscribe anytime. Sent via Substack · Privacy · or subscribe on Substack ↗