Test machines nobody switched off, disks left behind by deleted servers and seats nobody uses keep costing money every month. CloudMonitor lists them across your environment, or your clients', with an estimated monthly cost beside each one.
Cloud billing is per resource per hour, and resources outlive the projects that created them. A proof of concept ends, the team moves on, and the machine, the disk and the public address keep running.
Nobody owns the leftovers. They do not break anything, so no alert fires, and they hide inside a total that grows a little each month until finance asks why.
Cost tools show where money went. They rarely say which individual resource is idle and safe to review, and each platform has its own report in its own console.
Every platform CloudMonitor connects to, in the same order on every page, with what it checks for this problem today. Where nothing is checked yet, the table says so.
| Platform | What CloudMonitor checks for this problem | Status |
|---|---|---|
| Microsoft Azure | Virtual Machines: Idle and oversized VMs Waste: Orphaned resources, priced Cost: Reservation expiry, spend anomalies, budget burn | Live |
| Microsoft 365 & Entra ID | Licenses: Assigned but unused seats | Live |
| Amazon Web Services | EC2 & EBS: Exposure, idle and unattached resources Waste: Orphaned resources, priced Reserved Instances & Savings Plans: Commitment expiry Cost Explorer & Budgets: Spend anomalies, budget burn (opt-in) | Beta |
| Google Cloud | Compute Engine: Exposure, idle instances Waste: Orphaned resources, priced Committed use discounts: Commitment expiry Billing export: Spend anomalies, budget burn (opt-in) | Live |
| Kubernetes | Version support, node health and workload checks only. No idle-cost check yet. | No check yet |
| Containers & registries | Host and image posture only. No idle-cost check yet. | No check yet |
| On-prem servers & Exchange | Disk, patch and certificate checks only. No idle-cost check yet. | No check yet |
| MuleSoft Anypoint | Runtime status and alerts only. No idle-cost check yet. | No check yet |
| Domains, DNS & email | Not a cost check. Domain and certificate checks cover renewal dates, not spend. | No check yet |
| Uptime & heartbeats | Not a cost check. Endpoint and heartbeat monitoring has no idle-cost view. | No check yet |
How deep each platform goes. Live means scheduled for every connected account; Beta means scheduled and verified against emulated APIs only. Azure is the most complete and is run against real accounts every day. The AWS and Google Cloud scanners have been verified against emulated APIs, not yet against live customer accounts. Kubernetes, MuleSoft and the on-prem collector are narrower still.
Access is read-only and least-privilege, and there are no agents to install on your cloud accounts.
Full setup guide: connectors.
Each platform has its own rules, shown in the table above: for example idle or oversized machines, disks and other resources attached to nothing, and license seats assigned but unused. Findings are prompts to review, not instructions to delete.
Yes, where a cost can be estimated. Orphaned resources are priced and shown with an estimated monthly cost, so you can start with the largest.
No. Access is read-only. It tells you what to look at and where; you decide what to change.
No. Idle and orphaned resource checks work from resource inventory. Spend anomaly and budget checks on AWS and Google Cloud are opt-in and need billing data connected.
No. The table states what each platform contributes today and marks the ones with no cost check yet. AWS and Google Cloud scanners have been verified against emulated APIs, not yet against live customer accounts.
There is a 14-day free trial with no credit card. After that plans are flat monthly bands; see the pricing page.
14-day free trial. No credit card needed to start, and it never turns into a paid plan on its own.