The disk outlives the VM. The bill knows; the console does not tell you.

Stop a VM and the compute meter stops. The disk under it keeps billing, every hour, until someone deletes it. Nobody does, because the console shows a stopped VM and a disk that looks attached to something. Six months later it is a line on an invoice nobody can explain.

Control Cloud reads your clouds through the provider API with read-only credentials and shows that disk for what it is.

A list of what bills for nothing

The alerts page opens with the unused resources that are still billing. On this demo organization: 4 proven orphans (nothing uses them, they are still paid for) and 5 disks whose VM is stopped. Each item carries an estimated monthly saving and a link to the breakdown in the cost advisor. Proven means the API confirmed it, not a heuristic on names.

On the map, every disk hangs from its VM

The topology draws disks as nodes attached to the VM that uses them. A disk with no edge stands out at first glance: there is nothing on the other end. Click it and the panel shows size, attach state and tier, the three things you need to decide whether it is a snapshot waiting to happen or money leaving every hour.

Why this is not another cost dashboard

Cost tools tell you the total went up. This shows you the resource, in its place, with what it is connected to, read live from the cloud. You see it on the map; you do not find it on the invoice.

Watch the 20-second clip · Full 60-second demo

Try it

Free plan: 1 operator, 1 provider, no card. Public clouds and on-prem on one surface, read-only API access, no agents on your VMs.

Request access

How do you find the disks of VMs that were stopped months ago today? I answer every comment.