Skip to content

Cloud cost optimisation: pay for the load you actually have

We go through the bill line by line and compare it with real consumption. Then we remove what is not used, resize what is oversized and make capacity follow the load. You get a report with the bill before and after. How far it drops depends on how the system was built.

When you need this

  • 1

    The AWS bill grows faster than traffic

  • 2

    Nobody can say which service or team a line in the bill belongs to

  • 3

    Instances were sized with a margin at launch and never revisited

  • 4

    Workers and test environments run at night and at weekends with nothing to do

  • 5

    You suspect the same workload would cost less at another provider

What's included

  • Bill audit

    Cost Explorer and usage reports are broken down by service, environment and tag. We find the largest lines and the ones nobody can explain.

  • Unused resources

    Detached volumes, old snapshots, idle load balancers, unattached IP addresses, forgotten environments. We list them, confirm with you and then remove them.

  • Right-sizing

    CPU and memory usage of EC2 instances, RDS databases and Kubernetes pods is compared with what is provisioned. Instance sizes and Kubernetes requests are brought down to the measured load plus a margin.

  • Autoscaling and scale-to-zero

    Services scale with load through HPA. Workers scale by queue depth through KEDA and stop when the queue is empty. Non-production environments shut down outside working hours.

  • Pricing models

    Steady load goes to Savings Plans or reserved instances, interruptible work goes to spot. We also check data transfer, NAT gateways, S3 storage classes and log retention.

  • Cheaper provider

    For workloads that do not depend on AWS-specific services we calculate the cost on Hetzner or another provider and compare the difference with the migration effort.

The bill follows the load

A cost review ends with a report like this: what you paid before, what you pay now, and where the difference came from.

billing · cost reviewmonthly, USD

Monthly cost

Before
$10,400
After
$6,200
Δ per month
−40%

Cost by month

M1M2M3M4M5M6
BeforeAfter

Cost by service

ServiceBeforeAfterΔ
EC2 / EKS compute$5,200$2,900−44%
RDS$2,100$1,500−29%
NAT + data transfer$1,600$650−59%
S3 + EBS$900$550−39%
Other$600$6000%

Example of the report format with illustrative figures. The real saving depends on the account and is shown to you before anything is changed.

How the work goes

  1. 1

    Call and access

    You grant read-only access to billing and monitoring. Nothing is changed at this stage.

  2. 2

    Report and price

    A list of findings with the estimated effect and the risk of each, ordered by return. The price of the work is agreed before it starts.

  3. 3

    Changes

    We apply the agreed items through code, starting with the safe ones. After each resize we watch the metrics to confirm that performance holds.

  4. 4

    Result and control

    A before-and-after comparison of the bill, plus budgets and cost alerts, so the next increase is noticed when it starts.

Questions

  • AWS Cost Explorer
  • AWS Budgets
  • AWS Compute Optimizer
  • Kubernetes
  • KEDA
  • Terraform
  • Grafana
  • VictoriaMetrics
  • Hetzner
  • Cloudflare

Describe the task — get a plan and a price

Write what you have and what you need. We answer within one business day with questions or a concrete proposal.