A dev VM is used from 8 to 8, five days a week. That is 60 hours. The cloud bills 168. Multiply by every VM in dev and QA and the night shift is the most expensive team you have, and it does nothing.
Control Cloud reads your clouds through the provider API with read-only credentials and puts a number on that, from your own inventory, not from a calculator with guessed inputs.
What a night costs, by the hour
The Overnight bleeding card takes the VMs that are running right now, their hourly rate, and the hours a night you choose. On this demo organization: 16 running VMs, 12 hours a night, $1.51 an hour, $18.16 a night, $127 a week, $6,627 a year. It excludes what bills 24/7 anyway (databases, load balancers, NAT gateways), so the number is what you can actually get back.
Three things that bill for nothing
Under the card, the same page lists the efficiency opportunities it found: unused resources still billing (4 proven orphans: nothing uses them, they are still paid for), disks of stopped VMs (5 disks that keep billing although their VM is off) and off-hours shutdown (the estimated saving of powering dev and QA off at night and on weekends). Each one links to the breakdown in the cost advisor.
Then make it stop
Schedules power resources off and on at set times. Every run lands in the audit log (who, what, when, on which resource), and a run that fails emails the person who created the schedule. A shutdown that fails silently leaves four VMs on all weekend; that one is on the invoice, not in the UI, unless someone tells you.
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.
What do you do with dev and QA at night today: cron scripts, a tag and a Lambda, nothing? I answer every comment.
Top comments (0)