How integrations work
Integrations connect third-party platforms to QuilrAI. Some bring AI usage, inventory, and compliance data into Quilr; others send Quilr activity, findings, and alerts from Quilr to your security and operations tools.
Availability
Every integration below is available. Most are set up from a card in Settings › Integrations › Library; a few use a dedicated screen.
Installed and Library
The Integrations page has two tabs:
Use the search box (providers, types, and capabilities) or the Capability filter to narrow either list.
Each card shows the provider and vendor, a status badge, a short description, capability chips, and a category with its direction, for example "Cloud agent platform · Into Quilr" or "Observability · From Quilr".
Capabilities and direction
Install, manage, and uninstall
- Open the Library tab and click Install on a card.
- Follow the setup steps in the drawer. Each integration's page lists its own fields and credentials. The steps depend on the integration: credentials or a service principal, which scopes or subscriptions to monitor, and which capabilities (data flows) to enable.
- The integration moves to Installed.
On an installed card:
- Manage or Configure reopens the setup drawer to change credentials, scopes, or capabilities.
- Uninstall removes the integration from the tenant.
Credentials and configuration are encrypted and stored for the tenant. Secrets are never shown again after you save them.
To stop showing an integration's data in the console without uninstalling it, use the Included in console toggle in Data sources. This changes visibility only; ingestion continues.
Available integrations
Pull AI usage and inventory
Send logs and alerts
Runtime guardrail integrations
TrueFoundry calls QuilrAI guardrails from the partner gateway. You set it up with an LLM Gateway app and in the partner product, not from the Integrations page. Microsoft Copilot Studio supports the same pattern for tool-execution checks, in addition to its inventory card.