Gemma 4 31B Just Made Half Your API Budget Obsolete

Google dropped Gemma 4 and it's not incremental. The 31B dense model ranks #3 on Arena AI with an ELO of 1,452, scores 85.2% on MMLU Pro, 89.2% on AIME 2026, and 80.0% on LiveCodeBench v6. It outperforms models 20x its size. Under Apache 2.0. At $0.20 per run.

Only Opus 4.6 and GPT-5.2 beat it. Let that sink in.

The ecosystem response has been immediate and broad. Google's AI Edge Gallery app hit #8 on the App Store productivity charts. It runs Gemma 4 models entirely on-device, no internet required, under 1.5GB of memory. A developer benchmarked the 26B MoE variant on a MacBook Pro M4 Pro running LM Studio's new headless CLI and got 51 tokens per second. That's usable. Someone built PokeClaw, a working app that uses Gemma 4 to autonomously control an Android phone. No server, no cloud, no API calls. Just a phone running a model that rivals frontier systems.

The technical explanation for why it punches this far above its weight comes down to per-layer embeddings, an architecture where the 26B MoE variant only activates 3.8B parameters per pass. It's a 448-upvote technical explainer on r/LocalLLaMA and the clearest community breakdown of how Google pulled this off.

Here's what I'd actually do this week: take your three most expensive API-dependent features, benchmark them against Gemma 4 running locally, and calculate the savings. If you're spending real money on Sonnet calls for tasks that don't require Opus-level reasoning, Gemma 4 at $0.20/run or free on local hardware might just be the answer. The economics have shifted. Not theoretically. Right now.