PHP hosting that keeps up with your code

You can run any of the modern PHP 8.x releases right up to PHP 8.4, and you set the version independently for each domain rather than being locked to one platform-wide default. If a project still depends on an older 7.x build, that is available too, so a legacy app and a brand-new one can happily share the same hosting. Choosing a version per site matters because different applications state different requirements: the latest CMS and framework releases often want PHP 8.2 or newer, while an older plugin or bespoke script may only be certified against an earlier build. Because switching is instant and reversible, you are never forced to upgrade everything at once — you migrate each site on its own schedule. New releases are added as they become officially supported, so you can move to a current, actively maintained version well before the one you are on reaches end of life.

It takes a single click. Open the PHP selector in your control panel, choose the release you want for that specific domain, and it applies straight away — there is no support ticket to raise and no maintenance window to wait for. Because the setting is per domain, you can test an upgrade on a staging site first: point it at the newer version, run your app, and confirm nothing breaks before you move production across. If a release ever causes trouble — a deprecated function, a plugin that has not caught up — rolling back is just as fast, so you are never stuck on a version that misbehaves. The same screen is where you manage extensions and core settings for that version, so once you have picked a release you can enable exactly the modules your app needs. In practice, keeping up with PHP is a two-minute job, not a project.

Yes. Composer comes pre-installed on every plan and works over SSH, so managing PHP dependencies behaves exactly as it does on your own machine. Log in and composer install, composer update, composer require and composer dump-autoload all run immediately against the PHP version you have selected for that site. That is essential for modern PHP work, because frameworks like Laravel and Symfony, and countless standalone libraries, are distributed through Composer rather than downloaded by hand. You keep your own composer.json and composer.lock in your repository, so the package versions you tested locally are the exact versions that end up in production. Alongside Composer you get a real command line for the rest of your workflow — run your framework's CLI, trigger database migrations, clear caches and script deploys. Cron support means anything you can run by hand can also run on a schedule, without waiting on us to set it up.

Yes. The extensions most applications ask for — GD and Imagick for image work, mbstring and intl for multibyte and internationalised text, cURL for outbound requests, PDO and the MySQL drivers for database access, plus OPcache, zip, bcmath and more — are ready to toggle per PHP version from the control panel. Because the list is tied to the version you have selected, you can give one site the modules it needs without affecting anything else on the account. The same area lets you adjust the core php.ini values that trip up busy apps, such as memory_limit, max_execution_time and the upload size limits, so you can match a CMS or framework's stated requirements precisely. Most extensions switch on and take effect without a support ticket. If your app depends on something less common, our team can confirm availability and help you enable it, so you are not left guessing whether a module is there.

Almost certainly. Laravel, Symfony, CodeIgniter and Slim all run well, as do the major content and commerce platforms — WordPress, Drupal, Joomla and Magento — because they are standard PHP applications and this is a standard, well-equipped PHP stack. The trick to a smooth install is simply matching the environment to what the software recommends: set the PHP version it supports, enable the handful of extensions it lists, and raise memory_limit or the upload size if its documentation calls for more. From there you deploy the way you prefer — a one-click installer for the popular platforms, or Git and Composer for a framework project or your own code. A real CLI and cron cover the scheduled tasks these systems rely on, from queue processing to nightly maintenance. If you are unsure whether a specific app is a fit, our support team has almost certainly seen it before and can advise.

Speed comes from the whole stack working together rather than any single switch. NVMe SSD storage cuts the disk latency behind every file read and database query, so pages assemble quickly. OPcache keeps your compiled PHP bytecode in memory, which means the server skips recompiling your scripts on each request — a large saving on framework-heavy code. Server-level caching shortens the path to a rendered page for repeat visitors, and object caching takes pressure off the database for values your app looks up again and again. Underneath, CloudLinux isolates every account into its own resource lane, so a neighbour's runaway script can never quietly starve your site of CPU or memory during a traffic peak — your app performs the same at its busiest as it does when it is quiet. Tuning OPcache, the realpath cache and your PHP version to the workload lets you squeeze out the last bit of response time.