Plans decide which connectors are on.
Three plans set the default bundle. A platform admin can grant or revoke a single connector for your tenant, and free add-ons are yours to switch on.
Pick the posture. The connectors follow.
Each plan answers a different question: what exists, who is told, and what you can stop.
Visibility only
Why choose it
You want a complete AI inventory and a coverage score first, with no change to any machine or workflow.
What it includes
Everything observe-only: connectors across cloud, SaaS, storage, data platforms, vector databases, code, Kubernetes, endpoint security, network and IoT (private-network families need a switch, below), plus the AI runtime stack, compliance mapping, ownership, the risk register and free Slack and Teams alerts.
Outcome
You see what AI exists and where you are blind, and you decide the next step with evidence.
Discover, and warn when policy is broken
Why choose it
You have an approved-AI policy and want people and owners alerted when it is broken, still without blocking anything.
What it includes
Everything in Discover, a warn response posture, AI red-team and change-risk analysis, and more connectors (LLM gateways, web proxy and DNS log sources, Palo Alto firewall logs and NetFlow/IPFIX), plus Jira, ServiceNow and SIEM export, and the same free Slack and Teams alerts.
Outcome
Violations reach the owning team through alerts and tickets, and gateway and proxy evidence shows AI use on machines with no sensor.
Every capability, with enforcement
Why choose it
You want to act as well as see: block or quarantine rogue AI and enforce content policy, under audit.
What it includes
All 72 connectors in every family plus the 7 mobile-device collectors, all free add-ons switched on, the content-DLP policy engine, SSO and SCIM, ownership sync and endpoint enforcement (generally available on Linux). Enforcement is opt-in and every action is audited.
Outcome
Discovery, evidence and response sit in one place, and the actions you take are recorded for auditors.
What each plan includes, family by family.
A check mark means the family is included in that plan.
| Connector family | Discover | Discover + Warn | Discover + Warn + Block | Free add-ons (you opt in) |
|---|---|---|---|---|
| Cloud accountsFinds the AI services, roles and findings inside your AWS, Azure, Google Cloud and Oracle accounts, including AWS Organization, serverless functions and AWS Config. | ✓ | ✓ | ✓ | None |
| SaaS-embedded AIFinds AI apps and AI note-takers that users authorized inside Microsoft 365, Google Workspace, Slack, Zoom and GitHub. | ✓ | ✓ | ✓ | GitHub Copilot (org seats and policy), Slack (AI apps) |
| Identity providersLists the service principals, API tokens and AI sign-ins that agents use as their identity. | ✓ | ✓ | ✓ | Microsoft Entra ID (service principals, credentials), Okta (AI apps, service apps, API tokens) |
| Mobile devicesReads installed AI apps on managed phones and tablets from your MDM, plus sign-in, cloud-app and DNS evidence. | None | None | ✓ | None |
| LLM gateways and AI proxiesReads gateway routes, keys, budgets and guardrails, and accepts OpenTelemetry GenAI traces. | None | ✓ | ✓ | None |
| Web proxy, SWG and DNS logsTurns proxy, secure web gateway and DNS logs into per-user AI usage, including for machines with no sensor. | None | ✓ | ✓ | None |
| FirewallsReads firewall logs and device lists so hosts behind the firewall are counted and their AI traffic is seen. | ✓ | ✓ | ✓ | None |
| Network devices and NACBuilds the device census from controllers, NAC, SNMP, DHCP leases and NetFlow, and flags AI-capable devices. | ✓ | ✓ | ✓ | DHCP leases (ISC / Kea / Windows) |
| IoT and OT platformsReads the device inventory your IoT and OT platform already keeps and flags devices that could carry AI. | ✓ | ✓ | ✓ | None |
| Cloud storageFlags public or unprotected buckets that hold AI datasets, model weights or vector indexes. | ✓ | ✓ | ✓ | None |
| NAS and storage appliancesFlags AI-named shares and volumes on NetApp, Pure Storage, Dell and Synology that are open or unencrypted. | ✓ | ✓ | ✓ | None |
| Data platformsShows which models and AI endpoints your warehouses and lakehouses serve, and who may query them. | ✓ | ✓ | ✓ | None |
| Vector databasesLists vector stores and flags servers that accept unauthenticated requests or plain HTTP. | ✓ | ✓ | ✓ | None |
| Source control and CI/CDFinds AI libraries, provider credentials in pipelines and committed agent configs across GitHub, GitLab, Bitbucket, Azure DevOps and Jenkins. | ✓ | ✓ | ✓ | None |
| EDR and XDRLists endpoints your EDR manages that have no sensor as known AI-blind, and turns AI-related Defender alerts into findings. | ✓ | ✓ | ✓ | None |
| Kubernetes (agentless)Reads clusters with a read-only service account to find model servers, notebooks and GPU workloads. | ✓ | ✓ | ✓ | None |
| Generic import and webhooksImports CMDB or CSV asset lists and accepts webhooks, so any inventory can count toward coverage. | None | None | ✓ | Asset list import (CSV / JSON), Generic REST (JSON) poller, Generic webhook / event receiver |
Default bundles. A platform admin can change them for a tenant. The mobile connectors are one licensed feature, MDM import.
Four layers, from plan to private network.
Each layer is explicit and recorded, so you can always see why a connector is on or off.
1 · Plan: the plan sets the bundle
Your plan includes a default set of connector families. Sargha sets it when your tenant is created.
2 · Grant: one connector at a time
A platform admin can grant or revoke a single connector for your tenant, with an end date and a note. A revoke always wins.
3 · Opt in: free add-ons are yours to switch on
Free add-ons are licensed on every plan but stay off until you opt in: GitHub Copilot (org seats and policy), Slack (AI apps), Microsoft Entra ID (service principals, credentials), Okta (AI apps, service apps, API tokens), DHCP leases (ISC / Kea / Windows), Asset list import (CSV / JSON), Generic REST (JSON) poller, Generic webhook / event receiver, plus Slack and Teams alerts.
4 · Reach: private networks need a switch
Connectors that read gear on private networks (network, firewall, NAS, IoT and OT) also need private-network access enabled for your tenant. It is off by default.
Two things worth knowing before you choose.
A lapse never deletes your data, and price is a separate conversation.
History stays, connectors pause
A connector whose license ends is disabled automatically. Its data, history and encrypted credentials are kept, and it resumes when it is licensed again.
Commercial terms are on the pricing page
This page explains what each plan switches on. Editions, price and support terms are on Pricing and are confirmed on a scoping call.
Not sure which plan fits?
Tell us your clouds, gateways, proxies and device platforms. We map each to a connector and recommend a plan.