Cloud cost optimisation

Know what every dollar on your cloud bill is buying.

Most cloud bills carry waste nobody has looked at: logs nobody reads, idle load balancers, oversized databases and usage-based tools nobody capped. We find it, remove it safely and set guardrails so it stays gone.

Cloud cost optimisation
The problem

What this solves

The bill grows and nobody can say why

We break it down by system and team so each cost has an owner.

Logging costs more than the servers

We tune what is logged and for how long.

Old projects are still running

Idle VPNs, empty load balancers and forgotten environments are removed after sign-off.

A usage-based tool surprised you

We set caps, budgets and alerts on usage-billed tools and APIs.

Deliverables

What you get

  • A cost breakdown by system, environment and team
  • Savings ranked by value and risk
  • Safe removal of unused resources after your sign-off
  • Rightsizing and commitment recommendations
  • Budgets and alerts
  • A one-page summary for finance
Engagements

Ways to work with us

  • One-off cost review
  • Implementation of agreed savings
  • Monthly cost tracking
  • Build-versus-buy analysis
  • Costing a new service before you commit, such as a reporting or BI tool

Scope this with us

Process

How the work runs

  1. Read

    Billing and read-only access; up to twelve months of data.

  2. Attribute

    Costs mapped to systems and owners.

  3. Recommend

    Savings ranked by value and risk.

  4. Act and guard

    Approved changes made, then budgets and alerts set.

Results from the field

What changed when we did this work

25%of one month's AWS bill was loggingCost review

Monthly tracking against approved budget lines surfaced the cost; logging review, reserved instances and NAT consolidation were committed as offsets.

US$12Kin-house build against a US$240K vendor proposalBuild versus buy

An analysis that led leadership to choose the in-house route.

Leannetwork hub design chosen on costCost by design

A private network hub built in its lean form: one VPN to the standby provider and client VPN cut to a single subnet.

Stack

Tools we work with

  • AWS Cost Explorer
  • AWS Budgets
  • Cost and Usage Reports
  • Compute Optimizer
  • Trusted Advisor
  • CloudWatch
  • Terraform
  • your finance team's spreadsheets
FAQ

Questions buyers ask us

Still unsure? Ask us directly; you will get an answer from an engineer.

How much can we save?

We do not quote a percentage before seeing your bill. The review states exactly what we found and what each saving is worth.

Will cost cuts weaken security?

No. Controls needed for security and compliance are kept, though often made cheaper.

Do you only do AWS?

Our cost work is deepest on AWS. We also review Azure, Google Cloud and Hetzner bills; how far we can go depends on the billing access you have.

Do you need write access?

Not for the review. Changes are made only after you approve them.

Harare city skyline

Tell us what you are running today.

Send a short note about your systems and what is getting in the way. You will hear back from the engineer who would do the work.