Google positions Gemini 4 Argon for long-horizon agentic work
Google has launched Gemini 4 Argon, a new flagship AI model aimed at complex enterprise and software-development workloads, pairing claims of stronger coding performance and advanced reasoning with an introductory pricing model that doubles after November 30.
Google has launched Gemini 4 Argon, a new flagship AI model aimed at complex enterprise and software-development workloads, pairing claims of stronger coding performance and advanced reasoning with an introductory pricing model that doubles after November 30.
The model “excels at deep work in complex, real-world tasks,” Koray Kavukcuoglu, senior vice president of Google DeepMind and chief AI architect at Google, wrote in a blog post.
Google said that its engineers used Argon to refactor a legacy folder of about six million lines within Chromium’s 40 million-line codebase, finishing in weeks rather than months. Teams using Argon in Antigravity increased agentic code submissions by more than 35% and cut code rollbacks by nearly a third, the company said, without detailing how it measured either figure.
Argon is available through the Gemini API in AI Studio and on Google’s Gemini platform, and to Google AI Ultra subscribers in the Antigravity agentic development environment, the post added. In a separate developer blog post, Google said the model is “designed for those long-horizon workflows that require deep reasoning and structural precision.”
According to the post, Argon costs $2 per million input tokens and $10 per million output tokens during the introductory period, with cached input discounted 95%. A footnote in the post states the prices rise to $4 and $20, respectively, after November 30. The company said the model’s 1 million-token limit in the Gemini API is shared between input and output.
Sanchit Vir Gogia, chief analyst at Greyhound Research, said CIOs should budget at the higher rate from day one, because no enterprise evaluation, security review and procurement cycle finishes within the discount window. “A business case built on the launch rate is a business case built to be rewritten in seven weeks,” he said.
In context
- Topic: Cloud y Arquitectura — Nube pública, híbrida, costos y decisiones de infraestructura.
- Source: InfoWorld
- Published: 14/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
The cloud conversation moved from migrate everything to deciding what goes where. That maturity is a good sign, but it also makes the discussion harder: there is no single answer any more, it has to be argued case by case, and very few people have the numbers to do it.
What I look at in these announcements is portability. The more comfortable a platform is, the harder it usually is to leave, and that comfort gets paid for in negotiating power three years later, exactly when renewal comes up and there is no credible alternative left.
What usually goes wrong
What I see fail most is the literal migration. The system gets moved exactly as it was, nothing redesigned, and you end up paying hourly for what used to be paid once. It works the same, costs more, and two years later somebody asks why it was done. Lift and shift is not modernising.
What to watch
- Where the data physically sits and what local regulation demands about that.
- What happens when the provider has an outage, because it will, and what keeps running meanwhile.
- Three-year total cost with real growth, not the first-year promotion.
How I read this entry
What I would install alongside any move to the cloud is the discipline of switching things off. Tag everything by owner, review monthly what is running unused, and give somebody the authority to turn it off. Without that, waste eats the promised savings within two years.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
