Every logo here is something Kapālins connects to today.
Grouped by how each one connects: inline through the gateway, from audit logs, through identity, on the device, out to your SOC, and inside the tools people work in. Counts are read from the platform code, not typed.
AI providers, governed inline.
Applications call the gateway instead of the provider, using the OpenAI or Anthropic API format and a virtual key of their own. Policy Shield runs on every call, in and out.
How it connects: change the base URL and key · routing and failover across providers
Counted from the gateway’s provider listAudit-log sources.
What each platform’s own logs say about AI use: who used which AI feature, what was configured, and what changed. 13 are pulled on a schedule and 2 push to Kapālins by webhook.
How it connects: an admin API credential you grant, read on a schedule · or a webhook the platform pushes to
Counted from the ingestion runner and its webhooksCopilot, Entra, Azure and Teams.
Most enterprise AI arrives through Microsoft first. Kapālins reads Microsoft 365 Copilot audit and seat usage, checks SharePoint oversharing and sensitivity labels, routes Copilot Studio agents, finds Azure OpenAI deployments the gateway has never seen, and runs the Governed AI Workspace as a Teams tab.
How it connects: Microsoft Graph and Office 365 Management API with admin consent · Azure Resource Manager inventory · Entra for SCIM, SSO and grant discovery
Microsoft insights and the Copilot Studio recipeIdentity providers.
SCIM 2.0 keeps people and groups in step from all four. OAuth grants in Entra and Okta are matched against 31 AI apps, so an AI app someone connected with one click still shows up.
How it connects: SCIM 2.0 push from the directory · OIDC single sign-on · read-only grant sweep in Entra and Okta
SCIM from all four · grant discovery from Entra and OktaAI tools found on the device.
The sensor recognises 69 AI tools and 14 AI web domains. A sample of the coding agents and local models it finds is below, with the platforms the sensor runs on.
How it connects: an enrolled sensor checks in and reports what it finds · decisions come back from the same policy as the gateway
Counted from the device catalogueDesktop sensor for Windows and macOS · browser extension for Chrome, Edge and Firefox
SIEM and ITSM.
Findings, blocks and incidents are pushed to the tools your SOC already runs, in each tool’s own format, plus signed webhooks for anything else.
How it connects: Kapālins pushes to the destination you configure · nothing is pulled from your SIEM
Counted from the SIEM and ITSM formattersThe Governed AI Workspace, where people already work.
Chat, skills, assistants and projects inside Microsoft Teams, Office and Google Workspace, with the same Policy Shield as the gateway.
How it connects: a Teams tab · an Office task pane · a Google Workspace add-on
Connect what you already run.
Tell us which of these you use, and we will show what Kapālins reads from each.
Questions buyers ask.
Do I need to route all AI traffic through the gateway?
No. The gateway governs what you route through it. Audit-log connectors, identity grants and the device sensor cover the AI that never touches a gateway, such as Copilots and personal accounts.
How are audit-log sources connected?
Most are pulled from the platform’s admin API on a schedule, using credentials you grant. A few push events to Kapālins by webhook instead.
Where is the platform hosted?
Hosted in Australia. Our privacy policy explains how personal information is handled.