What is an AI control plane, and how does it differ from an AI gateway?
An AI gateway sees the call to the model. An AI control plane governs the agent: owners, approvals, budgets and the record. Which one you need.
- Topic
- Control plane
- Product
- Novie Control
- Format
- Guide
- Reading time
- 3 min
An AI gateway sits between applications and model providers and manages the call to the model: routing, keys, rate limits, caching and cost per request. An AI control plane governs what AI does across the organisation: which agents exist, who owns them, what each is approved to reach and spend, and a record of every action. A gateway sees the request to the model. A control plane sees the agent, its permissions and its owner.
Where the terms come from
Both are borrowed from networking and cloud infrastructure. A gateway is a point traffic passes through. A control plane is the layer that decides policy, as distinct from the data plane that carries the traffic. Applied to AI, the gateway is the path of the call, and the control plane is the set of rules and records about who may make which calls, for what, at what cost.
What an AI gateway does
- Routes each request to a model and provider, with failover when one is down.
- Holds the provider keys, so applications do not.
- Applies rate limits and, in some cases, content filters.
- Caches repeated requests.
- Records tokens and cost per request.
What an AI control plane does
- Keeps the inventory: every agent, its owner, its model and tools, its data and systems.
- Holds the approvals: the scope each agent was approved for, by whom, until when.
- Sets and enforces budgets: caps by organisation, team, project and agent, holding before spend is committed.
- Records actions: what each agent did, in which system, on whose authority.
- Brings approvals back for review when an agent's model, tools or reach change.
The difference that matters: the enforcement point
A gateway can see that a call went to a model and what it cost. It cannot see that the answer was then used to change a customer record, approve a refund or send an email, because those actions happen in other systems, through other tools. A control plane is built around the agent rather than the call, so its question is whether this agent was allowed to take this action, and who answers for it.
That is why the two are often used together. The gateway is a good place to enforce a budget, because every call passes through it. The control plane is where the budget, the owner and the approval are defined, and where the record of what the agent did is kept.
Which one you need
- A gateway alone fits an organisation calling models from a few applications its engineers own, where the question is cost and reliability per request.
- A control plane is needed once agents act on the organisation's behalf, more than one team builds them, and someone has to answer to a board, an auditor or a regulator for what they did.
- Most organisations running agents in production need both: a path every call takes, and a layer that says who may take it.
The numbers say most are now in the second group. In KPMG's Q2 2026 AI Pulse Survey, 53 percent of large US enterprises had AI agents deployed, and Deloitte's State of AI in the Enterprise 2026 found 21 percent have a mature governance model for them.
How Novie Control does it
Novie Control is live. Every dollar visible. Every budget governed. Every call optimised. Every agent governed. It sits in the path the calls take and governs the agents behind them. Every AI dollar is traced to the team, the project and the owner at the moment it is spent. Caps hold before spend is committed, with a named human on every increase. Each call is routed to the model that should take it, with failover when a provider stumbles. Every agent carries a named owner, an approval trail and a full audit trail.