Save money and cut cloud costs. Don't compromise performance.
DevOps engineer with extensive experience across AWS and GCP. I find the money your provider quietly collects for resources nobody uses, then remove it: Kubernetes, databases, storage, commitments.
The audit is free. Once the optimization is done and the savings show up on your own bill, I invoice three times one month of verified savings. One invoice, after the first full month.
How it works
Read-only access to billing data and infrastructure. You get a written list of what wastes money and what each fix is worth.
Take the whole plan, part of it, or none of it. Walking away here costs you nothing.
Changes go out incrementally, off-peak, each with a rollback. Your team reviews every change.
After the first full month we compare bills. Three times the verified monthly saving, once.
Cases I'm most proud of
The Kubernetes estate had been sized for peak traffic and left there. Four moves, no architectural rewrite.
A deeper job: the database and the Kubernetes architecture itself, further than any cost dashboard reaches.
Questions I get asked first
Read-only to start: the billing export and cluster metrics. Write access only for changes you have approved, and I am happy to work entirely through your CI and pull requests.
One to two weeks for a typical account. Longer when the setup is unusual or access takes time to arrange.
You keep the written audit and I send no invoice. That is the entire arrangement.
That is the one thing I don't trade for money. Every change ships incrementally with a rollback path. In the game studio case reliability went up while the bill went down.
By your cloud provider's own invoice. The last full month before the work against the first full month after, same provider, same currency. The difference is what my fee is calculated from.
Yes, send yours before the audit. The cases on this page are published without client names for the same reason.