{"id":89845,"date":"2026-06-29T20:17:11","date_gmt":"2026-06-29T20:17:11","guid":{"rendered":"https:\/\/www.europesays.com\/ai\/89845\/"},"modified":"2026-06-29T20:17:11","modified_gmt":"2026-06-29T20:17:11","slug":"meta-was-running-on-googles-ai-until-google-said-no-2","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ai\/89845\/","title":{"rendered":"Meta Was Running on Google\u2019s AI \u2013 Until Google Said No"},"content":{"rendered":"

\"Image:<\/a> Image: Gadget Review <\/p>\n

Behind Meta’s open-source AI announcements<\/a>, a quieter story was unfolding. Customer service, advertiser chatbots, scam detection, content moderation, internal coding tools \u2014 all running, at least partly, on Google’s Gemini models. Then around March 2026, according to the Financial Times, Google told Meta it couldn’t supply the compute Meta wanted. The AI self-sufficiency narrative cracked like a phone screen on day one. <\/p>\n

When Your Rival’s AI Keeps the Lights On <\/p>\n

Meta’s internal AI stack relied heavily on Google’s Gemini \u2014 and the dependency ran deeper than anyone outside the company knew. <\/p>\n

The scope of Meta’s Gemini dependency<\/a> is striking. Sources told the Financial Times that Gemini was chosen because it was<\/a> “performing better than Meta’s own models” for specific internal tasks. Meta also ran Anthropic’s Claude<\/a> alongside Gemini and Llama \u2014 hedging bets across providers rather than committing to a single external source. <\/p>\n

Here’s what the reporting reveals: <\/p>\n

Gemini powered customer service, ad tools, coding assistance, and harmful content takedowns across Meta’s platforms <\/p>\n

Google imposed capacity limits around March 2026 after Meta requested more compute than available <\/p>\n

Meta’s demand was unusually high compared to other Google Cloud customers <\/p>\n

Employees were told to conserve “AI tokens” \u2014 the units measuring how much model capacity each request consumes <\/p>\n

Meta began shifting workloads to Muse Spark, its own internal model built for content moderation <\/p>\n

The Token Wall Nobody Talked About <\/p>\n

Global AI compute demand is now growing faster than even the largest infrastructure providers can build to meet it. <\/p>\n

This isn’t Google punishing Meta. It’s structural. Google Cloud<\/a>‘s AI backlog now exceeds $460 billion<\/a>, according to Alphabet’s recent results. Its models process over 16 billion tokens per minute \u2014 up 60% quarter-over-quarter. Even after enormous data center investment, demand is outrunning supply. It’s the GPU shortage during the crypto boom, except now the scarce resource is inference capacity for models that half the Fortune 500 wants running simultaneously. <\/p>\n

Meta’s response has been swift \u2014 possibly forced. The company is investing up to $600 billion<\/a> in US data center capacity through 2028, building custom MTIA chips with Broadcom. This mirrors the ambition behind the Stargate Project<\/a>, as the race to control AI infrastructure accelerates across the industry. Separately, per CNBC, Meta is replacing third-party human moderation vendors like Accenture and Concentrix with AI systems. Muse Spark is absorbing moderation duties that Gemini once handled. <\/p>\n

The uncomfortable reality: “AI-native” is doing heavy lifting as a marketing term. Behind the keynotes, the biggest platforms are buying critical AI capacity from the same companies they’re racing against. Meta builds<\/a> toward self-sufficiency, but Meta’s token-rationing memo is this era’s equivalent of discovering your favorite restaurant sources its signature bread from the shop next door. What happens next depends entirely on who controls the ovens \u2014 and right now, that list is very short. <\/p>\n

From the coolest cars to the must-have gadgets, GadgetReview’s daily newsletter keeps you in the know. Subscribe – it’s fun, fast, and free<\/a>. <\/p>\n","protected":false},"excerpt":{"rendered":"Image: Gadget Review Behind Meta’s open-source AI announcements, a quieter story was unfolding. Customer service, advertiser chatbots, scam…\n","protected":false},"author":2,"featured_media":89846,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[5029,2408,132,2194,1430,1122],"class_list":["post-89845","post","type-post","status-publish","format-standard","has-post-thumbnail","category-google","tag-content-moderation","tag-gemini","tag-google","tag-google-cloud","tag-google-gemini","tag-meta"],"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/89845","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=89845"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/89845\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/89846"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=89845"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=89845"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=89845"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}