Why your hosting bill is confusing, and how to read it
Hosting invoices mix infrastructure, services, add-ons and support into lines nobody explains. The six kinds of line and which to question.
The short answer
Hosting invoices are confusing because they mix four different things, infrastructure, services, add-ons and people’s time, into lines that nobody explains. The way to read one is to sort every line into one of six kinds and ask of each: is this infrastructure, a service or time, and what would it cost bought directly? Infrastructure should match the provider’s public price. Services should have a name and a purpose. Time should have a defined scope. Anything that fails those tests is the line to question.
The six kinds of line
| Kind | What it is | What to check |
|---|---|---|
| 1. The plan | The base hosting or platform tier | Matches the provider’s public price for that tier; the tier fits the site |
| 2. Usage | Bandwidth, requests, function calls, storage beyond the plan | Occasional is fine; recurring means the wrong plan or a wasteful site |
| 3. Domains and certificates | Registration, renewal, DNS, certificates | Registrar price for domains; certificates usually free on modern platforms |
| 4. Add-on services | Backups, CDN, security layer, monitoring, email, search | Each named, each used, each priced like the provider prices it |
| 5. Management or support | Someone’s time to look after it | A written scope: what is done, how often, what response times |
| 6. Taxes and fees | VAT, payment fees | Correct rate, correct entity |
Reading your bill in ten minutes
- Identify the provider and plan behind line one, and look up the public price. If you cannot identify the provider, that is the first question to ask.
- Look at usage lines across three months. Recurring overages are a decision waiting to be made.
- Check every domain line against the registrar’s price, and ask why any certificate is charged.
- List the add-ons and ask which are used. Unused add-ons are the easiest savings on any bill.
- Find the management line and ask for its scope in writing. No scope, no line.
- Check whose name the account is in. If it is not yours, that matters more than the total.
What a clear bill looks like
Hosting from the provider, at the provider’s price, in an account whose holder you can name; if that holder is your supplier, you can ask what the provider charges and the transfer to your own name is in writing. Domains from the registrar, in your account. A separate invoice from your partner for maintenance and support with the scope attached. Add-ons named and justified. No certificate line on a modern platform. Usage lines that are rare and explained. When each party bills you directly for what they provide, the confusion disappears, and so does the invisible margin.
What this means for you
Sort each line into one of six kinds, check infrastructure against public prices, demand a scope for management and a name for every add-on, and make sure the accounts are yours. Ten minutes with last month’s bill usually finds an unused add-on, a certificate that should be free or a management fee with no definition. The clear bill is the one where each party charges you directly for what they actually provide.
Frequently asked questions
Our agency bills hosting as one line. Is that normal?
Common, and worth unpacking. Ask what the line contains: which provider, which plan, what the provider charges, and what the difference pays for. If the difference is a defined maintenance scope, fine, and it should be labelled as such. If it is unexplained margin, ask for hosting in your own account at the provider's price.
We pay for an SSL certificate every year. Should we?
For an ordinary business website, no. Automated certificates from free authorities are standard on modern platforms and are what most of the web uses. Paid certificates have niche uses. A yearly certificate line on a small business bill is usually a leftover or a mark-up.
Usage overages appear every month. What does that mean?
That the plan is the wrong size, or the site is wasting resources. A recurring overage costs more than the next plan tier or than fixing the cause, such as oversized images or a script polling the server. Either resize the plan or fix the consumption; do not keep paying the penalty rate.