A potential client walked me through their agency contract this month and one line stopped me. Every monthly bill from the agency included a hosting fee. Not a pass-through invoice from a hosting vendor. A fee, set by the agency, for infrastructure the agency controlled. The merchant did not know which company hosted their store, what the real server cost was, or what would happen to the site if the agency relationship ended badly. They were paying for the privilege of not knowing.
Regardless of how good the agency is, that structure is wrong. If you run an ecommerce business, the infrastructure your business stands on should belong to you. Not to your developer, not to your agency, not to the freelancer who set it up three years ago. You.
MageCloud Hosting Ownership Note
The Ownership Test for Ecommerce Infrastructure
THE BILLING TEST
The hosting bill hits your card
The agreement is between you and the hosting vendor. The invoice arrives in your inbox, priced in the vendor’s real numbers, not wrapped inside an agency fee.
THE ACCESS TEST
You hold the root credentials
Your agency works inside your infrastructure with access you grant. If the relationship ends tomorrow, the only thing that changes is who logs in.
THE NUMBERS FROM THIS CASE
$600 a month hiding in the bundle
Unbundling the hosting fee from the agency bill saved this merchant at least $600 a month, roughly $30,000 a year once paired with a no-retainer engagement model.
Paul Ryazanov · MageCloud · we maintain client infrastructure we deliberately do not own
Why Agencies Bundle Hosting, and Whose Problem It Solves
Bundled hosting solves three problems for the agency and none for the merchant. It creates recurring revenue that survives quiet months. It deepens the switching cost, because a merchant who wants to leave has to migrate infrastructure, not just hand over a repository. And it hides the margin, because nobody comparison-shops a line item they cannot see the real cost of.
I run an agency. I understand the temptation from the inside, and I still will not do it. The same reasoning sits behind why I refuse advance payments for hosting and why a 47-month hosting contract is a red flag. The shape of the bill tells you whose problem the arrangement was designed to solve. A bundled hosting fee is an agency cash flow solution wearing a convenience costume.
What Ownership Actually Looks Like
Ownership is specific and checkable. The hosting account is registered to your business email, not the agency’s. The payment method on file is your card. The agreement, the terms, and the renewal notices run between you and the vendor directly. Your agency and your developers have access because you granted it, through their own named accounts that you can revoke, not because they hold the only set of keys.
The same applies one layer down. The code lives in a repository your business owns, with the agency contributing through access you control. The domain is registered to you. The DNS is in your account. The analytics, Search Console, and ads accounts belong to your business with the agency added as a user. None of this prevents the agency from doing excellent work. It just means the work product accumulates in accounts that survive the relationship.
What This Costs the Merchant Who Skips It
The merchant in this story was exposed in two directions at once. Commercially, they were overpaying by at least $600 a month, because the bundled fee carried agency margin on top of the real server cost. Add the savings from moving off a retainer model and the annual number reached roughly $30,000. That is not optimisation at the edges. That is a salary.
Operationally, the exposure was worse. A merchant whose agency owns the hosting cannot fire the agency without a migration project. Every disagreement about quality, price, or priorities happens with the agency holding the server. Nine times out of ten nothing dramatic ever comes of it, and the relationship winds down politely when it winds down. But the structure means the merchant negotiates from weakness for the entire life of the engagement, and the agency knows it. I have watched stores stay with underperforming vendors for years purely because the infrastructure hostage problem made leaving feel impossible. The cheapest time to fix this is before there is any conflict at all.
How to Unbundle Without Burning the Relationship
If your current setup fails the ownership test, the fix does not require a confrontation. Open a hosting account in your name, with the vendor your agency recommends if you trust their judgement. Ask the agency to migrate the site into it as a normal paid project, then grant them the access they need to keep maintaining everything exactly as before. A good agency will not resist this, because a good agency was not depending on the hostage structure. We do this migration for stores regularly, and the work pairs naturally with a proper look at what the infrastructure should actually cost, because the bundled setups are almost always oversized as well as overpriced.
If the agency does resist, pay attention. The resistance is the information.
The One Rule to Take Away
It is fine to pay an agency to maintain your infrastructure. It is not fine for the agency to own it. Keep the agreement between you and the hosting vendor, keep the bill on your card, keep the credentials in your business’s hands, and let everyone work inside access you control. If you want help working out what your bundled setup really costs and what unbundling would look like, get in touch. The first conversation is the audit.