The question that stalls most cleanup work is not “how much does this cost?” but “what is this for?” Cost tools surface recommendations that ignore intent: a resource that looks oversized may be sized for high availability or disaster recovery on purpose, and a quiet one may be a shared platform service that half the company depends on. When nobody can say what a resource supports, the safe choice is to leave it alone, and the recommendations turn into alert fatigue.
Continuous inventory and topology gives Cloud Sleuth the context to answer that question. It is a living inventory with relationship context, kept in sync with your cloud accounts through read-only APIs.
How it works
- Normalized inventory. One consistent inventory across AWS, Azure, GCP and Kubernetes, designed to expand to more sources over time. The free local tool covers AWS and Azure; GCP and Kubernetes are part of Cloud Sleuth Cloud.
- Dependency and relationship graph. Attachments, network connections, IAM relationships, Kubernetes ownership and higher-level service mappings, so you can see how resources connect to each other and to the services they belong to.
- Interactive exploration. Search, filter and visualize resources with ownership, cost, utilization and policy status overlaid.
- Context for action. Before anything recommends deleting or rightsizing a resource, you see what it supports and who owns it.
- Resources that cannot be tagged. Resources that cannot be natively tagged are supported, not left out of the picture.
Why it matters
Inventory tools show topology, but they do not drive ownership or cost allocation. Cost tools show spend, but not what a resource is connected to. Cloud Sleuth brings the two together: the inventory carries the ownership model and virtual tags with it, so a platform engineer looking at a resource sees its relationships, its owner, its cost and its policy status in one place.
The durable waste in a cloud estate is in resources nobody can confidently claim, explain or safely remove. Ownership tells you who to ask; context tells you what depends on it. With both, “reduce cloud spend” stops being a risky guess and becomes a decision someone can make safely, with the owning team in the loop.
For engineering managers, this is the difference between a list of cleanup candidates and knowing which of them are actually safe to clean up.
Free local tool vs. Cloud Sleuth Cloud
The free local tool collects a basic inventory from a limited number of AWS accounts and Azure subscriptions and makes it searchable through a local UI or CLI, with nothing leaving your environment. Its topology is limited to basic lists. Cloud Sleuth Cloud is planned to add the full relationship graph and interactive visualization, Kubernetes and GCP inventory, large-scale multi-account support, and longer retention with historical trending.
Both are pre-launch. Get early access to hear first when they are ready.