All products 
How to host 10 or more websites on a single hosting plan
Hosting for multiple websites is what you need if you run several projects of your own, manage client sites as an agency, or operate a network of sites. This selection includes around 1,560 plans from more than 670 hosts that allow at least 10 websites per account. Prices start at about $0.70 a month, and the median is around $10.50. The most common plans allow exactly 10 sites, followed by 20, unlimited, 50, 15 and 100 sites.
The site count isn't the limit that matters
Permission to add ten domains tells you nothing about whether the account can actually run ten live websites. Resources are shared across all your projects, so these are the parameters to look at instead.
- CPU and memory per account. Usually a fraction of a core or one or two cores, plus 1–2 GB of RAM for the whole account. If three sites get traffic at the same time, or a search engine crawler hits all of them at once, the rest will slow down.
- Concurrent processes (entry processes). The limit on parallel PHP requests is shared by every site on the account. With 20 processes across 10 sites, each one gets only two on average.
- Inodes. This is the limit on the number of files. A single WordPress install with plugins and cache takes up 10,000–30,000 files, so a limit of 150,000–250,000 inodes will run out before your disk space does.
- Databases. Every CMS-based site needs its own database. Make sure you get at least as many databases as sites, and check how much space they're allowed to use.
- Disk. The median in this selection is 40 GB, twice the catalog average. That's enough for a dozen sites without heavy media, but remember that backups and email also count against your quota.
- Email. The hourly sending limit is usually shared across the account. If every site sends notifications, contact form submissions and sign-up emails, it's easy to exceed.
What "unlimited websites" really means
Plans with no cap on the number of sites are common, but "unlimited" applies only to the number of domains. CPU, memory, processes, inodes and disk are still limited. In practice, a plan like this works well for dozens of lightweight sites (landing pages, business card sites, static pages) and just a handful of busy ones. On top of that, many hosts' acceptable use policies prohibit hosting third-party sites on a single account or using the plan as a reseller account.
Site networks and separate IPs
If you run several related projects, keep in mind that on shared hosting all the sites on an account usually share one IP address, which is also shared with other customers on the server. That's fine for some purposes; for others you need separate IPs or accounts with different hosts. A dedicated IP is often available for an extra fee. For a large number of projects on different IPs, it's sometimes easier to get several inexpensive plans from different hosts, or a VPS with additional addresses.
For agencies: isolating client sites
If one account holds sites for different clients, a single vulnerable plugin can compromise every neighboring site, because they all run under the same system user. Ways to protect yourself:
- a reseller plan, where each client gets a separate account with their own control panel;
- panels that support a separate user for each site: ISPmanager and Plesk can do this, and ISPmanager shows up noticeably more often in this selection than across the catalog as a whole (see ISPmanager hosting for details);
- regular backups of each site separately, so you can restore them one at a time.
Maintaining a dozen websites
As the number of sites grows, the main problem is no longer hosting but updates. An abandoned site running an outdated CMS is the most common way an entire account gets hacked. Keep a list of your sites with their CMS and plugin versions, turn on automatic updates where it's safe, and delete unused sites and staging copies. Disable registration and comments on inactive projects so they don't attract spam and eat into your email limit.
When to move to a VPS
Shared hosting for many sites makes sense as long as the projects are lightweight. Signs that it's time for a VPS:
- You regularly see 503 and 508 errors caused by process or CPU limits, and upgrading to a higher plan no longer helps.
- Your sites' combined traffic reaches tens of thousands of visits a day.
- You need different PHP versions, Redis, your own long-running cron jobs or background processes.
- The plan's price has come close to that of a VPS with dedicated cores and memory.
On a VPS you can install the same panel (ISPmanager, FASTPANEL, HestiaCP) and split sites across separate users while getting guaranteed resources. For a selection of servers suited to websites, see VPS for websites. If your sites mostly target Russia and collect leads, consider servers in Russia: this selection has noticeably more Russian plans than the catalog average, and you can filter them on the hosting in Russia page.