A smaller cloud bill, without the risk.
Hosting bills grow quietly: servers sized for a launch years ago, test machines nobody switched off, snapshots nobody deletes. I find the waste, cut it safely and show you the savings.
- Covers
- AWS, Google Cloud, Azure, Hetzner, DigitalOcean and dedicated hosting
- You get
- A costed list of savings, then the changes made
- Ongoing
- Included in Managed and the fractional lead plan
- Price
- A fixed quote, in writing
Where the money goes
The same few things turn up on almost every bill.
- 01Oversized servers
Machines sized for a peak that never came, resized to what they actually use.
- 02Forgotten resources
Test servers, old load balancers, unattached disks and IP addresses still being paid for.
- 03Paying on-demand for things that never stop
Reserved instances and savings plans for the servers that run all year.
- 04Old server generations
Providers keep releasing faster, cheaper server types, but existing servers stay on the old price until someone moves them.
- 05Storage, snapshots and backups
Old snapshots cleared, data moved to cheaper storage tiers, retention set on purpose.
- 06Data transfer
Traffic between zones and out to the internet, often fixed with a CDN or a change of layout.
- 07Too many servers, or the wrong provider
Consolidating small servers, or moving steady workloads to a cheaper provider where it makes sense.
Migrations →
How it runs
- Read the bill
Every line of the last few months matched to the server or service behind it.
- A costed list
Each saving with its monthly value and its risk, in the order I'd do them.
- The changes
Made in maintenance windows, with a way back, and checked afterwards.
- The result
The bill compared month on month, so you can see what was saved.
Regular infrastructure reviews
A one-off clean-up drifts back. A review every quarter keeps the bill and the servers current.
- 01New server types
When a provider launches a faster or cheaper generation, I tell you what moving would save and plan the migration.
Migrations → - 02Price and plan changes
Provider price rises, new storage tiers, reserved pricing about to expire: caught before the invoice.
- 03Capacity
Servers that have grown busy or gone quiet since the last review, resized either way.
- 04End of life
Releases nearing their end-of-life date, planned in before they become urgent.
End-of-life tracker →
Questions
Will cutting costs make things slower or less safe?
No. Every change is checked against real usage first, made in a maintenance window with a way back, and watched afterwards. Backups and monitoring are never what gets cut.
Which providers do you work with?
AWS, Google Cloud, Azure, Hetzner, DigitalOcean, Akamai (Linode) and dedicated hosting, for the Linux servers and services running on them.
Is it a one-off or ongoing?
Either. A one-off review is a fixed-price project. Managed and fractional lead clients get a quarterly infrastructure review as part of the plan, cost included.
How is it priced?
A fixed quote in writing after a short call, so you know the cost before anything starts.
Is your hosting bill bigger than it should be?
A 15-minute call: what you run and where, and whether a cost review is worth doing.