Skip to content

Assessment · Typically two weeks

Cloud Cost Assessment

Where spend can come down, what each change involves and what it is worth, before anything is committed.

Scope

  • Spend and utilisation across accounts and subscriptions
  • Kubernetes requests, limits, node pools and autoscaling
  • Storage tiers, snapshots and idle resources
  • Commitment (reservation / savings plan) fit
  • Egress, database and observability spend

Deliverables

  • Savings opportunities ranked by value, effort and risk
  • Quick wins the team can apply immediately
  • A commitment recommendation with the reasoning

We need read access to the relevant environments and a few hours of the team's time, never production credentials shared outside your own tooling.