UAE · ENBook a demo
HotelEngineeringDecision-maker

Cloud Cost Agent

Finds and reduces wasted cloud spend.

Cloud Cost AgentPlatform and Reliability
Industry
Hotel
Department
Engineering
Team
Platform and Reliability
Kind
Decision-maker
Approver
Financial Controller
Code
ENG-13

It finds wasted cloud spend behind the hotel systems (booking engine capacity sized for peak season all year, idle test environments, old reporting snapshots, untagged property spend and commitments that no longer fit) and estimates the monthly saving of each fix. It decides which savings to take within the risk rules and schedules safe rightsizing and clean-up, keeping booking capacity for the peak season and holding back anything that could slow bookings.

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 billing and usage export: cost and utilisation by resource, tag, system and hotel for the period..

  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 Financial Controller with its reasoning before anything goes out.

  7. 07Acts

    Once approved, it acts in the infrastructure pipeline: it schedules the approved rightsizing and clean-up. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The cloud cost policy: cost allocation by hotel and system, the seasonal demand calendar, commitment rules, protected resources and the rightsizing playbook.

Reads from

the cloud billing and usage export: cost and utilisation by resource, tag, system and hotel for the period.

Acts in

the infrastructure pipeline: it schedules the approved rightsizing and clean-up.

Hands back

A list, each with resource, system, property (or null), finding (idle, oversized, unattached, untagged or commitment), monthly_saving_usd, action, risk (low, medium or high) and schedule (date or held).

Asks a person when

The saving touches production, booking capacity, card-data scope resources, or a commitment purchase.

ApproverFinancial Controller

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
CPU below which a resource is idle (%)5Averaged over the look-back.
Look-back (days)30Usage window it judges by; booking capacity is always judged against last peak season too.
Smallest saving worth acting on (USD a month)50Smaller savings are listed but not scheduled.
Where it may act itselfnon_production_onlyProduction rightsizing needs approval unless set to all.
Months booking capacity must stay at peak sizeJune, July, August, DecemberBooking engine and reservation services are not scaled down in these months.
Tags that protect a resourcedo-not-stop, booking-critical, pci-scopeResources with these tags are never acted on.

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

Rules it always follows

  • Count a resource idle below 5 percent CPU over 30 days, and schedule only savings above 50 USD a month.
  • Never scale down booking engine or reservation capacity during June, July, August, December, or before a known demand event named in the request.
  • Never act on resources tagged do-not-stop, booking-critical, pci-scope.
  • Act itself only within non_production_only; production changes go to the Financial Controller.
  • Allocate every saving to its hotel and system so property P&Ls see it.

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 · Hotel | Basinwright Industries