Google Pitched Openness. Now Its Building the Walls.
The travel demo was the showroom. The real news was in the protocol numbers.
When Google Cloud CEO Thomas Kurian took the stage at Next 26 in Las Vegas last week, the company trotted out Virgin Voyages as its proof-of-concept: AI agents handling cruise booking workflows, real-time itinerary changes, dynamic pricing queries. Clean demo. Travel industry credentials established. Move along.
Except the number that should have gotten attention was 150 the count of organizations now running Googles Agent-to-Agent (A2A) protocol in production environments, up from 50 when the spec launched less than a year ago. AWS, Microsoft, Salesforce, SAP, ServiceNow, IBM, and Cisco are all listed as supporters. The Linux Foundation hosts the spec. (The Next Web)
On its face, A2A is Googles answer to Anthropics Model Context Protocol a competing attempt to define how AI agents discover each other, negotiate tasks, and hand off work across organizational boundaries. Google positioned it as an open alternative, a way for enterprises to avoid locking into a single vendors agent framework. Use Claude here, Gemini there, a homegrown model in the corner A2A would be the common language they all spoke.
Except language doesnt run on goodwill alone. And the architecture Google announced at Next 26 suggests the company has a preferred destination for all that interoperability.
Last year, Kurians pitch was openness: Google would help enterprises use whatever AI models worked best, including competitors. The message was pragmatic neutrality. Why not Google? was the question; the answer was that Google would let you bring your own models. (Reuters)
This year, Vertex AI is gone as a standalone product. All Vertex AI services and roadmap items now live inside the Gemini Enterprise Agent Platform. The agent runtime, memory bank, agent identity system, agent registry, and agent gateway are all Google infrastructure. The company is no longer selling pick-and-choose developer tooling its selling a destination. (Google Cloud Blog)
The Knowledge Catalog is the part that should make Salesforce, SAP, and ServiceNow uncomfortable. Googles new data architecture reaches into competitor platforms and ingests their data as context for Googles reasoning engine. Salesforce Data360, SAP, ServiceNow, and Workday are named as data sources that feed Googles AI. Googles framing: these platforms are input providers. Googles reasoning layer is the brain. (DIGI)
Michael Gerstenhaber, whom Google hired from Anthropic last year, described the governance problem at a press Q&A in terms that illustrated exactly why this matters. There are two kinds of agents in an enterprise interaction: the agent working on behalf of a user say, an employees assistant and the agent representing a data provider, like ServiceNows agent handling ticket queries. When the users agent queries ServiceNows agent, both sides need independent audit trails. The users admin needs to know what data was accessed. ServiceNows admin needs to verify the query was legitimate. Both traces must exist. (Reuters)
Googles Agent Gateway, Gerstenhaber explained, handles the monitoring on the user side. ServiceNow handles its own side. But heres the unasked question: who watches the gap between them?
ServiceNow would argue it does. ServiceNow built Agentforce specifically to own the governance layer for customer-facing agentic workflows. Salesforce has Agentforce. Microsoft has its own agent governance story. None of these companies is going to quietly accept being the data-providing satellite in someone elses solar system.
This is the governance tangle Google is asking enterprises to buy into. And its why the 150-organization A2A figure is the number to watch not the Virgin Voyages demo. (Linux Foundation)
The 150 includes AWS and Microsoft. If both hyperscalers are running A2A in production and both have integrated it into Azure AI Foundry and Amazon Bedrock AgentCore Runtime respectively, then A2A has genuinely become a common fabric. Every agent built on any major cloud can talk to any other. Thats a real interoperability layer, and its worth covering. (The Next Web)
But the open question the one Google hasnt answered is who owns the hub when everyones talking. Googles Agent Platform is the obvious integration point for any enterprise that wants to centralize agent management. The company that manages the interoperability layer captures the most value from it. Kurian called the platform "the Android of the agentic era." Android won by being the connective tissue that hardware, apps, and users needed at a moment when the market was fragmented. Google is making the same argument for enterprise AI.
Whether it holds depends on how much enterprises want Google as the operating system of their AI workforce and how much the ServiceNows and Salesforces of the world are willing to let that happen. (CIO)
Sundar Pichai gave a sense of the stakes. Alphabet is investing $175 billion to $185 billion in total capital expenditures this year, up from $31 billion in 2022. Thats nearly a six-times increase in four years, with over half going to cloud infrastructure. Alphabet is not hedging. Its betting that enterprises will consolidate around a single stack for chips, models, data, and governance and that Googles full-stack argument will be the one that lands. (DIGI)
The 93% figure from diginomicas research is instructive here: most organizations are using AI in some form, but fewer than 60% report achieving better than a 50% success rate with their implementations. The gap between experimentation and production is real, and its where every cloud vendor is competing. Google says its unified platform closes that gap. The question is whether enterprises believe it and whether their existing vendors let them act on that belief. (DIGI)
The travel demo will be forgotten. The protocol numbers wont be.