The Short Answer
In November 2026 Google, Chargebee and Neo4j each shipped one layer of agent governance: a gateway that polices agent traffic, an approval gate that holds agent actions for review, and a memory store for what agents learn. ibl.ai runs all three layers as one model-agnostic platform on your infrastructure, where you own all the code and the data, instead of renting them from three vendors.
Google put Agent Gateway for cross-cloud into Limited Preview on November 11. Neo4j released Relate the same day. Chargebee launched Arc on November 18.
None of the three is a model or a chatbot. Each is a control: what an agent may call, what it may commit, and what it remembers. That is the layer enterprises now have to decide where to put.
What did Google ship with Agent Gateway, and where does Envoy fit?
Google's release notes for November 11, 2026 extend Agent Gateway to CNCF-conformant Kubernetes clusters outside Google Cloud, naming Amazon EKS, Azure AKS, Red Hat OpenShift and bare-metal clusters.
Agents get verifiable identities, agents and MCP servers are registered in Google's Agent Registry, and their traffic is routed through local gateway proxies.
It is free during Limited Preview; connected products such as Model Armor, Cloud Logging and Cloud Trace bill at standard rates.
A day later, Agent Gateway for GKE entered Preview for clusters on GKE 1.37.2-gke.1042000 or higher, in europe-west1 and us-central1.
Envoy is the foundation, not the product name. At Next '26 Google described Agent Gateway as understanding the MCP and A2A protocols, and said its agent networking work is "built on an open foundation including Envoy and Kubernetes".
Google and Tetrate engineers set out the technical case on April 3, 2026 in Envoy: a future-ready foundation for agentic AI networking.
Envoy reads MCP and A2A message bodies, exposes tool and model names to RBAC and authorization filters, and can inject a user's delegated token so the agent never holds it.
Their example restricts an issue-triage agent to 3 read-only MCP tools on a server that exposes dozens. That is the gateway layer: a policy decision on every tool call, enforced at the wire.
What is Chargebee Arc, and why does it matter for agent governance?
Chargebee announced Arc on November 18, 2026 as "a new agentic platform that runs complete finance workflows as one connected, traceable thread." It opened for early access the same day.
Arc launched with 3 pre-built agents, for contract ingestion, receivables and revenue recognition, plus Agent Studio, a workspace for building custom agents on the same foundations.
The governance is in the commit step.
Per the release, "every action is shown, cited, and held for review before anything is committed," and human teams approve, edit or reject each proposal. Arc's own site promises "a complete record of every decision: what was done, who did it."
That is the approval-gate layer: an agent may prepare a revenue schedule or a collections reply, but a person commits it, and the record says who. The release names no price and no general-availability date.
What is Neo4j Relate, and what does it change about agent memory?
Neo4j released Relate on November 11, 2026 as "an AI-native, open source, in-memory and in-process embedded database," built in Rust and released under the Apache 2.0 license.
In Neo4j's words, "a single Cypher statement can search by vector similarity and execute graph traversals simultaneously." Reads are sub-millisecond in memory, with an optional fsync'd write-ahead log for durable stores.
Neo4j's launch post says Relate runs as a library, a CLI or a WebAssembly build with no server, runs more than 30,000 test scenarios for openCypher, Cypher 25 and GQL, and can serve a database to agents as MCP tools.
That is the memory layer: agents store what they learn as connected facts rather than loose text, so the relationship between a customer, a contract and an exception survives the session.
Relate is the one launch of the three you can already own outright. It is open source and embedded, so it runs wherever your agents run.
What do an agent gateway, an approval gate and an agent memory store have in common?
All three are the governance layer around an AI agent, and each decides something the model does not. The table sets the three November launches side by side.
| Layer | November 2026 launch | What it governs | Where the rules and records live |
|---|---|---|---|
| Gateway | Google Agent Gateway for cross-cloud (Limited Preview, Nov 11) | Which models, MCP tools and agents an agent may call, under which identity | Agents and MCP servers registered in Google's Agent Registry; free in preview, logging and Model Armor billed |
| Approval gate | Chargebee Arc (early access, Nov 18) | What a finance agent may commit: each action shown, cited and held for review | Chargebee's platform; no price or GA date published |
| Memory | Neo4j Relate (open source, Nov 11) | What an agent knows and how facts connect, in graph plus vector form | Wherever you embed it; Apache 2.0 |
| All three, one stack | ibl.ai: Agentic Router, Agentic OS, Agentic Ontology | Per-user tokens and roles, spend caps, human approval steps, per-user memory, certified tools, audit logs | Your infrastructure; you own all the code and the data |
The pattern matters more than any single product. The model is becoming the interchangeable part, and the controls around it are becoming the system of record for how your agents behave.
Should an enterprise rent the agent governance layer or own it?
An enterprise should own the agent governance layer, because that layer holds the policies, the memory and the audit trail an examiner will ask for. Renting each piece separately puts those records in as many places as you have vendors.
Assemble the three November launches as sold and a single agent's rules sit in one vendor's registry, its approvals in a second vendor's application, and its memory in a database you embedded yourself.
Each is reasonable alone. Together they give you three policy models and three audit formats.
The gateway is the clearest case. Google's cross-cloud preview reaches into EKS, AKS and OpenShift, but the agents it governs are registered in Google's Agent Registry. Your agents can run on any cloud while their policy is held on one.
None of that makes the launches wrong. Identity per agent, deny-by-default tool access, a human approval before anything is committed, and memory as connected facts are exactly the controls to want. The question is only whose infrastructure holds them.
How does ibl.ai run the agent gateway, memory and audit layers on infrastructure you own?
ibl.ai builds the three layers into one platform you deploy in your own cloud, on-premise or air-gapped, model-agnostic across any LLM. You own all the code and the data, under a perpetual license.
The gateway. Agentic Router is one API key for 45 providers and 316 chat models (as of November 6, 2026) and 1,000+ MCP servers. Calls authenticate per user, with each person's own token and role, or server to server with a tenant-scoped key.
Spend caps apply at three scopes, the organization, one agent, and one person on one agent, and enforcement is server-side, so a runaway script stops at the cap. Cost is broken down per call.
The memory. Agentic OS connects your systems of record over an MCP-based interoperability layer and assembles a secure per-user memory, with field-level permissions, PII redaction, RBAC, audit logs and prompt and response archives.
The approval gate. Agentic OS workflows lay a multi-step agent run out as a graph, and a User approval node holds the run until a person signs off. A Guardrails node screens output before it moves on.
The certified tools. Agentic Ontology, open source under the MIT license, has your people certify the business terms agents call. A certified term becomes a tool with a fixed definition and fixed SQL, so an agent picks the right one and cannot widen it.
1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University. ibl.ai is family-owned and operated from New York, NY, and our team stays on as a long-term partner, shipping updates and new agents after deployment.
For the same thesis applied to Broadcom's per-tool-call authorization, see Agent Governance Moved Into Infrastructure.
Related: AI Agent Governance: Managing Autonomous AI Systems Responsibly