Cloud Cost Optimization
FeaturedStarts from the bill, attributes each of the largest lines to the service and team that caused it, and only then proposes savings, each with its dollar value and its risk.
How it works
- Runs when: on a schedule, or when you ask for a cost review.
- States its window: reads the coverage of the cost data first, and says how much of the month it can actually see.
- Attributes the largest lines: one subagent per bill line, in parallel, working from traffic flow rather than from the line's name.
- Proposes changes: each with the saving in dollars a month and the risk, stated as what would have to happen for the change to hurt.
- You get: savings ranked by saving per unit of risk, with the ones it declined and why. A validator subagent argues against the whole set before the total is reported.
What it needs
- Vantage: read cost reports
- AWS: read resource usage and flow