Cloud Intelligence
Cloud Intelligence
Establish a read-only AWS or Azure inventory baseline, then retain deterministic drift and hygiene evidence for review.
Reader-only inventory and evidence; no automatic remediation. Azure VM utilization review runs only where eligible running VMs exist.
Capabilities
- AWS and Azure asset inventory through read-only customer authorization
- Deterministic inventory drift, hygiene and factual-posture evidence
- FinOps review candidates are evidence-led; AntOps does not resize or remediate cloud resources
Connect with least privilege
AWS uses a cross-account read-only role with an External ID and short-lived STS credentials. AntOps never requests access keys.
Azure uses a Reader-only Azure Lighthouse delegation and a certificate-authenticated managing identity. AntOps never stores customer Azure credentials.
Baseline, then focused evidence
The first inventory records a baseline. Later material differences create an event with focused before-and-after evidence; current inventory and observations remain available for review.
- 01Asset
- 02Monitor
- 03Observation
- 04Event
- 05Evidence
- 06Delivery
Illustrative evidence layout
FinOps is evidence-led
Cost-efficiency candidates, hygiene conditions and reliability trade-offs are deterministic review signals. Policy-based findings follow configured policies. Estimated savings stay unavailable unless authoritative cost evidence exists.
What AntOps never does automatically
AntOps does not change, resize, remediate or deploy customer cloud resources. Your team reviews the evidence and decides what happens next.
Use it in your workflow
Establish a baseline or submit a scoped request, then keep the current result, source-linked evidence and relevant change notifications in the workspace where your team works.