Skip to content

Cloud cost optimisation · Google Cloud & AWS

Cut your cloud bill without breaking production.

Most cloud accounts pay for machines that are too big, services nobody uses and storage that only grows. We find the waste, prove it with your own billing data, and remove it safely. Nothing changes without your sign-off.

Recent client bill
−33% in one month
Downtime caused
None
Access needed to start
Read-only

The real problem

Your cloud bill isn't the scary part.

Most businesses already suspect they're overspending. What stops them acting is the fear that whoever cuts the bill will take the site down three weeks later.

What usually happens

  • A dashboard suggests smaller machines without knowing what runs on them
  • Servers get resized, the bill drops, and nobody checks memory afterwards
  • A restart loses a public IP address and a site goes dark
  • The cost plan is written once and never checked against what was done
  • Six months later the bill has quietly climbed back

What we do instead

  • Every change verified against your account's own audit logs
  • Memory and swap history checked before any machine shrinks
  • Addresses, snapshots and rollback steps confirmed before anything is touched
  • Free configuration fixes recommended before paid upgrades
  • A budget alert left in place, because costs drift back on their own

Case study

A third off the bill in four weeks

An investment research platform's Google Cloud bill had risen every month under the setup it inherited from its previous developer.

−33%
monthly cloud bill, August to September, from the client's own billing reports
−99%
App Engine spend after moving the API to Cloud Run, with a one-command rollback kept ready
0
minutes of downtime, with every change verified against the account's own audit logs

Read the full case study →

What an audit catches

Things a cost dashboard won't tell you

Your cloud provider gives you resize suggestions for free. They don't know what those changes will break, or what has already been changed in your account.

A saving that was breaking production

A server had been resized months earlier, halving its memory. The bill went down, then the machine started killing its own database under load. The real cause was a cache set to 78% of memory. Fixing that cost nothing, and the smaller machine was fine.

A cost plan built on wrong facts

Services listed for migration had already been migrated. A charge blamed on the main API came from a batch server. None of it was visible without reading the audit logs.

Deploys weeks from failing

Old app versions had piled up to 200 of a hard 210 limit. Nobody had noticed, because nothing fails until the day you can't ship a fix.

Pricing

Fixed fees, not a cut of your savings

Savings depend on traffic and timing, so billing a percentage of them turns the job into an argument about numbers. You pay a fixed price, and you keep every ringgit saved.

Start here

Free Cloud Cost Triage · 1 working day

Read-only access, no commitment. Your three biggest spend lines explained, an estimated savings range, and an honest answer on whether it's worth going further.

Get a free triage

Cloud Tune-up

RM1,999 fixed

For bills of about RM1,000–6,000 a month · 3 working days

  • Unused IP addresses, orphaned disks and stale snapshots removed
  • Oversized machines right-sized, after a memory check
  • Monitoring and image storage capped so they stop growing
  • A budget alert left in place
Book a tune-up

Implementation

RM2,999–5,999

Scoped from the audit ledger · 2–3 days

  • Approved changes applied one at a time
  • Maintenance windows scheduled with you
  • A snapshot and written rollback before each change
  • Ledger updated as each item closes
Discuss implementation

Want it watched every month? Spend anomalies, new unowned resources and capacity headroom can be covered within any monthly engineer plan. On the recent client above, the Tune-up price would have paid for itself in under four months of savings.

How it works

Read-only first, always

  1. 01
    Viewer access
    Read-only roles on the project and billing account. We can't change anything, even by accident.
  2. 02
    Free triage
    Within a day: your biggest costs explained. Walk away here at no cost.
  3. 03
    Tune-up or audit
    Evidence gathered, every finding checked, capacity confirmed.
  4. 04
    You approve each change
    Nothing is applied until you sign off that specific item, with a snapshot and rollback ready.

One thing worth doing today, whether or not you hire us

On Google Cloud, switch on detailed billing export to BigQuery. It's free, takes two minutes, and only records from the day you turn it on. Every week it stays off is detail you can't get back.

Not sure your bill is worth a look?

Start with the free triage. If the numbers don't justify going further, we'll tell you, and it costs you nothing to find out.