VoyantIQ

Custom Agents. Not finding the agent you need? Have one built for your business, and it is not finished until it passes the cases you wrote.

The whole catalogue

Idle Cloud Spend

Flags cloud resources with no recorded activity, works out who owns each one, and estimates what stopping it would save.

Everybody knows there is waste in the bill and nobody can find it, because finding it means reading a billing export against a tag inventory against a directory of who has left. The concept does that join, flags what has had no recorded activity over a stated period, puts a name against each one, and estimates what stopping it would save. It would stop nothing and resize nothing. A flag is where a person starts looking, not a verdict. None of it is built yet.

Availability

In Development. Specified, and not built. The run below is the shape the job would take, not a recording of one. Nothing of it runs today, so it cannot be subscribed to and carries no price.

Intended user

Whoever gets asked why the cloud bill went up, and has to find out from three exports that do not agree.

Monthly price

Not purchasable. No price, and no subscribe button until it runs.

Nothing here runs yet, so there is no Subscribe and no Run on this page. Asking for it is what decides which of the five gets built first, and a close variation of it can be quoted as a custom build today.

Request This ToolDiscuss an adaptation

What this is not.

The corrections worth making before anything else on this page is read, because each one is a thing a reader could reasonably assume and would be wrong about.

  • A flag is not verified idleness. A resource with no recorded activity may be a warm standby, a disaster-recovery copy, or a job that runs once a quarter. The owner confirms. The agent only points.
  • Every saving is an estimate, and it states the period it measured and what the export did not cover. It is not a quoted reduction in anybody's bill.
  • It stops nothing, resizes nothing and deletes nothing. A recommendation existing is not permission to act on it.

How the job would go.

Four steps, in order, ending where it stops. No timing is published for any of them: nothing has run, so there is nothing to measure, and a written duration shown as a measurement would be an invention.

Idle Cloud Spend, start to finish

Illustrative
  1. Joins the billing export to the tag inventory
  2. Flags what shows no activity in the period
  3. Matches each flag to an owner
  4. Estimates what stopping it would save
Would readBilling exportTag inventoryOwner directory
Open a ticket for each owner?

Illustrative. The steps are written for this page to show the shape of the job, and none of it is a recording.

What would land when it finishes.

A list of flagged resources, each with an owner against it and an estimate of what stopping it would save, with the assumptions behind the estimate printed beside it.

Flagged, with an owner against eachThree of twenty two, by estimated monthly costIllustrative
ResourceNo activity forEstimated monthlyCaveat
db-staging-replica-228 days412.00Flagged, not verified idle
gpu-pool-experiments34 days1,860.00Flagged, not verified idle
logs-archive-eu-west41 days97.40Flagged, not verified idle

Nothing would be stopped, resized or deleted. Each figure projects the resource's own recorded cost over the stated period forward at the same rate; committed-use and reserved discounts are not in a usage export, so a real saving can be lower. The resources, the days and the figures are written for this page.

Illustrative. These rows are written for this page and are never a customer’s data.

Supported inputs

Kinds of source, from accounts you would connect in your own Tools workspace. Which account, and the credential behind it, are yours and never appear anywhere on this site. No named integration is listed, because none has been built.

  • Billing export
  • Tag inventory
  • Owner directory

Output

A list of flagged resources, each with an owner against it and an estimate of what stopping it would save, with the assumptions behind the estimate printed beside it.

Illustrative

Approval boundary

Open a ticket for each owner?

Reading, checking and comparing change nothing outside your workspace and would happen on their own. Anything that cannot be taken back waits for you, and what it is asking about is shown in full rather than summarised.

Idle Cloud Spend is in development.

It is specified and not built. Billing does not exist yet and the usage allowance has not been measured, so there is nothing to subscribe to and no price to show. Asking for it is what decides what gets built next; a close variation of it can be quoted as a custom build today, against acceptance cases you write.

Request This ToolHave one built for your business

The rest of the catalogue.