BETA

A NEW CHAPTER

A fresh look. A clearer comparison.

Welcome to the redesigned HostingCompass. We’ve rebuilt the browsing and comparison experience to make it easier to explore hosting, domains and the providers behind them.

01

Find the right starting point

Explore hosting by product type, location, application or payment method.

02

Compare the details that matter

Bring plans together to review pricing, specifications and billing terms side by side.

03

Look beyond the first price

Compare domain registration, renewal and transfer offers in one place.

Still improving, with your help.

We’ll continue refining the experience and expanding the catalog. Prices and availability can change; check the provider’s current terms before purchasing. If you spot a missing detail or something that doesn’t work, let us know.

Send feedback →
Hosting & features

Can my ChemiCloud websites use different PHP versions in one account?

The short answer

Yes, on the documented cPanel setup, ChemiCloud supports a different PHP version for an addon domain, subdomain or folder through an .htaccess handler. The account-wide PHP selector alone does not provide that per-site setting.

In more detail

ChemiCloud distinguishes the account's global PHP selector from per-directory handlers. Its guide documents using an .htaccess handler when an addon domain, subdomain or folder needs a different PHP version. This is useful when assessing whether several applications can share one Pro or Turbo account without changing every site's runtime together.

Our recommendation is to list each application's supported PHP versions and required extensions before consolidating sites. Check the actual versions available on the target account, then test one site at a time. Include admin pages, forms, scheduled jobs and any commercial component; a working homepage alone does not establish compatibility across the application.

Record which directories have overrides so a future maintainer does not mistake the account's default version for every site's effective runtime. Keep a copy of the existing configuration before changes and plan how to reverse a failed update. Use separate versions as a controlled compatibility arrangement, while scheduling application updates; the ability to select an older runtime should not become a reason to postpone maintenance indefinitely.

Related providers & products

All questions