Cloud cost reduction
We cut your cloud bill and get paid from what we save
01 / The problem
Where the money actually goes
Most cloud bills are big for three separate reasons, and most cost-cutting only addresses one of them.
Provider pricing
The same workload costs different amounts on different clouds, and the list price is rarely the price you have to pay.
Infrastructure
Instances sized for a load test that ran two years ago. Idle environments nobody turned off. Storage on the wrong tier. Egress nobody measured.
Software
The query that scans a whole table. The service that retries in a tight loop. The job that runs hourly and needs to run nightly.
This is the expensive one, and it's the one almost nobody touches.
02 / The work
What we do about each one
Three problems, three different kinds of work.
Fix the software that creates the bill
Profiling the hot paths, the query patterns, the retry logic, the scheduled jobs. Infrastructure changes save money once. Software fixes keep saving it every month after, including long after our fee period ends.
Right-size the infrastructure
Reserved and spot pricing, instance families, autoscaling that actually scales down, storage lifecycle, network paths. Unglamorous work with fast payback.
Move to better economics
For US companies, provider credit programs are substantial. AWS and Google both run them, in both directions. We've moved clients between providers and claimed six figures in credits as part of the migration.
Credits are never the plan on their own. They're a bonus on top of real savings, and they're yours — our fee is calculated on the actual reduction in run-rate cost, not on your invoice while credits are burning down.
03 / Process
How it works
Six steps, and nothing is sold before step five.
-
01
You tell us what you spend.
Two minutes, the form at the bottom. -
02
We sign an NDA.
Before you show us anything. -
03
You give us read-only access.
Cloud accounts and the relevant repositories. Read-only, nothing else. -
04
We audit.
Infrastructure, spend patterns, and code. -
05
We come back with a number and a proposal.
This is the first point at which any offer exists. Nothing is being sold to you before the audit is done. -
06
You decide.
If the numbers don't work for you, we part ways and you keep the report.
04 / Terms
The deal
Nothing up front. Here's the whole invoice, in advance.
- Up front
- $0.00
- Our fee
- Share of savings
- After the term
- All yours
05 / Trust
Access, and what we don't do
You're being asked to let a stranger look at production. Here's exactly how far that goes.
What we ask for
- Read-only access, always. We don't need write access to audit.
- An NDA first. Signed before anything is shared with us.
- The relevant repositories. Read-only, and only the ones that touch the bill.
What we don't do
- × We don't move you onto our tooling, our platform, or our hosting.
- × We don't take ownership of your accounts or your infrastructure. They stay yours.
- × We don't leave anything to unpick. Stop working with us and nothing breaks.
06 / About us
Who we are
An engineering firm, not a cost-cutting consultancy.
Automaze works as CTO-as-a-Service: senior technical leadership and delivery for founders and companies who need it without hiring it full time. Cost work is one of the things that comes with knowing infrastructure and code equally well.
07 / Get started
See if you qualify
The audit is free if you're spending $5,000+ per month. The rest of these just tell us which options are open to you.
08 / FAQ
Frequently asked questions
The things people ask before they hand over access.
What if you don't find anything?
Then we tell you, you keep the report, and you owe us nothing. It's happened, and we'd rather say it than pad an invoice.
What if we want to stop partway through?
The terms cover that before anyone signs. We're not interested in locking anyone into anything.
Do you need write access to our accounts?
No. Read-only for the audit. If you then want us to do the migration work, we agree that access separately and explicitly.
What about the credits — are you just taking those?
No. Our fee is based on the real reduction in what your infrastructure costs to run. Credits are separate, they're yours, and they reduce what you actually pay while our fee period runs.
Who does the migration work?
We do. That's included. You're not getting a PDF and a wish of good luck.
Do you look at our code?
With an NDA in place and read-only access, yes — that's where a lot of the savings are. If you'd rather we stayed on the infrastructure side only, say so and we'll scope it that way.
Can you keep working with us after the audit?
Some clients do. Automaze is an engineering firm, and cost work often surfaces architecture problems that are bigger than a cost project. That's a separate conversation, and only if you want it.