Introducing Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash Cyber
Google DeepMind is introducing three new Gemini models: Gemini 3.6 Flash, Gemini 3.5 Flash-Lite, and Gemini 3.5 Flash Cyber. The release expands the Gemini…
By Dillip Chowdary • Aug 04, 2026 • Source: Google DeepMind
Google DeepMind is introducing three new Gemini models: Gemini 3.6 Flash, Gemini 3.5 Flash-Lite, and Gemini 3.5 Flash Cyber. The release expands the Gemini lineup with a 3.6-generation Flash model alongside two 3.5 Flash variants, one Lite and one Cyber, rather than a single new flagship.
The naming points to a split product stack. Gemini 3.6 Flash sits on a newer Flash generation; Gemini 3.5 Flash-Lite and Gemini 3.5 Flash Cyber stay on the 3.5 Flash line but target different roles—Lite as a lighter tier, Cyber as a specialized Cyber-branded variant. Exact architecture, latency, and quality numbers were not included in the announcement summary, so capability claims should wait for DeepMind’s full model cards and API docs.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
For engineers and builders, the practical issue is which model to route to for which job. A 3.6 Flash option and two 3.5 Flash options mean product teams may need clear routing rules—default throughput path, cost- or footprint-sensitive path, and any Cyber-restricted path—before swapping defaults in production.
In market terms, Google DeepMind is filling the mid-stack Gemini Flash family instead of only shipping one headline model. Multiple Flash SKUs force competitors and customers to compare within Google’s own ladder, not only against outside providers, and make pricing, rate limits, and feature parity across the three models the real comparison surface.
What to watch next is DeepMind’s official documentation for each model: supported modalities, context limits, safety and usage policy for Flash Cyber, and how Flash-Lite is positioned relative to 3.6 Flash on quality and cost. Until those details land, treat the three names as product slots and validate each against your own evals before changing production routing.
Advertisement