Kimss for enterprise
The agent control plane for Azure-standardized enterprises: Entra SSO, optional SCIM (Scale and Enterprise), APIM GatewayLogs into Log Analytics, and a named kill switch on routed traffic. No laptop rollout. Inference stays on the endpoints you already own.
Identity & access
Work or school accounts in your Entra tenant. Multi-tenant SSO, admin consent, and role-aware workspaces.
Connected infrastructure
Vault your OpenAI-compatible endpoints. Inference stays on your provider bill; Kimss meters governed requests and estimated spend.
Kill-switch drill
Route one of your agents, see the inventory row, press the switch, see the deny. Same meeting: a one-shot Security Lab report on that routed agent. No IT project. Routed traffic only.
Audit-ready operations
Audit log of administrative actions and governed requests, with configurable retention. Optional APIM GatewayLogs to Azure Monitor / Log Analytics when enabled. Gateway-verified on routed traffic, not self-reported usage.
Procure Kimss on Microsoft Marketplace, then activate the subscription in the app. Kimss does not provision a hosted model runtime; connect your own endpoints under Connected Infrastructure. For sales-led onboarding, use Contact sales. See Identity & SSO, route your traffic, execution logs, and the workspace for governance operations. Confirm Azure consumption-commitment eligibility with your Microsoft AE; Kimss does not advertise MACC drawdown until Partner Center shows enrolled.
Enterprise FAQ
Kimss is the multi-tenant control plane enterprises place in front of their own model endpoints so identity, budgets, and agent APIs stay consistent across every workspace.
How does Kimss differ from buying a model provider alone?
Providers execute models. Kimss adds workspace identity, RBAC, kill switch, governed-request caps, and a stable developer API so product teams do not rebuild tenancy for every app.
How do we control AI spend?
Governed-request meters and FinOps estimated-spend views (labeled self-reported vs gateway-verified) give operators soft alerts and hard exhaustion policies before cost becomes an incident. Inference itself stays on your provider bill.
Where is the public API reference?
Use the public HTML reference at /docs/api_docs and the Python SDK / MCP guide at /docs/python_sdk_mcp. Interactive Swagger is not enabled on the production origin.
How do we start procurement?
Transactable Azure Marketplace SaaS (Production and Scale), self-serve at /pricing, or sales-led contracts via /app/enterprise/contact. Ask your Microsoft AE before promising committed-spend drawdown.
What is the kill-switch drill?
A meeting-length drill: point one agent at api.kimss.ai, watch the inventory row appear, press the named kill switch, see the deny. Optional one-shot Security Lab report on that same routed agent. Kimss does not scan laptops or run a continuous red-team lab.