- Industry
- Procure AI
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Decision-maker
- Approver
- FinOps Lead
- Code
- ENG-13
It finds wasted cloud spend behind the platform, such as idle per-client sandboxes, oversized invoice OCR workers, unattached storage from finished sourcing events, spend-analytics clusters running overnight and commitments that no longer fit usage, and estimates the monthly saving. It decides which savings to take within the risk rules, schedules safe rightsizing and clean-up, and attributes the remaining cost to client tenants for margin reporting.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the cloud billing and usage export: the cost and utilisation per resource, with tags and client tenant, for the accounts and period named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to FinOps Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the infrastructure pipeline: it schedules the approved rightsizing, stop schedules and clean-up as changes. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The cloud cost policy: budgets per team, tagging rules including client tenant, rightsizing guidelines, the commitment strategy, the month-end peak profile for invoice ingestion, and the resources that must never be stopped.
Reads from
the cloud billing and usage export: the cost and utilisation per resource, with tags and client tenant, for the accounts and period named.
Acts in
the infrastructure pipeline: it schedules the approved rightsizing, stop schedules and clean-up as changes.
Hands back
A list with one entry per opportunity, each with resource, account, client_tenant (or shared), kind (idle, oversized, unattached, untagged, commitment or schedule), current_monthly_cost, proposed_change, monthly_saving (USD), risk (low, medium or high) and step (apply, schedule or report).
Asks a person when
A change touches production or a resource tagged do-not-stop, production-critical, payment-file, client-sandbox-contracted, deletes storage or snapshots, or buys or changes a commitment.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Idle below this average CPU (%) | 5 | A resource below this average CPU over the window is idle. |
| Lookback window (days) | 45 | Usage is judged over this window, long enough to include one month-end invoice peak. |
| Smallest saving worth acting on (USD) | 50 | Savings below this a month are reported but not actioned. |
| Where it may act | non_production_only | Where it may schedule fixes. |
| Longest commitment it may propose (years) | 1 | Reserved capacity is proposed for at most this term. |
| Tags that are never stopped | do-not-stop, production-critical, payment-file, client-sandbox-contracted | Comma-separated. Resources with these tags are reported, never changed. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Call a resource idle only when its average CPU stays below 5 percent with near-zero network over 45 days.
- Rightsize to keep the month-end peak under 70 percent, never to the mid-month average.
- Act only on savings of 50 a month or more, and only where non_production_only allows.
- Never stop, resize or delete a resource tagged do-not-stop, production-critical, payment-file, client-sandbox-contracted, including client sandboxes their contract guarantees.
- Snapshot before deleting any volume and keep it 30 days; sourcing-event and contract documents follow their retention rule, not the cost rule.
- Propose commitments of at most 1 years, sized to the steady baseline, and attribute untagged spend to a client tenant before calling it waste.
See the Cloud Cost Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.