Landing zone
Cost allocation by account and by team, consolidated billing, sandbox accounts that expire, budgets with alerts.
Cost optimization
We review your bill and your architecture together, then apply the changes in your accounts. The fee is a percentage of the measured monthly saving. The baseline and the measurement period are fixed in the contract.
An AWS bill is the sum of four layers. Each layer has its own cost topics, and the largest savings are usually in the workloads layer and in the network layer. We review all four, because a change in one shifts cost into another.
Cost allocation by account and by team, consolidated billing, sandbox accounts that expire, budgets with alerts.
NAT gateway and Transit Gateway data processing, VPC endpoints instead of internet paths, traffic that crosses Availability Zones without need.
Web application firewall rule tuning, threat detection and findings cost, log retention, security groups and resources nobody uses.
Rightsizing, Graviton and Spot capacity, Savings Plans and Reserved Instances once usage is stable, scale to zero outside working hours.
We read billing data and configuration, never your application data. You receive every finding with its saving per month and the effort to apply it, ranked by return.
We agree the baseline bill, the measurement period and the percentage. Setting the scope and the contract takes one to two working days.
We apply the changes in your accounts in order of return, each with a rollback plan. The saving is measured against the baseline each month, and the fee follows the measurement.
Tell us the size of the bill and what runs on it. An engineer replies within one working day.
Talk to an engineer