I have been spending more time than I want to admit looking at hosting bills lately. Several of our ecommerce clients have come to us in the last few months saying sales are softer than they would like, but they do not want to pause our support entirely. The conversation always lands in the same place: where can we cut without breaking anything?
Hosting is almost always the first place I look, the same way skipping a Magento release is often the cheapest engineering decision a merchant can make in a soft quarter. Most merchants are paying for capacity they no longer use, on infrastructure that was sized for a peak that never quite returned, with backup retention nobody has audited in two years. The savings are real, the work is unglamorous, and the impact lands on the bottom line within the first invoice cycle.
Real Hosting Cuts From the Last 30 Days
Why Pausing Beats Pretending
When a client tells me sales are down, the worst thing I can do is keep invoicing for a roadmap that no longer matches their reality. I would rather pause new development than push work the merchant cannot absorb. The relationship survives a pause. It does not always survive a bill that lands at the wrong moment.
Pausing is not the same as walking away. We keep the lights on, we keep the support channel open, and we wait for the merchant to tell us when the budget is back. Long term, that is good for our agency too, because the merchants who are treated fairly during a slow quarter are the ones who restart with us when conditions improve.
Hosting Is the Cheapest Lever to Pull
Before we touch any feature work or rebuild any module, we pull up the hosting invoice. One UK client was paying £850 a month for a server we knew was overprovisioned. We moved them to a managed VPS this month for what comes out to roughly $79 per month including our partner discount. Same uptime, same response times, no merchant downtime during the migration.
Another client was paying $2,500 every month on AWS. The bill was a mix of unused storage, expensive logging, and a database tier sized for a Black Friday three years ago. We are right-sizing them down to roughly $1,040 a month right now. The work took our infrastructure team a few days. We approach it the same way we rebuilt a neglected UK store in 55 focused hours rather than a six-month overhaul. The savings continue every month for as long as they want them.
The $8,000 a Month That Should Be $2,500
The most extreme case I am working through right now is a merchant paying around $8,000 a month for hosting. The bill is dominated by backup storage, much of it years old, and a primary instance class that has not been reassessed since they launched. With a careful migration and an honest backup retention policy, I am confident we can land them somewhere closer to $2,500 a month without losing performance during peaks.
That is more than $5,000 a month freed up. For a merchant in a tight quarter, that money pays for a marketing campaign, a contract developer, or a runway extension. Hosting savings translate directly into options elsewhere in the business, and that compound effect is the part most operators undervalue when they are signing the renewal.
What to Audit Before You Renegotiate
Start with traffic. If your monthly visitor count is flat or down, your hosting plan probably should not be growing. Pull the last twelve months of analytics and compare them to your current resource allocation. Most overspend lives in the gap between peak-day capacity and what you actually use Tuesday at 3am.
Check your backup retention next. Daily snapshots stored for 365 days at full size is a very expensive insurance policy and almost never the policy you actually need. A tiered policy with daily for a week, weekly for a month, monthly for a year cuts storage cost dramatically and still gives you everything a real recovery scenario requires.
When a VPS Beats Managed Hosting
Managed Magento hosting is excellent if your team does not have infrastructure capacity in-house. But you are paying a premium for that managed layer, and once you are working with an agency that includes hosting management as part of the relationship, you are paying twice. A clean VPS with our team handling the operational layer regularly comes in at a fraction of the managed alternative, and once you pair it with sensible Core Web Vitals tuning on the Magento side, the performance numbers usually improve rather than regress.
The flip side is honesty. If your agency cannot actually run infrastructure, do not move off managed hosting. The cost saving disappears the first time you have an outage nobody can fix at midnight. We only recommend the move when we are the ones picking up the pager.
Where to Find Me Next
If you want me to look over your hosting setup and tell you honestly whether there is fat to trim, come find me at the next Ecommerce Camp UK. Bring your last invoice. We will go through it line by line.
Related reading: The Daily Monitoring Stack I Run on Every Ecommerce Site — the monitoring layer that sits on top of the hosting work, and why I treat them as one stack.
Related reading: Why I Refuse to Pay Hosting Two Months Ahead — the billing-shape rule that sits next to the cost-cutting work, and why advance hosting invoices are a vendor red flag.