Google caps Meta access to Gemini AI over compute capacity

The headline reads like a rivalry story, but the mechanism underneath is purely physical. Google did not refuse Meta - it told Meta around March that it simply could not provide all the Gemini capacity Meta wanted to buy ^[1]. That is a remarkable admission from the company with arguably the deepest chip supply in the industry. The constraint is infrastructure, not money: GPUs, memory, power, and data centers, as one strategy analysis put it, when even a trillion-dollar buyer gets rationed ^[3]. Sundar Pichai had already signaled this on the April earnings call, saying Google Cloud is compute-constrained in the near-term and that cloud revenue would have been higher had it been able to meet demand ^[4]. In other words, Google is leaving revenue on the table not because customers won't pay, but because there are not enough serving racks to sell.

Selling Gemini access is not like selling software licenses - every token a customer processes consumes real-time inference capacity on physical accelerators that can also be serving Google's own products. When aggregate demand exceeds the fleet, the provider has to allocate, and the largest single buyer is the most visible thing to throttle. Meta was reportedly among Google's largest AI customers, which is exactly why its exceptionally high demand made it the hardest-hit when Google began rationing ^[1]. The scale of the underlying growth explains the squeeze: Google Cloud's AI products grew roughly 800% year-over-year, API token processing hit 16 billion tokens per minute (up from 10 billion a quarter earlier), and backlog doubled to $462 billion ^[4]. Back in November, Google's own infrastructure team had warned staff it must double serving capacity every six months just to keep pace ^[5]- a treadmill that the Meta cap shows it is still losing ground on.

The cap did more than delay projects - it sharpened Meta's incentive to depend less on a competitor's cloud. Meta had leaned on Gemini for content moderation, scam detection, customer service, advertising tools, and software development, and is now shifting some of those workloads to its own Muse Spark model while investing in its own infrastructure ^[2]. Internally, the response was austerity: Meta encouraged staff to be more efficient with AI tokens, the units that measure usage ^[1]. There is an irony worth naming - Google was willing to sell its flagship model to a direct rival, and the relationship strained not over strategy but over supply. The demand-side context matters too: industry commentary has framed Meta's appetite for Gemini against setbacks in Meta's own model efforts, which is part of why it wanted so much external capacity in the first place.

Across social platforms the dominant read was that this confirms physical compute - chips, data centers, power - as the true bottleneck of the AI build-out, with the sharpest framing being that compute is the scarcest resource in AI, not corporate rivalry. Semiconductor-investor circles took it as bullish, expecting Google to raise capex in response. But the most interesting friction was a contrarian thread questioning whether AI 'demand' is even genuine, with skeptics arguing that auto-injected AI summaries and forced features inflate token usage, countered by others pointing to real, voluntary workloads. That tension - genuine demand versus manufactured demand - is the unresolved question lurking beneath every capacity-constraint story: if Google must double serving capacity every six months ^[5], it matters enormously whether that curve is being driven by users who want the product or by products that inject themselves.