Detector Catalogue
Active detector counts per provider, and the six detection layers they fall into.
Active detectors by provider
| Provider | Active detectors |
|---|---|
| AWS | 102 |
| Azure | 73 |
| GCP | 59 |
| Oracle Cloud (OCI) | 38 |
| Multi-cloud | 23 |
| Kubernetes | 14 |
| Total | 309 |
What 'active' means
An active detector is a rule backed by real detection logic that produces findings. 309 is the figure to use in any assessment of detector depth.
The platform publishes this number live at its public detection coverage page — computed from the running rule registry rather than typed into marketing copy, so it cannot silently go stale.
The six detection layers
Detection is layered. Each layer requires progressively more from your connection, and produces progressively stronger evidence.
Evidence attached to findings
Detectors backed by measured telemetry attach the daily utilisation series they measured to the finding — rendered as a sparkline with p95, average, minimum, and maximum.
A resource owner can check the recommendation against their own dashboards instead of taking it on faith.
Optimization reports what share of identified savings is backed by this measured evidence rather than heuristics alone.