UAE · ENBook a demo
Insure AIEngineeringDecision-maker

Cloud Cost Agent

Finds and reduces wasted cloud spend.

Cloud Cost AgentPlatform and Reliability
Industry
Insure AI
Department
Engineering
Team
Platform and Reliability
Kind
Decision-maker
Approver
FinOps Lead
Code
ENG-13

It finds and reduces wasted cloud spend across the insurance platforms, such as idle quote environments, oversized claims databases and analytics clusters left running after the reserving close. It proposes rightsizing and commitments and acts only within the agreed scope.

How it works

7 steps, and a person signs off before step 7.

  1. 01Looks it up

    Finds the record the request is about in the cloud account: cost and usage by resource over the lookback..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Forecasts, when it decides

    Projects what each option will cost or return before it recommends one.

  5. 05Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  6. 06Asks a person

    Hands the work to FinOps Lead with its reasoning before anything goes out.

  7. 07Acts

    Once approved, it acts in the cloud account: it applies the approved rightsizing and shutdowns. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The cloud cost policy, the workload calendar (renewal peaks, month-end and quarter-end reserving, catastrophe surge capacity) and protected workloads.

Reads from

the cloud account: cost and usage by resource over the lookback.

Acts in

the cloud account: it applies the approved rightsizing and shutdowns.

Hands back

A list, each with resource, finding, action, monthly_saving and risk.

Asks a person when

The change is in production, involves a commitment, or touches surge capacity.

ApproverFinOps Lead

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Idle below CPU (%)5Resources below this are idle.
Lookback (days)30History looked at.
Smallest saving to propose (USD)200Smaller is ignored.
Act itself onnon-productionWhere it may act.
Protected tagscatastrophe-surge, reserving-close, renewal-batchNever touched.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Treat resources under 5 percent CPU over 30 days as idle, but check the workload calendar for renewal, reserving and catastrophe peaks first.
  • Never touch resources tagged catastrophe-surge, reserving-close, renewal-batch.
  • Propose savings of at least 200 a month.
  • Act only on non-production; the rest needs the FinOps Lead.
  • Keep catastrophe surge capacity sized for the claims volume of the worst recent event.

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.

Cloud Cost Agent · Insure AI | Basinwright Industries