Capacity Arithmetic
Hosting for multiple websites — Twenty-five sites share one allocation, so count what they consume rather than how many there are
You have collected sites faster than you have measured them, and the plan page counts websites while the server counts databases, inodes and simultaneous PHP processes.
The short answer
Buy for the aggregate rather than the count: Turbo at $4.66 a month carries 25 sites, 20 GB of NVMe, 1 TB of bandwidth and 50 MySQL databases on 1 core and 2 GB — and on a stack of mostly quiet sites the database allowance runs out before anything else does.
The count misleads because websites idle. Twenty-five brochure sites plus one busy one produce roughly the load of one busy site, since consumption follows requests rather than installations. What does not idle is scheduled work: every WordPress install wants to run wp-cron, and twenty-five schedulers landing in the same minute is a real spike on a single core.
By the HostingFast team · Reviewed 24 August 2026
99.9%
Uptime target, credited if missed
24/7
Support at any hour
Free
SSL on every domain in the account
NVMe
NVMe under every site
Plan pages advertise a site allowance because it is the easiest number to print. It is also the number least likely to be the thing that stops you: 25 sites sitting on 50 databases means a WordPress site with a staging copy has already spent two of the fifty before you have added anything interesting.
So measure the stack you actually have. Four figures — databases in use, inodes, peak simultaneous PHP processes and total monthly transfer — settle the tier in about ten minutes, and every one of them is readable from cPanel without asking anybody.
Four numbers, all readable from cPanel
Open Resource Usage first. It plots entry processes, CPU and memory against your account's limits, and the peaks are what matter — a stack of sites looks comfortable at the average and falls over at the spike.
Then MySQL Databases, for the count already in use. Sprint allows 25, Turbo 50 and Nitro 100, and every WordPress install plus every staging copy takes one.
Then file usage, for inodes. That figure climbs with plugin files and media rather than with megabytes, which is why a stack of image-heavy sites can be nowhere near 20 GB and still be in trouble.
Bandwidth last, because it is the number people worry about and the one that almost never binds. 1 TB on Turbo is a very large amount of brochure-site traffic. Write all four down before you look at a single plan page, and the tier chooses itself.
Where quiet sites actually collide
The collision is scheduled work, not visitors. WordPress fires wp-cron on page loads, so a stack of sites produces uncoordinated bursts of update checks, scheduled posts and cleanup jobs at moments nobody planned.
The fix is dull and effective: disable WP_CRON in each wp-config.php, add one real cron entry per site in cPanel, and stagger the minutes. Twenty-five jobs spread across an hour is a different machine from twenty-five jobs at the top of it.
Give plugin auto-updates the same treatment. A nightly platform backup plus twenty-five updaters that all chose three in the morning is a self-inflicted spike on 1 core and 2 GB.
Then watch for the site that is not quiet. In practice one property does most of the work, and when Resource Usage shows it pressing the entry-process ceiling, the answer is Nitro's 2 cores and 4 GB rather than pruning the twenty-four that cost nothing.
Housekeeping that keeps a stack quick
Run each site on the PHP version it deserves. The cPanel selector is per domain, so a 2019 build can stay where it is while everything else runs current — and switching one site first is the safe way to test an upgrade.
Keep the media libraries honest. Years of unused thumbnails across twenty-five installs will reach an inode ceiling long before they trouble the disk allowance.
Use per-site restores instead of account-wide ones. A cPanel restore can take one domain's files, or one database, which means rolling back a broken experiment leaves the other twenty-four untouched.
Finally, decide which sites belong to somebody else. Your own projects can share an account safely; a paying client's site should be a separate cPanel account, and that is a reseller plan rather than a larger shared one.
What to buy, and how to check it before you do
Turbo at $4.66 a month is the working answer for a personal stack: 25 sites, 20 GB of NVMe, 1 TB of bandwidth and 50 databases. Nitro at $7.08 doubles the cores and takes it to 100 sites, 200 GB and 100 databases when one property starts doing real numbers. Sprint at $2.42 is a single site, so it is the wrong shape for this page.
Before ordering, run the same measurements against sites we already host: time to first byte on a cached page, and whether x-litespeed-cache reports a hit. Compare the renewal figure with the order figure — ours are the same number — and look the company up: HostingFast is a trading name of Vitalcare at Home Ltd, registered in England and Wales.
Migration is free and normally inside 24 hours, and hosting carries a 30-day money-back window. Moving one site across first is the cheapest possible way to settle the question.
The numbers the plan page does not print
Site allowances are marketing. Databases, inodes and entry processes are the plumbing, and all three are visible in cPanel on any account including ours — which is why this page argues from them rather than from a comparison table.
Order annually and the first year of your domain registration is included, which counts for more than usual when you are collecting names faster than you are building sites.
- Databases and inodes counted, not just websites
- wp-cron replaced by staggered cPanel cron entries
- Per-site restores, so one rollback stays local
- Order price and renewal price, the same number
Why HostingFast
Standard on every plan
Turbo, specified
$4.66 a month for 25 sites, 20 GB of NVMe, 1 TB of bandwidth and 50 MySQL databases.
Per-domain PHP versions
The cPanel selector works per site, so an older build stays on its version while everything else runs current.
Restores with site granularity
Recover one domain's files or one database without rolling back the other twenty-four.
Real cron, not wp-cron
Proper cron entries you can stagger by the minute, which is what stops twenty-five schedulers landing together.
Resource Usage you can read
Entry processes, CPU and memory plotted against your limits, so the tier decision comes from data rather than nerves.
Nitro when one site pulls ahead
2 cores and 4 GB, 100 sites and 100 databases at $7.08, applied in place with nothing to migrate.
Prices Side by Side
Our numbers next to the big names
Typical intro and renewal pricing across the market, lined up against ours — including the renewal figure most comparison charts skip.
| Feature | HostingFastMost popular | Typical household-name host | Typical bargain host | Typical loss-leader deal |
|---|---|---|---|---|
| Starting price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Renewal price / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Cheapest plan renews at its sign-up price | ||||
| SSL as standard | ||||
| Migration done for you | ||||
| NVMe drives on the cheapest tier | ||||
| Daily backups from the first tier | ||||
| Real humans on support, 24/7 |
*Our number is the lowest-priced plan we sell on an annual term, pulled live from the same catalogue that powers our pricing page — it physically cannot fall out of date. The other three columns show the ranges shared hosts in each bracket typically advertise: introductory offers that mostly demand a one-to-four-year commitment, then jump once it expires. We no longer name rivals or print their prices, because a figure we cannot verify on the day you read it has no business on this page. Line us up against whichever host you are really weighing — and give the renewal row the hardest look.
Quick Start
From order to online
- 1
Count databases and inodes first
Both live in cPanel, and on a stack of WordPress installs both run out before the advertised site allowance does.
- 2
Move every site off wp-cron
Disable WP_CRON, add one cPanel cron entry per site, stagger the minutes. It is the single change that most improves a busy stack.
- 3
Watch entry processes for a fortnight
The peak decides the tier, not the average. If the ceiling is being touched weekly, the second core is the upgrade that matters.
Built In
Loaded onto every plan
- A database allowance covering every site plus its staging copy
- Inode headroom for years of media across every install
- Resource Usage graphs showing entry processes against the account limit
- Real cron entries in the panel, schedulable per site
- Per-domain PHP version switching from the control panel
- Per-site file and database restores you run yourself
- NVMe storage on every tier, so the database work stays quick
- LiteSpeed caching in front, so quiet sites cost almost nothing to serve
- In-place upgrades between tiers with no site migration
- Free SSL issued and renewed on every domain in the account
Frequently Asked
What people ask us most often
How many databases will twenty-five WordPress sites need?
At least twenty-five, and realistically more: every install takes one and every staging copy takes another. Turbo allows 50 MySQL databases against its 25-site allowance, which is comfortable with staging on the busiest few; Nitro doubles it to 100. If anything in the stack keeps a second database of its own, count those in before choosing.
Do twenty-five wp-cron jobs firing at once actually matter?
On 1 core and 2 GB, yes. wp-cron runs on page loads, so a stack of sites produces bursts of scheduled work with no coordination between them. Disable WP_CRON in each wp-config.php, add a real cron entry per site in cPanel and stagger the minutes. It costs an hour once and removes an entire category of unexplained slowness.
Can each site run a different PHP version on one account?
Yes — the cPanel PHP selector applies per domain. An older client build can stay on the version it was written for while everything else runs a current one, and switching a single site first is the safe way to test an upgrade: change it, watch that site's error log for a week, then move the rest.
How do I restore one site without touching the other twenty-four?
Use the per-site restore in cPanel rather than a full account restore: choose that domain's files, or that site's database, or both. Daily backups run on every plan and the restore starts from your own panel rather than a ticket queue. Rehearse it once on a site nobody would miss, so the first real attempt is not also the first attempt.
Keep reading
Email Hosting for Small Business
Where mail should live once a domain collection turns into a business, and the records that decide delivery.
Hosting With 24/7 Human Support
What a support desk can genuinely fix at three in the morning, and how to test one before you need it.
Uptime (Glossary)
What 99.9% works out to in minutes a month, and who is doing the measuring.
Web Hosting
cPanel hosting on NVMe behind LiteSpeed, with per-domain PHP versions and SSL on every name in the account.
Website Builder
A no-code builder for the sites in the stack that never justified a WordPress install.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Buy for the load, not the list.
25 sites and 50 databases on Turbo, per-domain PHP versions, per-site restores and a renewal figure that never moves.
View Web Hosting plans