Why an AI control plane sits above the gateway
Gateways matter. They are just not the whole problem. Once a team needs authorization, budget enforcement, and audit evidence before execution, it is shopping for a control plane, not only a gateway.
This distinction matters because buyers often start with gateway language even when their real pain is cost control, policy enforcement, or compliance evidence. The category is not wrong. It is incomplete.
What gateways do well
- provider abstraction and traffic steering
- rate limiting, retries, and transport-level reliability concerns
- credential handling and request normalization
- centralized ingress for teams using multiple model providers
What gateways miss
A gateway can move and shape traffic. That does not automatically make it the decision boundary. Teams run into trouble when they assume routing and logging are enough to answer policy, cost, and audit questions later.
- whether the request should run at all
- what budget state applied before spend landed
- how the decision becomes a durable audit artifact
- how later evidence is verified instead of merely collected
Why the permit primitive matters
Keel uses the permit as the canonical decision seam. That changes the architecture. The decision is not buried inside middleware behavior or reconstructed from logs later. It exists as its own artifact before execution.
| Question | AI control plane | AI gateway |
|---|---|---|
| Primary unit | Permit / decision artifact | Gatewayed request path |
| Main job | Authorize, constrain, and prove | Route, proxy, and normalize |
| Cost posture | Pre-execution deny/throttle/constraint | Usually downstream alerts or add-on logic |
| Audit posture | Decision-linked evidence and exports | Logs plus surrounding stack |
Why evidence depth changes the buying decision
The difference becomes commercial when the conversation shifts from engineering convenience to organizational proof. A gateway may help the team ship faster. A control plane is what lets the team prove later why a request was allowed, denied, or constrained.
Cost opens the conversation
Buyers notice the missing control boundary first when a bill spikes.
Evidence closes the deal
Buyers feel the category difference most clearly when procurement, legal, or auditors ask for something a log stream cannot cleanly provide.
When teams still need both layers
This is not an argument that gateways are unnecessary. Many teams will want both. The gateway handles transport and provider access. The control plane handles authorization and proof. The mistake is treating the lower layer as if it already solved the higher one.