Google introduced native PyTorch backends for vLLM and SGLang on TPUs, reporting that Meta is already using SGLang-TorchTPU in production.
Google announced native PyTorch backends for the vLLM and SGLang inference engines on its Tensor Processing Units, aiming to make TPU deployment easier for developers who already build and serve models with PyTorch. The launch includes TorchTPU, a backend that lets PyTorch run directly on TPU hardware, alongside TPU versions of both inference engines.
The announcement’s most significant deployment signal came from Meta. Google said SGLang-TorchTPU is running in production at Meta, and quoted Meta’s PyTorch-TPU lead describing the collaboration among Meta, Google and SGLang developer RadixArk. Meta’s statement said the stack enables PyTorch workloads to run on Google TPUs. The announcement did not disclose the scale of Meta’s deployment, the workloads involved, or whether the hardware is located in Meta facilities or accessed through a cloud arrangement.
The software is designed to reduce the need to adapt model code or serving infrastructure when moving PyTorch workloads to TPUs. Google described support for production features including tool calling, structured output, multimodal inputs, long-context serving and distributing inference across multiple hosts. Both engines are open-source projects, and Google said it built the TPU integrations with the teams behind vLLM and SGLang.
Google also reported benchmark results for its Ironwood TPU, including a cost-per-million-tokens figure and performance results for agentic workloads. Those figures are company-reported benchmarks, not an independent comparison across identical production configurations.
For the AI infrastructure market, the announcement shows Google extending TPU support into software ecosystems widely used by model developers. Meta’s reported production use is a concrete example of TPU deployment beyond Google’s own services, but the public announcement provides no information on volume, costs, or any commercial hardware agreement. The new backends may lower migration friction; their longer-term impact will depend on performance, availability and operational experience at larger scale.
