Infra Ops
Estate inventory, topology, drift, tagging, ownership — the foundation everything else builds on.
What Infra Ops in Escher covers
| Capability | Example question |
|---|---|
| Inventory | "What's running in prod?" |
| Topology | "Show the dependency graph for the checkout service." |
| Drift detection | "What's drifted from our IaC since last week?" |
| Tagging compliance | "Which resources are missing required tags?" |
| Ownership mapping | "Who owns each resource in prod?" |
| Change tracking | "What was added / removed / modified in the last 24 hours?" |
Sample answers
"What's running in prod across all clouds?"
Returns a unified inventory: compute, storage, networking, identity, data — across AWS, Azure, and GCP. With totals, costs, ownership tags, and risk flags.
"What changed in production overnight?"
Returns a diff Canvas: new resources, removed resources, configuration changes — ranked by risk and grouped by responsible team or deploy.
"Show every resource that doesn't match our naming convention."
Returns a hygiene report — useful for cost allocation, ownership tracking, and audit prep.
Why Infra Ops matters even when nothing's broken
A clean estate is the foundation for everything else Escher does. Bad tags lead to bad cost attribution. Drift leads to silent compliance failures. Unclear ownership leads to slow incident response.
Running an Infra Ops audit weekly takes 10 minutes with Escher and saves hours per incident.
Tips
TIP
Ask for a hygiene report. "Show our top hygiene gaps in production" surfaces tag drift, naming inconsistencies, and ownership gaps in one Canvas.
TIP
Diff before deploys. Asking "what changed?" before a major change is a cheap way to catch unexpected drift.