The product
A live map of your cloud, with an owner on every resource.
Cloud Sleuth maps everything you run in AWS and Azure, works out who owns each resource even when it isn't tagged, and helps you clean up safely with the owners. Ask it in SQL, plain English or from your AI agent.
-
01 / question
Who owns it?
An owner on every resource: from tags where they exist, inferred from who created it, the IaC that manages it and how it's named where they don't, with a confidence score.
-
02 / question
What does it connect to?
A live map of everything you run, scoped to a team, service or VPC, so you see what a resource supports before anyone touches it.
-
03 / question
Is it safe to remove?
Last activity, dependencies and owner sign-off in one place, then a cleanup plan that snapshots first and can be undone.
The problem
Every tool shows a slice of your cloud. None of them tell you whose it is.
Rightsizing and idle-resource detection are the easy part. The waste that sticks around is in resources nobody can confidently claim, explain or safely remove, and unclear ownership is the root cause.
- 01 Native tags are incomplete, inconsistent or stale, and many resources can't be tagged at all, so the bill has a growing "unallocated" line.
- 02 Diagram tools draw the boxes but not who owns them or what to do next, and they turn into an unreadable hairball at a few thousand resources.
- 03 Inventory sits inside security platforms built for a different job, so a simple "what do we have and whose is it" report is hard to get.
- 04 Cost tools recommend changes that ignore intent, like HA headroom or a shared platform service, so the alerts get muted.
- 05 Nobody can confidently say what a resource is for, so the safe choice is to leave it running and keep paying for it.
Capabilities
Seven capabilities on one live inventory.
The map is what you see first. Ownership is what makes every other view useful: search, cleanup, allocation, guardrails and the answers your AI agents get all know whose resource it is.
Live Cloud Map
An AWS and Azure architecture diagram that draws itself from your real accounts, scoped to a team, service or VPC, with the owner, cost and next step on every resource.
? What does it connect to?
Read moreAutomatic Ownership
An owner on every cloud resource, even untagged ones: inferred from who created it, the IaC that manages it, its name and its neighbors, with a confidence score the owner confirms in one click.
? Who owns it?
Read moreSafe Cleanup
Remove idle and orphaned cloud resources without the outage: dependencies, last activity and owner sign-off first, then a plan that snapshots, stops before deleting and can be undone.
? Is it safe to remove?
Read moreInventory Search
A cloud asset inventory you can query: every AWS and Azure resource in one schema, searchable in SQL or plain English, with saved views and export.
? What do we actually have?
Read moreCost Allocation & Showback
Put every dollar of AWS and Azure spend on a team, even where tags are missing or can't exist: virtual tags, shared-cost splits, backfill, and showback and chargeback built on owners people have confirmed.
? Who pays for it?
Read moreGuardrails
Built-in checks and your own policies, including existing Cloud Custodian policies, evaluated against the live AWS and Azure estate, with each finding routed to the resource's owner. Quiet by default.
? Is it allowed to exist like this?
Read moreMCP Server for AI Agents
Give Claude, Cursor and your own AI agents read-only answers about your AWS and Azure estate: who owns a resource, what depends on it and what's unowned, before they act.
? Can my agent act on it safely?
Read moreBuilt against the complaints
We read what people say about today's tools. Then we designed out every complaint.
These are the themes that keep coming up in G2 reviews of cloud diagram, inventory, FinOps and governance tools. Each one shaped a decision in Cloud Sleuth.
What reviewers say
What Cloud Sleuth does
-
Reviewers say: Expensive, and priced per resource
Cloud Sleuth: One flat price with unlimited resources and users. The CLI is free with no resource cap.
-
Reviewers say: A steep learning curve and slow setup across many accounts
Cloud Sleuth: One read-only command and no YAML to start. Built to show a map and owners in minutes, not after a rollout project.
-
Reviewers say: Diagrams get cluttered and laggy with thousands of resources
Cloud Sleuth: Maps scoped to a team, service, account or VPC, so you see the 40 boxes that matter instead of all 4,000.
-
Reviewers say: "Only visualisation does not help"
Cloud Sleuth: Every box has an owner, a cost and a next step, and the next step goes to that owner in Slack or Jira.
-
Reviewers say: AWS first, everything else later
Cloud Sleuth: AWS and Azure at parity from day one, in one schema. GCP and Kubernetes are next.
-
Reviewers say: Noisy alerts that nobody owns
Cloud Sleuth: Findings go to the resource's owner in a weekly digest by default. Exceptions expire instead of piling up.
-
Reviewers say: Hard to get a simple inventory report out
Cloud Sleuth: Ask in SQL or plain English, save the view, and export to CSV, an API, draw.io or Mermaid.
-
Reviewers say: Automation that changes things without telling you
Cloud Sleuth: Read-only by default. Every change is previewed, explained, approved by the owner and reversible.
Themes from G2 reviews, October 2026. Cloud Sleuth is pre-launch, so the right-hand column describes what we're building.
Pricing
One flat price. Unlimited resources. A CLI that's free for good.
Tools that charge per resource or per dollar of spend get more expensive exactly when your estate gets messier. Cloud Sleuth doesn't.
-
Cloud Sleuth CLI
Free forever
For an engineer and their own accounts. Runs on your machine, and nothing leaves it.
Get early access- AWS and Azure, unlimited resources
- Live cloud map, exported to draw.io, Mermaid, SVG or PNG
- Owner inference from tags, CloudTrail and Activity Log, IaC state and naming
- Inventory search in SQL or plain English
- Built-in checks: no owner, untagged, orphaned, idle
- Local MCP server for Claude, Cursor and other AI tools
-
Cloud Sleuth Cloud
flat price$399 per month, flat
For the whole team and every account, with nothing to install.
Get early access- Everything in the CLI, hosted and always up to date
- Unlimited users, resources and accounts
- Owner confirmations and findings in Slack and Jira
- Safe cleanup plans with approvals, snapshots and undo
- Virtual tags, shared-cost allocation, showback and chargeback
- Custom guardrails, including your Cloud Custodian policies
- 13 months of history, with a diff of what changed
-
Enterprise
Custom annual
For regulated estates and large organizations.
Talk to us- Everything in Cloud
- Self-hosted in your VPC, or single-tenant
- SSO, SCIM and fine-grained RBAC
- Audit log export and data residency
- Service catalog and IDP integrations
- Support SLA and a named engineer
- Never priced per resource, so a bigger, messier estate doesn't cost more to clean up.
- Never a percentage of your cloud spend or of your savings.
- Unlimited users, so every owner can see and confirm what's theirs.
- The CLI stays free, with no resource cap.
Planned launch pricing. Both editions are in development, and prices may change before launch.
Who it's for
Mid-market teams without a FinOps department.
Companies spending roughly $50k to $2M+ a month on cloud, where one person or a small platform team owns cost, native tools and spreadsheets have run out of road, and enterprise FinOps platforms feel too heavy.
-
Platform engineer
Needs
Understand the estate, enforce standards, reduce ownership ambiguity
Gets
A live map, SQL over the whole estate and guardrails that route to owners
-
FinOps practitioner
Needs
Allocate 100% of spend and drive accountability
Gets
Inferred owners, virtual tags, shared-cost allocation and a shrinking unallocated number
-
Engineering manager
Needs
See what their team owns and what is safe to clean up
Gets
A map of just their team's resources and a cleanup plan they can approve and undo
-
Finance & leadership
Needs
Trustworthy showback and chargeback
Gets
Showback and chargeback tied to owners people have confirmed, at a flat price
What it is, and isn't
Not another cost dashboard, or another diagram.
Cloud Sleuth doesn't try to be a commitment-automation, Kubernetes-rightsizing or security tool. It's the map and the ownership those tools are missing.
- Every view, from the map to the bill, knows whose resource it is, including the untagged ones.
- A map, a queryable inventory, cleanup, allocation and guardrails on one inventory instead of five tools.
- AWS and Azure at parity from day one, in one schema.
- Findings go to someone who can act, quietly by default, and nothing changes without the owner's approval.
- A flat price with unlimited resources and users, and a CLI that stays free.
Roadmap
The map and the owners first, then the rest.
Early users get the map and the owners quickly while Cloud Sleuth Cloud is built. No dates yet; the early-access list hears first.
-
Phase 1 · first
CLI: map and owners
- AWS and Azure inventory
- Live cloud map with export
- Owner inference with confidence
- SQL and plain-English search
- Local MCP server
-
Phase 2
Cloud: work with the owners
- Team workspaces, unlimited users
- Owner confirmations in Slack and Jira
- Safe cleanup with approvals and undo
- History and change diffs
-
Phase 3
Allocation & guardrails
- Virtual tags, shared costs, showback
- Custom and Cloud Custodian policies
- GCP and Kubernetes
- IaC drift and codifying unmanaged resources
-
Phase 4
Enterprise
- Self-hosted and single-tenant
- SSO, SCIM, audit and data residency
- Service catalog and IDP integrations