Productivity first
Enterprise teams are shipping agents quickly. That starts as a productivity win. It becomes a liability when a bot can reach more than its job, when identity is a shared key, and when token cost shows up as a surprise instead of a workspace number.
Unscoped access is not a strategy. It is a finding you usually meet during an incident.
What the plane actually is
Kimss AI is the Secure Enterprise Agent Control Plane. It is not another wrapper around a chat box, and it does not host your models. Azure AI Foundry, or the endpoint you already pay for, keeps doing inference. Kimss governs the calls you route through the gateway.
On that path you get:
- A workspace identity on the call, instead of one key copied across repos.
- A kill switch that stops that agent at the gateway. Disable it, and routed access stops. The inventory row and the audit of what already happened stay.
- A gateway-verified record of the requests that passed the gate, including usage you can attribute to a workspace.
Developer includes that gateway path, identity, the kill switch, and 25,000 governed requests a month. At the cap the gateway returns 429. Authority Boundary, the Threat Intercepts screen, and Team & Access are paid. SSO and SCIM are Enterprise.
What it does not cover
Workspace isolation applies to traffic on the gateway. It is not a promise that two processes can never touch the same system if they never call Kimss. The kill switch does not reach a job that never hits the gateway. A self-reported row is inventory hygiene. It is not an Article 12 record. Gateway-verified means the call went through the gate.
Adapted from a LinkedIn note on 19 July 2026. Wording here follows the product we ship now.