hosting
agency
wordpress

Hostinger for multiple client websites: plans, access and cost per website

By Sanjay GuptaUpdated 8 Oct 20267 min read
A small team working on laptops around a table
Photo: Startup Business People Working on Laptop by Rawpixel Ltd, CC BY 2.0, via Flickr

Disclosure: Some links to Hostinger on this page are affiliate links. If you buy through them we may earn a commission, at no extra cost to you. It does not change which plan we recommend.

"Unlimited websites" is the most misread phrase in hosting. It means unlimited entries in a list. It does not mean unlimited capacity, and on a shared plan every site you add is drinking from the same small cup.

If you build sites for clients — as a freelancer, a small studio or an agency — this is the maths that actually matters, plus the access and ownership questions nobody thinks about until a client leaves badly.

The resource pool is shared, and that is the whole story

On the Unlimited plan you get 2 CPU cores, 3 GB of RAM and 600,000 inodes. That allocation is for the account, not per website. Add fifteen client sites and all fifteen share those two cores.

PlanCPURAMInodesSensible site count
Premium1 core2 GB400,0002–3 light sites
Unlimited / Business2 cores3 GB600,0005–8 brochure sites
Cloud Startup2 cores4 GB2,000,00010–15 brochure sites
VPS KVM 22 dedicated cores8 GBNo inode cap15–25, with a panel
VPS KVM 44 dedicated cores16 GBNo inode cap30–50

"Brochure site" means a WordPress site with modest traffic and no store. One WooCommerce store counts as roughly three of them. One store running a sale counts as all of them.

Cost per website, which is the number you should quote from

Taking promotional pricing over the term:

  • Unlimited at ₹249/month with 6 sites: ₹42 per site per month.
  • Cloud Startup at ₹599/month with 12 sites: ₹50 per site per month.
  • KVM 2 VPS at ₹799/month with 20 sites: ₹40 per site per month, before your own time.

The numbers land close together, which tells you cost is not the deciding factor. Risk and access are.

The two risks of putting clients on one account

One bad site takes down every site

They share CPU, RAM and entry processes. A client who installs a cheap plugin with a runaway cron, or whose site is hit by a bot wave, consumes the pool — and your other clients get 503 errors for a problem that has nothing to do with them. You then have to explain downtime you did not cause to people you did not charge for it.

One compromised site can reach the others

Sites on the same account commonly share a filesystem space. Cross-site infection after one outdated plugin is compromised is a real pattern, and the clean-up is not one site's worth of work. If you are keeping a client's leads or customer data, that is their data you are putting next to someone else's risk.

The question is not whether one shared plan can host ten client sites. It is what happens to the other nine on the day one of them has a problem.

Access: the part that gets awkward

On an ordinary shared plan, hPanel is one login. There is no clean way to give a client control of only their own site's hosting, which leaves you as the permanent middleman for every DNS change, SSL question and backup request. That is unbilled work forever.

Hostinger's answer is Hostinger Pro, which is free to join and designed for exactly this. The parts that matter:

  • Access sharing per site — share a specific website with a client or team member, with permissions, instead of handing over the whole account.
  • An unbranded client dashboard, so clients see a clean view rather than your supplier's branding.
  • Managing clients' own accounts — you request access and the client verifies it, so the hosting stays in the client's name while you do the work.
  • A 20% referral commission on annual plans clients buy through you, which is a legitimate margin on work you were doing anyway.
  • Agency plans above the standard tiers, starting around ₹2,499/month, when you want dedicated capacity.

That fourth point is the important one architecturally, and it leads to the recommendation.

What we actually recommend

Client sites belong in the client's own account

Each client buys their own plan, in their own name, on their own card. You get delegated access. It is slightly more admin and it is the right answer for four reasons:

  1. No shared blast radius. Their traffic spike is their problem, not six other clients'.
  2. Clean exits. When a client leaves — and some will — you remove your access. No migration, no hostage situation, no uncomfortable email about who owns the files.
  3. No liability. You are not the data controller for their customers by accident.
  4. No float. You are not paying for hosting months before invoicing it, and you are not the one chasing a renewal that lapsed.

If the client cannot or will not hold the account, write into the contract who owns it and what happens on termination. The same discipline applies to domains, ad accounts and analytics: the client owns the account, you hold access.

Your own sites go on one plan

Your agency site, your landing pages, your staging copies, your experiments. One Unlimited plan, no client risk, cheap.

Scale on a VPS, not on more shared plans

