Margin Brief
Static client sites are the best accounts you will ever bill
A hand-built or generator-built site is the account that never rings, which makes the only hard part the conversation about why it still costs money every month.
Straight answer first
Put static client sites on a Launch plan and serve the files over LiteSpeed with free SSL, deploying by SFTP or Git. These are the highest-margin accounts on a reseller shelf: near-zero resource use, no plugin surface, and almost no support volume.
The rest of this page is about keeping them that way: why the margin is so good, how to deploy a dozen of them without adopting a build platform, what to say at renewal when the client points out that it is only files, and what the plan leaves room for.
Written by the Hosting Seller staff · Checked 4 August 2026
Free
Move-in, done by our staff
24/7
Answered by people, for you and them
Daily
Backups across every account
$0
Charged at setup, on any pack
Static files on a LiteSpeed and NVMe stack go about as fast as web content can go. What the static-hosting startups actually sell is workflow convenience layered on performance that ordinary hosting already provides.
For a reseller that convenience is worth much less than it looks, because you already have a panel, a billing system and a support process. What you want from a static client is exactly what these accounts give you: revenue with no operational tail.
Why these are your best margin
There is no database to grow, no plugin to update, no version to keep current and no admin login to be compromised. The account uses a little disk and serves files from cache.
That means the cost you actually care about, which is support time, is close to nothing. A static account can sit on your book for five years and generate one ticket, usually about an email address.
It also means overselling is entirely safe here. A shelf of static sites claims a fraction of what you allocate and never claims it all at once.
Deploying a dozen without adopting a platform
Build locally or in CI and push the output. rsync over SSH, SFTP, or a Git pull on the server all work, and Hugo, Eleventy, Astro and the rest are simply producing files.
The pattern that scales for a small agency is one account per client with a deploy key, and a single script that knows how to push any of them. That is a morning of work and it removes the temptation to log in and edit something by hand.
Keep a staging path or subdomain for anything a client reviews before it goes live. It costs nothing on an account that is already near idle.
The renewal question you will be asked
Sooner or later a client asks why they pay monthly for what is, in their words, just some files. It is a fair question and it deserves a real answer rather than a defensive one.
What they are buying is the certificate that stays valid, the backups that go back, the mailboxes on their domain, the DNS that answers, and somebody who picks up when it does not. The file serving is the cheapest part of the arrangement.
Say it in those terms once and the question stops recurring. Avoid it, and the client eventually finds a free tier, discovers what is not included, and comes back in a worse mood.
The plan, and what it leaves room for
The plan for this is Launch. Files served over LiteSpeed, a free certificate, a move-in handled by our staff, and mailboxes on the client's own domain already in the price.
The things a static site eventually wants live here naturally: somewhere for a form to post, a contact script, a redirect, a custom error page, an email address that is not a forwarder to a personal inbox.
And there is no proprietary layer to unlearn. No build-minute quota, no bandwidth band, no house vocabulary, and a backup that restores onto any cPanel host anywhere if the client ever leaves.
The account we make least from
A static site on a Launch plan is not where our margin is, and we recommend it anyway because a reseller with a book of quiet accounts is a reseller who stays in business. Sold the wrong plan, you would notice within a year.
Backups run every day on every plan, and putting a file or a database back takes one click from the panel.
- No plugin surface and no admin login to defend
- Deploy by SFTP, rsync or a Git pull
- Nothing proprietary to unlearn if a client leaves
- The renewal price is the price you quoted
Why Hosting Seller
On every plan, as standard
The plan behind this page
Launch serves static files over LiteSpeed with the certificate, the move-in and the mailboxes already in the price.
Almost no support tail
No database, no plugins, no updates. These accounts generate revenue and very little else, which is the definition of good margin.
Deploy how you already work
SFTP, rsync over SSH or a Git pull on the server. No build-minute quotas and no house vocabulary to learn.
Portable if a client leaves
A full backup from the panel restores onto any cPanel host anywhere, which is a fair thing to be able to promise.
A supplier you can name
IGI Security Services Ltd, registered in England and Wales, with a public record behind the accounts you resell.
Room to grow into
Forms, scripts, redirects and mailboxes are all on the same account, so a static site that needs one more thing does not need a new plan.
Price Tags Compared
How we compare with the household names
Typical sign-up and renewal prices across the market, set next to ours — the second number most comparison charts leave off.
| Line item | Hosting SellerBest seller | Typical big-brand host | Typical budget host | Typical loss-leader |
|---|---|---|---|---|
| Entry price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Price at renewal / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Renewal price on the entry plan is unchanged | ||||
| SSL on every plan | ||||
| Site migration included | ||||
| The entry plan uses NVMe storage | ||||
| Entry plan gets a backup daily | ||||
| Live human support, 24/7 |
*The number in our column is the cheapest plan on our shelf, priced on an annual term and pulled live from the very catalogue that feeds the pricing page, so it cannot drift out of date. Other columns show the ranges shared hosting tends to advertise inside each bracket: introductory rates that normally ask for a one-to-four-year commitment, then climb once that term expires. Naming individual competitors and printing their prices is something we have stopped doing. A figure we cannot re-check on the day you read it has no business sitting in front of you. So compare us with whoever you are genuinely weighing up, and read the renewal line first. That line tells you more than the headline ever will.
First Steps
From choosing to live
- 1
One account per client, one deploy key
Keep the boundary at the account rather than the folder. It costs nothing on this workload and it means a client can be handed over or removed cleanly.
- 2
Write the push script once
A single script that can deploy any client's build removes the temptation to log in and edit a live file by hand, which is where these accounts go wrong.
- 3
Answer the renewal question in advance
Put the certificate, the backups, the mailboxes and the support in the quote as line items. The client is not paying for file serving and should not think they are.
In the Box
Packed with every plan
- SSH, Git and Composer on the plans built for developers
- Free SSL on every site you host, reissued before it lapses
- LiteSpeed caching running at the server rather than by plugin
- NVMe SSD storage on every shelf, not just the top one
- Daily backups with restores you run yourself
- Mailboxes on the client's own domain, with spam and virus filtering
- Custom error pages and redirects from the panel
- Nothing added at setup, no joining fee ever
- Site migration handled by our staff at no charge
- A 30-day money-back guarantee on hosting plans, 7 days on reseller
Across the Counter
Things people ask us all the time
Why put a static client on ordinary hosting rather than a static platform?
Fewer proprietary layers, and a support process you already have. No build-minute quotas, no bandwidth bands, no house vocabulary for your staff to learn. The things a static site eventually wants, such as a form endpoint or a real mailbox, are already on the account.
Can one script push every client's build?
Yes, and that is the pattern worth building. Keep one account per client with its own deploy key, then write a single script that knows how to push any of them over rsync, SFTP or a Git pull. Hugo, Eleventy, Astro and the rest are all just producing files, and a morning spent on that script removes the temptation to log in and edit something live.
What do I say when a client asks why files cost money monthly?
Itemise what they are actually buying: a certificate that stays valid, backups that restore, mailboxes on their domain, DNS that answers, and somebody who picks up when it does not. File serving is the cheapest part of the arrangement and the least of what you provide.
Can a static client leave without a fight?
Yes, and being able to say so is worth something. A full backup can be pulled from the panel at any time and restores onto any cPanel host anywhere. The domain stays registered in the client's name and can move to another registrar once the standard sixty-day window has passed.
Read next
Wiki Hosting
A shared knowledge base as a client account, and what it needs that a brochure site does not.
Wix vs WordPress
The argument a client will bring you for a closed builder, and the answer that keeps the work in-house.
Web Hosting
cPanel accounts on NVMe disks, with SSL, the move-in and year-one domain included.
Plesk Reseller Hosting
Reseller accounts on Plesk for teams who prefer that workflow.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Fill the shelf with quiet accounts.
Reseller accounts with SSH and Git, free certificates, daily backups, and nothing charged at setup.
See Web Hosting plans