Google’s agent platform can’t canary behind its own gateway. Omnia can, and deploys to Google too.
Omnia gives you both at once: a stepped rollout behind the gateway, and policy on what a tool is called with. Google’s platform, formerly Vertex AI, has a simulation suite and a default-deny gateway, but on Agent Runtime the gateway and a canary can’t coexist.
The policy broker has sat beside the agent since its first version, and the canary carries on at its share of traffic. Every earlier version is still there to roll back to. docs
Changing an Agent Gateway binding archives every earlier revision, archiving is irreversible, and binding changes are only allowed while all traffic is on the latest revision. their docs
Policy that reads the arguments
A rule can allow transfer_funds under £500 to accounts the caller owns. CEL sees the call’s arguments and the caller’s identity, on any tool. docs enterprise
Gemini Enterprise Agent Platform: Access-policy conditions cover the tool name and annotation hints such as read-only or destructive, for MCP tools. Argument values aren’t an attribute. source
A rollout that decides for itself
The traffic split starts once the suite passes and widens as the metrics hold. If they slip, traffic goes back to the previous version. docs enterprise
Gemini Enterprise Agent Platform: Revisions and manual traffic splits are in preview. An eval gate, metric-gated promotion and automatic rollback aren’t documented. source
Telemetry into your own stack
At a glance
| Topic | Omnia | Gemini Enterprise Agent Platform, per its docs |
|---|---|---|
| Simulated users | yes Multi-turn, against real tools, adversarial included. docs | documented Personas, with virtualisedvirtualized tools and fault injection. source |
| Voice testing | yes Barge-in, overlapping speech and dead air. docs | not documented Not documented. source |
| Argument-level tool policy | yes A CEL rule on every call. docs enterprise | partly Tool name and hints only. source |
| Canary and policy together | yes Yes. docs enterprise | not documented Binding needs all traffic on the latest revision. source |
| End-user identity to tools | yes Carried through the agent to every call. docs | partly Three-legged OAuth for external tools, preview. source |
| Runs outside Google Cloud | yes Your cluster, AWS or Azure. docs | not documented Gateway on other clusters is coming soon. source |
Common questions
- Is this the same as Vertex AI Agent Builder?
- Google describes the Gemini Enterprise Agent Platform as the evolution of Vertex AI, and Agent Engine is now Agent Runtime.
- Can I use Omnia with Google Cloud?
- Yes. Omnia deploys a pack to Google’s agent runtime with one command, uses Gemini on Vertex natively, and runs its scenarios against the deployed agent.
Put your own agent through the gate.
Install Omnia in your cluster and run it free while you build.
Gemini Enterprise Agent Platform claims are from Google Cloud’s published documentation, checked 22 October 2026. Spot something out of date? Tell us.