Four ways to bill for hosting, and the one number sitting under all of them.
There are four billing models agencies and freelancers actually use for hosting and ongoing site work: pass it through at cost, mark it up, wrap it into a monthly care plan, or roll the whole build into a flat subscription. Each one is legitimate. Each one has a specific failure mode that surfaces about six months in, usually as a client who feels nickel-and-dimed or a developer quietly working for free. Pick the model that matches how much ongoing labor you actually expect to do, price it against real numbers instead of a guess, and write down the scope before the first invoice goes out. Underneath every one of these models is a hosting cost per site, and the agencies that price well are the ones who know that number cold. Devani Hosting exists to make it a flat, known figure rather than something you look up per client.
How to structure the hosting line, model by model.
Start here. Match one of these to how much support work the account will really carry, then hold the scope. The compressed version of each, and the trap each one springs, is below.
- Pass-through at cost. You buy the hosting, the client pays exactly what it costs, you do not touch the number. It is the most transparent option on the list. It also covers only the server, none of the support work around it, so on its own it is a slow bleed.
- Marked-up hosting. Buy through a reseller account and bill the client more than it costs you, commonly $10 to $40 a month over a basic shared plan. Legitimate as long as it is not hidden, but it is still a hosting line, not a maintenance plan, and clients often assume the two are the same.
- Monthly care plan. One fee that bundles hosting, updates, backups, monitoring, and a defined edit allotment, commonly up to 30 minutes of changes a month. This is the first model that actually prices the support burden instead of ignoring it. It lives or dies on where "included" ends.
- Flat website subscription. Roll the build and the ongoing work into one monthly fee from day one, sometimes with no upfront invoice at all. It meets a client who cannot absorb a $4,000 project cost, but the financing risk sits on your side, so it needs a minimum term in writing.
Pass-through and markup bill the hosting, not the work around it.
Pass-through is the simplest thing you can do: a $15 plan is billed at $15, no markup, no margin. The appeal is real. A client who asks "what am I paying for" gets an answer that matches an invoice they could look up themselves, and some freelancers on fixed-price projects use it specifically because they do not want hosting billing to be part of the relationship at all. The problem is what it does not cover. Hosting itself is rarely the expensive part of keeping a site running. The expensive part is the work around it: the "the site is down" call at 6pm, the plugin update that breaks checkout, the client who wants a phone number changed same day for free because "you handle our hosting." If pass-through is your only billing line, all of that support is either unpaid or billed in small invoices with small arguments attached about whether ten minutes counts.
Marking hosting up fixes the margin but not the coverage. Buying hosting yourself and billing more than it costs is common and it is not dishonest as long as it is not hidden. The client gets one point of contact instead of a hosting company's ticket queue, and you get a small, predictable margin on infrastructure you already manage for other clients. The risk is the one that shows up any time you resell a commodity: a client who compares your $35-a-month hosting line to a $5 plan they saw advertised and wants to know why they pay seven times more for "the same thing." You need a real answer ready, support, monitoring, the fact that you are the one who gets the 2am alert, and if you cannot articulate that value, the markup reads as a markup and nothing else. Either way it is still a hosting line, not a maintenance plan. If you are weighing which billing shape fits your roster, how a reseller markup compares to white-label and fully managed billing is worth reading before locking one model in over the others.
A care plan with no written boundary is just unlimited free labor with a retainer attached.
Care plans and subscriptions, and what they actually run.
The last two models charge for the work, not just the server. That makes them the ones most agencies who do this well actually land on, and also the two easiest to underprice. The ranges below are real ranges because the work behind them is a real range.
| Model | Typical monthly | What it prices, and the watch-out |
|---|---|---|
| Pass-through at cost | The host's exact price | Total transparency, zero margin; every support request is billed separately or absorbed for free |
| Marked-up hosting | $10 to $40 markup | Predictable margin on infra you already run; needs a clear value answer when a client compares it to a $5 plan |
| Care plan, basic brochure site | $50 to $100 | Bundles updates, backups, monitoring, and a small edit allotment; guard where the allotment ends |
| Care plan, higher-touch or ecommerce | $150 to $300, up to four figures | More traffic, more stakeholders, more change requests, all of it real work |
| Flat website subscription | $100 to $200 and up | Recurring from day one; easy to underprice because the sticker shock never happens, so it needs a minimum term |
| The hosting line underneath | Devani Hosting: free tier, flat per-site paid plans | The one cost that feeds every row above, a known figure instead of something you look up per client |
A care plan is the first model that prices the support burden instead of ignoring it, and it is recurring revenue that does not depend on landing a new project every quarter. Its failure mode is scope. A care plan without a clear boundary on what counts as included work turns into unlimited free labor with a monthly retainer attached, because the 30-minutes-a-month allotment quietly becomes three hours and the plan stops making money. A subscription goes further and smooths out the feast-or-famine cycle by starting the recurring revenue immediately, but the financing risk moves onto your side of the table. A client who cancels after four months has cost you real, unrecovered labor, so a minimum term, an early-termination clause, or both is what makes the math work at all. Terms matter here in a way they do not for the other three models.
Whatever model you pick, the scope is what actually prevents disputes.
The thing that heads off arguments later is not the pricing model, it is whether both sides know, in writing, where the line sits. Spell it out before the first invoice:
- What the base fee includes. Hosting, updates, backups, monitoring, and the specific size of the edit allotment, whether you track it in minutes or in requests. Pick the unit you actually measure.
- What is a "quick edit" versus billable project work. A text change or a swapped image is quick. A new page, a new integration, a section redesign, or anything that needs its own testing pass is a project, billed separately at your normal rate, not absorbed into the plan.
- The response time you are actually committing to. "We'll get to it" is not a service level. "Same business day for a site-down issue, within 48 hours for a routine change request" is, and it is specific enough that both sides know what a broken promise looks like.
- What happens when the allotment runs out. Does extra time roll over, get billed hourly, or wait until next month? Decide before someone asks mid-project, not during it.
Writing this down protects you as much as the client. The unpaid-support trap always starts the same way: vague, well-meaning language in the sales conversation ("don't worry, we'll take care of you") turns into a client who messages every time something looks slightly off, expecting it handled immediately and for free, because nothing in writing ever told them otherwise. It is rarely bad faith. It is an honest assumption based on genuinely ambiguous language nobody corrected at the start. The fix is not to sound less helpful, it is to be specific instead of reassuring. "We monitor your site and handle updates and backups, and quick content edits up to 30 minutes a month are included; anything beyond that is billed at our standard rate with your approval first" says the same thing as "we'll take care of you," except it holds up under a busy month.
Knowing your own hosting cost turns a care plan from a guess into arithmetic.
Here is the part that is easy to skip. A lot of the guesswork in pricing a care plan comes from not actually knowing what hosting costs across your client roster. If every site is on a different plan, a different host, or a reseller account whose pricing shifts with usage, it is hard to build a care plan with real margin, because the cost side of the equation keeps moving under you. An agency that quotes a flat $75-a-month care plan without knowing whether the underlying hosting for that specific site costs $8 or $28 is guessing at its own margin, and guessing at margin across dozens of sites compounds into real money left on the table, or plans that quietly lose money on the higher-traffic accounts. Fixed, predictable per-site hosting cost is what lets you defend a number. If your hosting cost is the same known figure across every site, pricing a $75 or $150 plan on top of it is arithmetic. If it varies site to site in ways you have to look up, it is a guess repeated across your whole client list.
What a managed platform takes off the billing math.
One flat per-site cost
Devani Hosting runs at a flat, predictable per-site cost with a free tier to start, so the hosting line in any care plan or subscription is a figure you already know rather than something that shifts depending on which reseller tier a client happens to sit on. The cost side of the equation stops moving, which is the whole reason margin gets hard to defend.
Every client site in one login
Each site sits in one dashboard instead of a different host, a different reseller panel, or a one-off VPS a past developer set up and never documented. That "where does this client's site even live" tax eats care-plan margin without ever showing up as its own line item. Paid plans add the white-label tooling built for a roster, and if your whole roster runs this way, consolidating onto one system is where the real time savings live.
Small edits without opening the site
Devani connects to your own ChatGPT or Claude account natively, nothing to install, so a client's small text or layout request can often get handled through the assistant instead of a developer opening the site for ten billable minutes. That is precisely the kind of request that burns through a 30-minute edit allotment faster than a plan accounts for.
Worth stating the limit without softening it: Devani Hosting runs sites built on Devani. Point an existing WordPress client's DNS at it and nothing carries over, not the theme, not the plugin stack, not the content already on the site. It fits new client builds, or a roster you are genuinely willing to move over time, not a drop-in swap for hosting you already run elsewhere. The CMS underneath is free and open-source too, so nothing about picking it locks you to the managed side specifically.
What people ask before setting a hosting bill.
Should I charge clients for hosting at all?
Yes, in almost every case, but be clear about what the charge is really for. Pure pass-through at cost is honest and simple, but it only covers the server, not the support work around it. If you are the person handling updates, the down-at-6pm calls, and the quick edits, the hosting charge should either carry a markup or be folded into a care plan that actually prices that labor. Billing nothing for hosting while absorbing all the support around it is how developers end up working for free.
How much should I mark up hosting for clients?
A common range is $10 to $40 a month over a basic shared or entry-level hosting cost, with higher-touch agencies charging more when they bundle in faster support response or their own monitoring. The markup is defensible as long as it is not hidden and you can articulate the value: one point of contact instead of a ticket queue, and someone who gets the 2am alert instead of the client. If you cannot articulate that, the markup reads as a markup and a price-shopping client will push back.
Should hosting be included in a maintenance plan or billed separately?
Either works, as long as the plan documents which one you chose. Bundling hosting into a single monthly care fee is cleaner for the client and gives you recurring revenue that prices the support burden. The critical part is not where hosting sits, it is defining the edit allotment, the response time, and what counts as billable project work versus an included quick edit. A plan without those boundaries turns into unlimited labor for a fixed fee regardless of how the hosting line is structured.
Is a flat website subscription a good way to bill clients?
It works well for clients who can absorb $100 or $200 a month far more easily than a $4,000 upfront invoice, and it starts recurring revenue immediately. The risk is on your side: if you are financing the build cost over monthly payments, a client who cancels after four months leaves you underwater on unrecovered labor. It needs a contract with a minimum term, an early-termination clause, or both, and an honest check that the monthly number actually reflects the build effort, because subscriptions are easy to underprice when the big sticker number never appears.
Build your care plan on a hosting number you already know.
Nothing to migrate today. Devani Hosting has a free tier and a flat, predictable per-site cost, so the hosting line under your next client build is arithmetic instead of a guess.