Hosting for Freelancers and Agencies: Many Sites, One Plan
10 November 2026 · 7 min read
You build or look after websites for clients, and each one lives on a different host with its own password and a renewal date you never remember. Good hosting for freelancers and agencies solves this by putting client sites on one plan. It works well as long as every site gets its own folder, database and users, the domain stays in the client’s name, and you know how to restore one site without touching the rest.
Should you host client sites on one plan?
Yes, for small and mid-sized sites such as company sites, portfolios and blogs, provided you separate them properly. You get one control panel, one invoice, one renewal date and one backup system for every site.
Know the limits from day one:
Resources are shared. A hosting account runs within a set allowance of CPU, memory and disk I/O, and every site inside it draws from that allowance. One client’s traffic spike can slow the others down.
Security is partly shared. Sites inside one cPanel account run as the same system user. If an outdated site gets compromised, the attacker may be able to reach the neighbouring sites’ files in that account.
The bill is in your name. Clients rely on you to renew, which suits ongoing care better than a one-off project.
A practical rule: keep on your plan the sites you actually manage and keep updated, and move any large or sensitive site, or one whose owner wants to own the hosting, to its own account.
How do I add each client site in cPanel?
Add each client site from the Domains tool in cPanel and give it its own folder. That tool replaced the old separate Addon Domains and Subdomains screens, but people still call the result an addon domain.
An addon domain is an additional domain owned by the same cPanel account and stored in its own configurable directory, as cPanel’s documentation explains. The steps:
Register the client’s domain, or point it at your server through DNS (see the ownership section below).
In cPanel, go to Domains → Create A New Domain and enter the client’s domain.
Untick “Share document root” and choose a clearly named folder, such as clients/example.com. Sharing the document root makes the new domain show your own site, and the setting is permanent.
Install WordPress on the new domain with WP Toolkit, or migrate the client’s existing site into it.
Check that the free SSL certificate is issued once the domain points to the server.
Pick a folder naming scheme on day one; by client ten you won’t remember which folder is whose.
How do I keep client sites separate in one account?
Separate them at four levels: database, WordPress users, file access and email.
Item
What to do
Why
Folder
One folder per site
Files never mix; moving or restoring one site is easy
Database
One database and database user per site
A mistake on one site cannot touch another’s data
WordPress users
A personal login for each person, with the right role
You know who did what and can revoke one person alone
File access
An FTP account limited to the site’s folder, when needed
The client never sees other clients’ files
Email
Mailboxes on the client’s own domain
Each business’s mail stays separate; sending limits apply per domain
WordPress users: never share one password
Every WordPress site has its own user list and roles. According to the WordPress roles documentation, an Administrator has access to all administration features of a site, while an Editor can publish and manage posts, including other users’ posts. Keep an Administrator account for yourself, give the client and their team personal accounts with only the role they need, and turn on two-factor authentication with a reputable plugin.
Don’t give clients your cPanel password
Your cPanel password opens every site, file, database and mailbox in the account, not just the client’s site. If a client or their developer needs to upload files, create an FTP account limited to that site’s folder and delete it when the work is done.
Email and sending limits
Create mailboxes on each client’s domain and set up authentication records per domain, as covered in our guide to business email on your own domain. At Start Bigger the outgoing limit is 100 messages per hour per domain, so client sites don’t share a single allowance, but any client’s email campaigns still need a dedicated sending service.
How do I test changes without breaking a client’s site?
Use staging: an exact copy of the site on a subdomain where you try updates and changes before they reach the live site. WP Toolkit in cPanel creates the staging copy by cloning, then pushes the files and database back to production and creates a restore point automatically so you can roll back.
A workflow for several sites:
Update small plugins directly, with a recent backup in place.
Test big updates (theme, page builder, shop plugin, PHP version) on staging first.
Check the key pages on staging: home, contact form and checkout, if there is one.
Push to live at a quiet time, then delete the staging copy so it doesn’t go stale.
WP Toolkit also lists every WordPress site in the account in one place, so pending updates are easy to spot.
How do I protect client sites with backups?
Rely on daily backups, and learn to restore a single site. Every Start Bigger plan takes a daily JetBackup backup of files, databases, email and account settings, kept for up to 60 days depending on the plan, as set out in our backups policy.
The key point when you manage several clients: don’t restore the whole account to fix one site. A full account restore rolls every site back to the backup date, and other clients lose whatever they added since. Instead, restore just the affected site’s folder and database from JetBackup inside cPanel.
Two more habits:
Download your own copy of a site before any major change. Backups are an extra layer of protection, not an absolute guarantee.
After a hack, do a full clean-up, not just a file restore, or the hole may stay open.
Who owns the domain and the site: you or your client?
The client owns them; you are the technical manager. The domain should be registered with the client as the registrant, using an email address they actually receive. ICANN’s registrants’ benefits and responsibilities state that the registrant assumes sole responsibility for the registration and use of the domain and must provide accurate, up-to-date information.
A domain in your name makes you a party to any later dispute or move, and the registrar may ask for email confirmation after registration or a change of details. Under our domains policy, failing to confirm within 15 days may lead to the domain being suspended until you do, so if that email reaches nobody, the client’s site goes down. We cover each stage in the domain lifecycle guide.
Keep a simple record per client: domain and renewal date, where DNS is managed, folder and database names, and whose name each premium plugin licence is in. It saves hours if a client later takes their site elsewhere (handover gets its own guide).
Which hosting for freelancers and agencies fits your client count?
Choose by how many sites you expect within a year, not only today’s client list. All Start Bigger hosting plans are annual and use cPanel; the main difference is the number of websites:
Plan
Websites
Good for
Business
3
A freelancer starting out: your own site plus two clients
Professional
10, plus SSH, Node.js, Python and PostgreSQL
A busy freelancer or developer who needs command-line tools
All-in
25, plus SSH, Node.js, Python, PostgreSQL, a monthly report and an onboarding call
A small agency with a larger client list
Every plan includes LiteSpeed with LSCache, NVMe storage, Redis and Memcached, Imunify360 and Monarx malware scanning, CloudLinux account isolation and free migration of your current site. If your client sites are scattered across hosts, read how to migrate WordPress without downtime before you start.
Your plan is the wrong home for a large store, a site that uses most of the resources, or a client who wants to own the hosting. If a client won’t handle updates, backups and security themselves, a managed site may suit them better; see hosting vs managed WordPress.
In short
One plan works well for small client sites you manage yourself, as long as each site has its own folder, database and users.
Never hand out your cPanel password; give clients personal WordPress logins and, if needed, an FTP account limited to their folder.
Test big updates on staging, and restore only the affected site from backup, never the whole account.
The domain always goes in the client’s name, with their email; you handle the technical side.
Move large or sensitive sites, or those whose owners want to own the hosting, to their own account.
Frequently asked questions
Can one client see another client's site if they are on my plan?
Not if you only give them a login to their own WordPress dashboard, because each WordPress site has its own separate users. The trouble starts when you hand a client your cPanel password, which opens every site in the account.
If one client site is hacked, are the others at risk?
They can be. Sites inside one cPanel account run as the same system user and can reach each other's files. CloudLinux isolates your account from other customers' accounts on the server, not one site from another inside your account, so keep every site updated and move sensitive sites to their own account.
Whose name should a client's domain be registered in?
The client's, with an email address they actually read. The domain belongs to the business, and registering it in your own name complicates any later move and puts the relationship in an awkward spot. You can still manage the technical settings on their behalf.
Can I restore one client site without affecting the others?
Yes. JetBackup in cPanel lets you restore a single file, folder, database or mailbox. Restore just that site's folder and database, and avoid a full account restore, which rolls every site back to the backup date.
When should a client site move to its own account?
When it is a busy store or a high-traffic site that eats most of your plan's resources, when the client wants full hosting panel access, or when they want the hosting bill in their own name.
An honest look at what a server in Germany means for visitors in Jordan and the Gulf: what distance really adds, when it matters, how caching and a CDN reduce it, and how to measure it yourself.
A checklist for recording every online asset your business depends on, who controls it and when it renews, so a departing developer or employee never takes your domain or site with them.
A practical breakdown of the recurring costs that keep a business website online after launch, with a simple way to turn them into a yearly budget without surprises.
20 November 2026 · 7 min read
Ready to start, or have a question first?
We answer on WhatsApp Saturday to Thursday, 9:00 am – 9:00 pm Amman time (GMT+3)