We audit your cloud bill
Where your money goes on AWS, Google Cloud or Azure, and how much you can cut.
190 € · Delivered in 48 h
Why it ends up being needed
The cloud bill has an uncomfortable property: it grows on its own. Nobody decides to spend more; somebody just spun up a machine for a test in March, a database grew, and backups have been piling up for two years because deleting them feels risky and keeping them costs little. A little, every month, for twenty-four months.
The breakdown providers hand you is written for whoever built the infrastructure, not for whoever pays for it. Fifty lines with service names and units that are neither hours nor euros. It can be understood, but it takes a whole afternoon and knowing where to look, which is why almost nobody does it more than once.
Here that bill is read line by line and something else comes out: which resources you are paying for that nobody uses, which are oversized, how much each change saves in euros per month, and in what order to touch them. With an explicit warning about what must not be touched without testing first, which is the part that keeps a saving from becoming an outage.
What is included
- Your AWS, Google Cloud or Azure bill reviewed line by line
- Resources you are paying for and not using, and the ones that are oversized
- The saving estimated in euros a month, for each change proposed
- An order of play: what to touch first, and what not to touch without testing
What gets decided before a line is written
- What counts as an idle resource — Not just what is stopped: also what has been running at five per cent of its capacity for months. The first kind is obvious; the second is usually where the money is, and it appears in no alert the provider sends.
- Reserved or on demand — Committing to a year cuts the price substantially, and it is a bad idea if the volume is about to change. It gets decided with your real growth over recent months in front of you, not the optimistic projection in the business plan.
- What gets changed and what gets tested first — Shrinking a production machine without measuring its real peak is how a thirty-euro monthly saving ends up costing an afternoon of downtime. The report separates what can be applied directly from what needs a test.
- Old storage, handled with judgement — Two-year-old backups almost never need deleting: they need moving to the storage class that matches something nobody is going to read. It costs a fraction and it is still there the day you need it.
What is not included
- Applying the changes to your infrastructure: the report is for whoever runs it, and if you want us to do it we quote once we know what needs touching.
- Architecture redesign or migration between providers.
- Negotiating discounts or contracts with the provider on your behalf.
- A security review of the infrastructure, which is the cybersecurity service.
What you need to have
- Your last two invoices, or the exported cost report
- Read-only access to the console, if you want the fine detail
Frequently asked questions
Do you need access to my infrastructure?
It is not essential: the exported cost breakdown shows almost everything. If you do give us access, make it read-only and revoke it when we finish.
And if you find no savings?
We hand you the report anyway, explaining why your bill is already tight. It has happened, and it is a legitimate answer for €190.
Do you apply the changes yourselves?
The report is written for whoever runs your infrastructure to apply. If you want us to do it, we quote it separately once we know what needs touching.