Self-hosted vs reseller hosting: when each makes sense in 2026

You're a freelance WordPress developer with 8 client sites. You're spending two hours a month managing five different hosting accounts because each client signed up with whoever had the best intro deal at the time. The renewal emails are staggered across three different cycles. You can't remember which client is on which cPanel version. You're starting to wonder if there's a better way to organise this.

The two options on the table are usually framed as "self-hosted" (each client has their own hosting account, you manage them from outside) versus "reseller hosting" (one master account, you provision sub-accounts for each client). The truth is the right answer depends on your specific situation, and the threshold where one model breaks down and the other becomes appropriate is more specific than the marketing copy suggests.

This piece walks through both models honestly, with the trade-offs that matter for small Indian agencies.

What "self-hosted per site" actually means

In the self-hosted model, each client signs up for their own hosting account (often with your guidance), and you're a developer / administrator with admin access. The hosting account is in the client's name, billed to the client.

This is the model we recommended for early-stage freelancers in the freelancer year-2 reality piece. It works well at small scale because:

• The client owns the hosting relationship. Clean if you part ways.
• You're not the billing intermediary. Less paperwork on your side.
• If a site is hacked, the blast radius is contained to that one account.
• You can pick the best host for each specific client's needs.

The problems show up at scale. Once you have 6+ clients on 3+ different hosts, your operational overhead climbs sharply. You're navigating multiple control panels, multiple support channels, multiple billing cycles. The cognitive switching cost is real.

What reseller hosting actually means

In the reseller model, you (the agency) buy a master plan from a hosting company. The plan comes with WHM (Web Host Manager), which lets you provision individual cPanel accounts within your master account. Each client gets their own cPanel with their own credentials, but everything sits under your one billing relationship.

You can rebrand the panel (white-label) so the client never sees the underlying host's branding. You can set resource limits per account. You typically pay one monthly fee to the underlying host and bill clients separately on your own terms.

Reseller hosting works well at moderate scale because:

• One bill, one dashboard, one support relationship with the underlying host.
• Standardised stack across all clients — same cPanel, same PHP versions, same backup tool.
• You can charge a markup on hosting and pocket the difference.
• White-labelling lets you present the hosting as part of your agency service.

The problems show up either at very small scale (overkill) or at very large scale (single-server bottleneck). And there are second-order issues we'll get to.

The threshold where each model breaks

This is the practical question.

Below 4-5 client sites: Self-hosted is almost always the right answer. The operational overhead of running reseller infrastructure isn't worth it for so few sites. Each client has their own account, you have admin access, you charge separately for maintenance.

6 to 15 client sites: This is the grey zone. Self-hosted starts to creak. Reseller starts to look attractive. The deciding factors:

• Do your clients want unified branding (white-label)? If yes, lean reseller.
• Do your clients want to own their hosting independently? If yes, lean self-hosted.
• Are you comfortable with the cash-flow implication of being the billing intermediary? If yes, lean reseller.
• Do you have enough technical comfort to manage WHM? If yes, lean reseller.

15+ client sites: Either reseller (if your clients are happy with a standardised setup) or a more sophisticated agency-tier plan that combines per-site billing with a unified dashboard. Pure self-hosted past 15 sites is operationally painful.

50+ client sites: You're probably at the size where dedicated infrastructure (a managed VPS cluster, a Kubernetes setup, or a serverless-WordPress platform) starts to make sense over traditional reseller. This is agency-scale.

The second-order issues nobody mentions

A few things that don't show up in the brochure-level comparison.

Reseller blast radius

If your reseller server has an issue — server-level downtime, IP-level blacklisting, performance degradation — every single client site is affected simultaneously. You become a single point of failure for your entire portfolio. The damage to your reputation from a single bad incident can be substantial.

The mitigation is to spread risk across multiple hosts (which defeats some of the reseller advantage) or to pick a host with strong infrastructure (which is the harder question). At the price point of reseller hosting, you're typically on shared infrastructure, which means the blast-radius risk is real.

Self-hosted credential sprawl

The other extreme: with 10 clients each on their own hosting account, you have 10 sets of credentials, 10 sets of billing dates, 10 different account recovery flows. Lose track of credentials for one and you can't help a client when something breaks.

Mitigation: a disciplined password manager setup. 1Password's "shared vaults" feature lets you organise credentials per client. Bitwarden Teams is similar. The cost is modest; the operational improvement is large.

Billing intermediary risk

In the reseller model, you pay the underlying host and bill the client. If the client doesn't pay you, you still owe the host. Over time, an agency accumulates AR balance and the cash-flow risk grows.

In the self-hosted model, the client pays the host directly. You're never the credit risk. Your AR is only the maintenance fee you charge, which is much smaller than the hosting bill.

For freelancers operating on thin margins, this difference can be meaningful.

A practical hybrid

The model we increasingly recommend for the 6-20 site range:

1. Each client has their own hosting account (self-hosted model, in their name, billed to them).
2. You use a centralised management tool like ManageWP, MainWP, or InfiniteWP to push updates, run backups, and monitor uptime across all sites from one dashboard. This gets you the "single pane of glass" benefit of reseller without the blast-radius risk.
3. All clients use the same host to standardise the operational experience. You're still managing 10 cPanel accounts, but they're all the same version with the same toolset.
4. You charge a per-client monthly retainer for the maintenance work, separate from the hosting bill that goes directly to the client.

This is what we call "agency-light" — most of the operational benefits of reseller, most of the financial cleanliness of self-hosted, no single point of failure across your portfolio. The downside is you can't white-label as cleanly as with traditional reseller.

When reseller still wins

Three scenarios where reseller is genuinely the right answer despite the blast-radius risk:

1. You want full white-label. Your agency brand is on the control panel. Clients log in to "Acme Hosting" and never see the underlying host. This requires reseller.
2. Your clients are non-technical and don't want hosting accounts of their own. They want one bill from you, period. Reseller makes this clean.
3. You're charging a substantial markup on hosting as part of your agency model. Reseller lets you pocket that. Self-hosted with pass-through pricing means the markup happens entirely on the maintenance retainer, which some agencies find harder to justify.

For these cases, accept the blast-radius risk and pick a reseller host with strong infrastructure. The traditional cPanel reseller plans from MilesWeb, Hostgator India, or similar work. growhost doesn't currently offer traditional reseller — our agency-tier model is closer to the hybrid we described above.

What about cloud-native?

If you have developer skills on your team, the modern alternative is a cloud platform — managed Kubernetes, serverless WordPress, or a managed cloud platform like growhost Apps, Cloudways, Spinupwp on top of DigitalOcean.

The advantage is real: better performance, infrastructure-as-code, version control for your hosting setup, the ability to scale specific sites independently.

The disadvantage is operational complexity. If you don't have a dev-ops mindset on the team, cloud-native is harder to operate than traditional reseller. We see this trip up smaller agencies that adopt cloud-native because it's fashionable, then struggle when their developer leaves and nobody else can operate the infrastructure.

The honest recommendation: stay on traditional WordPress hosting (self-hosted or reseller) until you have a clear reason to move to cloud-native. That reason usually has to do with specific performance requirements, deployment workflows, or scale that traditional hosting can't deliver.

For our take on the per-tier pricing of WordPress hosting, see the pricing page. And for the longer guide on freelancer-specific hosting setup, the freelancer year-2 reality piece covers the broader workflow questions.

The reseller-vs-self-hosted question is a useful one because it forces you to confront the operational reality of your business. Whichever model you pick, the discipline matters more than the choice.