Once you genuinely host 15+ sites as a service you are selling, a VPS with a control panel is the right architecture: dedicated CPU and RAM, no inode ceiling, your own backup policy, Redis, and per-site isolation if you set it up properly. At that point hosting is a product you sell and should be priced accordingly — it is not a favour anymore.

What to charge for hosting

If you are going to carry client sites, price it as a service rather than reselling capacity at a markup. Capacity is a commodity and your margin on it will always be thin; the thing clients actually value is that someone is responsible when the site breaks.

A workable structure in the Indian market: hosting at cost or lightly marked up, plus a monthly maintenance fee covering updates, backups, uptime monitoring, security scanning and a short report. That fee is defensible because it maps to work the client can see. "₹800 a month for hosting" invites a client to search for a ₹149 plan and ask why; "₹2,500 a month so your site is updated, backed up, monitored and fixed within four hours" does not, because nothing on a hosting pricing page competes with it.

Things to standardise before you host anyone

  • Backups you control. The host's backups protect the server. You want off-server copies you can restore without a support ticket. For a store, daily is the minimum.
  • A staging site per client. Updating plugins on a live client site is how a Tuesday becomes a bad Tuesday.
  • A monthly maintenance window, billed. Updates, backups check, uptime report, security scan. This is the difference between hosting being a cost and hosting being a retainer.
  • An uptime monitor with alerts, so you find out before the client does. That one habit protects more client relationships than any technical choice on this page.
  • A written SLA. What you guarantee, what you do not, and how fast you respond. "Unlimited websites" on a ₹249 plan is not an SLA.

A worked example: six client sites

Say you look after six small business sites — four brochure sites, one with a small store, one that runs ads to landing pages. Two ways to structure it.

Option A — one Unlimited plan in your name, ₹249/month. Cost per site is ₹42. You hold one login. Every DNS change, SSL question and backup request comes to you. The store counts as roughly three brochure sites, so you are already at about the plan's sensible ceiling with six. When the client running ads has a good week, everyone shares the slowdown. When one of them leaves, you are extracting their site from an account that also holds five others.

Option B — six client-owned plans, your access delegated. Each client pays ₹149–249 directly. You earn a referral commission on their annual plans, you charge a maintenance retainer, and your exposure is zero. Nothing you host can take down anything else you host. When a client leaves you remove your access and the conversation ends there.

Option A saves roughly ₹1,000 a month across six clients. Option B removes an entire category of risk and turns hosting from an absorbed cost into a billable service. We have never seen anyone regret Option B, and we have seen several people regret Option A — always on the same day, and always because of a site they did not build.

Verdict

Unlimited or Cloud Startup for your own portfolio of sites. Client sites in the client's own account, with delegated access through Hostinger Pro. A VPS once hosting is something you sell rather than absorb.

Hosting ten client sites on one ₹249 plan looks like a clever margin until the month it is not. The agencies that make money on this charge for maintenance rather than reselling capacity. If you want to compare the VPS tiers before committing, start with the KVM plan breakdown.

For the client work itself, three things earn their place in the browser: a password manager, so credentials are shared properly rather than pasted into chat; SEO extensions for auditing a site you have just inherited; and the password generator built into that manager for every new admin account you create. The marketer shortlist covers the rest.

Frequently asked questions

How many websites can I really host on Hostinger's Unlimited plan?

Five to eight light WordPress sites is a sensible ceiling. The plan gives 2 CPU cores, 3 GB of RAM and 600,000 inodes to the account as a whole, not per site. One WooCommerce store counts as roughly three brochure sites, and one store running a sale counts as all of them.

Is it safe to host client websites on one shared account?

It carries two real risks. Sites share CPU and RAM, so one client's runaway plugin causes 503 errors for everyone else. And sites on one account commonly share filesystem space, so one compromised site can reach the others. Both are reasons to put client sites in the client's own account.

Does Hostinger have an agency or reseller option?

Hostinger Pro is free to join and built for this. It offers per-site access sharing with permissions, an unbranded client dashboard, the ability to manage a client's own account once they verify your request, a 20% referral commission on annual plans, and agency plans starting around ₹2,499 a month.

Should client hosting be in my name or the client's?

The client's, with delegated access to you. It removes shared blast radius, makes exits clean, keeps you out of the data-controller role for their customers, and means you are not floating hosting costs. If the client cannot hold the account, write ownership and termination into the contract.

Related on Single Tab Browser

Go deeper on the extensions mentioned in this post.

More from the blog

Posts on nearby topics, so nothing on the blog sits without a way in.

Browse the directory