Engineering Brief
Hosting with multiple PHP versions — Move one site at a time, and measure each move
You have a 2019 build that dies on anything above 7.4 and a new project that wants everything a current branch offers, and one account-wide PHP setting cannot serve both.
The short answer
Choose hosting where the PHP version is set per site rather than per account: on Turbo at $4.66 a month you switch the branch for one site from cPanel without touching the other twenty-four, and extensions are toggled per version on the same screen.
Then treat every switch as an experiment with a before and an after. Change one site, watch its error log for a day, and time a real page with `curl -s -o /dev/null -w '%{time_starttransfer}'` before and after. A version bump usually helps, but 'usually' is not a measurement.
Below: how to find out what breaks before your users do, what a newer branch actually buys in milliseconds, and how to run a controlled wind-down for the site that genuinely cannot move yet.
By the HostingFast team · Reviewed 24 August 2026
Free
Migration, run by us
24/7
Humans on the desk
Daily
Backup cadence
$0
Setup charge
A collection of sites accumulated over years is a collection of PHP requirements. Forcing them all onto one branch means either holding everything back to the oldest one or breaking the awkward one to please the rest.
Per-site switching removes the trade entirely — but only if you use it as a migration ramp rather than a hiding place. This page is about doing the moves in a controlled, measured order.
Finding out what breaks before anyone else does
Do the discovery on a staging copy, not the live site. Clone it, switch the clone to the target branch, and then exercise the paths that matter: the checkout, the contact form, the admin screens, the cron job.
The error log is the actual test. `tail -f ~/logs/yourdomain.example.error.log` while you click through will surface deprecation notices and fatals in the order the interpreter meets them. Deprecations are warnings about the branch after next; fatals are the ones stopping you today.
For PHP-heavy applications, a static scan of the codebase for removed functions is worth an hour before you start clicking. Most breakage in practice is one abandoned plugin or one library pinned years ago, and finding it early turns a scary migration into a small piece of shopping.
What a newer branch is actually worth
The honest answer is: usually a real improvement on CPU-bound work, and usually nothing at all on anything dominated by database queries or by network calls to a third party. Which of those describes your site is a question you can answer rather than assume.
Measure it directly. Take the median of five `curl -s -o /dev/null -w '%{time_starttransfer}'` runs against an uncached page — a logged-in view, a search result, a basket — before the switch and after it. Cached pages will not move, because they never reach PHP in the first place.
On Nitro at $7.08, PHP X-Ray on CloudLinux Pro will point at the slow function rather than leaving you to infer it. If your problem is one query in a plugin, a version bump was never going to fix it, and knowing that saves a wasted week.
The wind-down lane for the site that cannot move
Once a branch reaches end of life, security fixes stop being published for it. That is a hard fact about the upstream project, not a policy of ours, and it means an old branch is a temporary position rather than a destination.
So give it a date. Switch everything that can move now, list what is blocking the rest — usually a named plugin or a bespoke library — and put a review in the calendar. A site parked on an old branch with an owner and a date is a plan. The same site with neither is a liability.
In the meantime, reduce exposure: keep the site behind the platform's server-level scanning and edge DDoS filtering, keep backups verified, and take the ageing site off any shared credential it does not need.
How the switching works here
PHP version is set per site from cPanel, along with the extensions for that version. The change applies to that document root alone, so a modern build and a legacy install run side by side on one account with no interference.
Turbo at $4.66 a month gives you 25 sites, 20 GB of NVMe, 1 TB of bandwidth, 1 core and 2 GB of RAM and 50 MySQL databases, with the renewal charged at the same $4.66. Full SSH with Git and Composer is on the account, so `php -v` confirms what a site is actually running rather than what the panel says it should be.
If you are arriving from a host that pinned everything to one branch, our engineers move the whole estate free, usually within 24 hours, and nothing switches until you have checked the copy. Shared plans carry a 30-day money-back window, and HostingFast is a trading name of Vitalcare at Home Ltd, company number 15098204.
Why the recommendation is a ramp, not a resting place
It would be easier to sell you version choice as a way to avoid upgrading forever. It is not that, and pretending otherwise would leave you on an unsupported branch with our name on the invoice.
We recommend our own plan on this page and we would rather say so. In exchange the page gives you the commands, the log to read and the criterion for deciding whether the bump did anything.
- Per site, not per account
- Extensions toggled per version, on one screen
- A before-and-after that takes two minutes
- $4.66 at order is $4.66 at renewal
Why HostingFast
Standard on every plan
One site at a time
Switch the branch for a single document root from cPanel. The other twenty-four carry on exactly as they were.
Extensions per version
The legacy requirement that only exists on the old branch stays available there, without polluting the current one.
A log you can watch live
SSH means `tail -f` on the error log while you click through, which is how deprecations and fatals surface in useful order.
Staging for the rehearsal
Clone, switch the clone, break the clone. The live site never participates in the discovery phase.
X-Ray on the top tier
Nitro at $7.08 includes PHP X-Ray on CloudLinux Pro, which names the slow function instead of leaving you guessing.
A free move if you are stuck
Our engineers migrate an estate pinned to one branch elsewhere, typically inside 24 hours, at no cost.
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
Inventory what each site actually needs
Application, plugins, libraries and the oldest thing pinning each one. The list is short and it is the whole project.
- 2
Rehearse on a clone with the log open
Switch the copy, exercise checkout, forms, admin and cron, and read the error log rather than the homepage.
- 3
Time an uncached page before and after
Five curl runs, median, on a page that reaches PHP. Cached pages will not move and will tell you nothing.
- 4
Give the stragglers a date
Anything left on an unsupported branch needs a named blocker and a review date, or it stays there for years.
Built In
Loaded onto every plan
- People on the desk at every hour of every day
- Per-site PHP version switching, with per-version extensions
- Full SSH so `php -v` can confirm what is really running
- Staging copies for rehearsing a branch change safely
- Refund cover: 30 days on hosting plans, 7 days on reseller accounts
- Edge filtering in front of every account, permanently on
- Mail filtering on every mailbox, without a separate subscription
- Mailboxes on your own domain, included in the plan
- Webmail plus IMAP, POP and SMTP for any mail client
- NVMe underneath every plan, which is what an uncached read waits on
- WebP image conversion built in at no extra cost
Frequently Asked
What people ask us most often
How do I find out what a version bump will break?
Clone the site to staging, switch the clone to the target branch, then exercise checkout, forms, admin and any scheduled job while tailing the error log over SSH. Fatals stop you today; deprecation notices are advance warning about the branch after next. Most breakage traces back to one abandoned plugin or one pinned library.
Does a newer PHP branch make a site measurably faster?
On CPU-bound work, often. On anything dominated by database queries or third-party API calls, usually not. Measure an uncached page — a logged-in view or a search result — with five curl timing runs before and after and take the median. Cached pages never reach PHP, so they will not move at all.
Can two sites on the same account run different versions?
Yes, that is the point of per-site switching. The branch and its extensions are set for one document root from cPanel, so a 2019 application and a current build coexist on one Turbo account at $4.66 a month without interfering with each other.
One plugin is holding me on an unsupported branch. Now what?
Treat the old branch as a ramp with an end date rather than somewhere to settle, because upstream security fixes stop when a branch reaches end of life. Name the blocker, set a review date, and in the meantime keep the site behind the server-level scanning and edge filtering and off any shared credential it does not need.
Keep reading
Hosting for Nonprofit Projects
Volunteer-run sites are where old PHP branches survive longest, and where a review date matters most.
CMS Hosting for Content Teams
Choosing a CMS and the runtime under it together, so the publishing workflow is not hostage to a pinned library.
How to Change Your PHP Version
The switch itself, screen by screen, plus how to confirm from the shell that it actually took effect.
PHP Hosting
Current branches available quickly, older ones still offered, and the version chosen per site rather than per account.
WordPress Hosting
Managed WordPress with Toolkit Deluxe, staging and Redis, for the sites where a plugin decides your PHP ceiling.
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.
Upgrade one site. Then the next.
Turbo at $4.66 a month: per-site PHP from cPanel, SSH to prove it, staging to rehearse it, NVMe under all of it.
View PHP Hosting plans