What changes for the organisation
You find out which AI services your organisation is already using, by department, before someone else does.
Maps which AI services your organisation already uses, and by whom.

What changes for the organisation
You find out which AI services your organisation is already using, by department, before someone else does.
How it works
It ingests your existing egress proxy and DNS logs alongside the M0 event store, resolves destinations against the signed catalog, and maintains a heuristic suspected-AI bucket for services the catalog does not yet know.
The mechanism, not the marketing. If a step below would not survive an engineer's scrutiny, it should not be on this page.
Operating path
The question that decides whether an observability tool is an instrument or a decoration.
The projection shows unsanctioned AI destinations up 40% week on week. The figure renders with its watermark and projection version attached.
By OU, the increase concentrates almost entirely in one department. Low-count suppression holds; no individual resolves.
Three of the top five destinations sit in the suspected-AI bucket — real traffic, LLM-shaped, matching no catalog entry. The dashboard says suspected, on the tile, not in a footnote.
One is a translation service with an LLM backend, adopted by the team without review. The other two are regional services not yet in the catalog.
The watermark had moved: a proxy connector that had been degraded for nine days recovered and backfilled. Roughly 28 points of the “increase” was newly-visible existing usage. Only 12 was growth.
The catalog is extended locally, policy scoped to the department, and that department moves from observe to warn.
What it came to
The interesting answer was that the number was partly an artefact — and the product said so itself. An inventory that cannot distinguish new usage from newly-visible usage will mislead you at exactly the moment you brief an executive.
The authority ladder. Green rungs are authoritative — a rule, a scanner, a sandbox, or a person. Blue is where the model contributes. Amber is where a human decides.
Pattern description over the inventory — which departments are converging on which services, and how that is trending.
It cannot see what proxy and DNS cannot see. Local and on-device models of the Ollama class are invisible to this telemetry; that gap is recorded, not papered over.
These surfaces are designed and reviewable in the console reference.
Phase 1.5. Freeze requires the first named proxy and DNS product/version targets, numeric capacity and projection-refresh SLOs, approved workforce-privacy defaults, and agreed metric definitions.