PHP hosting that keeps up with your code

Every modern PHP 8.x release is here, right up to PHP 8.4, and the version is set per domain rather than fixed once for the whole account. Got a project that still leans on a 7.x build? That's on the shelf too, so an old application and a fresh one can live side by side under one login. Per-site control matters because software states its own requirements: current CMS and framework releases usually ask for PHP 8.2 or newer, while an ageing plugin or a script somebody wrote in-house may only be certified against something earlier. Switching happens straight away and can be undone, which means no forced big-bang upgrade across everything you host. You move each site when that site is ready. As new releases become officially supported they get added, so there's room to shift onto a current, actively maintained build long before the one you're using reaches end of life.

One click does it. Open the PHP selector in your control panel, pick the release you want for that particular domain, and it's live immediately. No ticket to raise. No maintenance window to sit through. Because the setting belongs to the domain rather than the account, you can try an upgrade on a staging site first: aim it at the newer build, run the application, and satisfy yourself that nothing has fallen over before production follows. If a release does cause grief, whether that's a deprecated function or a plugin whose author hasn't caught up, going back is exactly as quick. Nobody gets stranded on a version that misbehaves. That same screen holds the extensions and core settings for whichever release you've chosen, so once you've picked one you can turn on precisely the modules your app wants. Keeping up with PHP here is a two-minute job, not a project.

Yes. Composer is pre-installed on every plan and runs over SSH, so dependency management behaves just as it does on your own machine. Log in and composer install, composer update, composer require and composer dump-autoload all work straight away against whichever PHP version that site is set to. For modern PHP work that's not optional: frameworks like Laravel and Symfony, plus a great many standalone libraries, are shipped through Composer rather than downloaded by hand. Your composer.json and composer.lock live in your repository, which means the package versions you tested locally are the exact versions that end up in production. Beyond Composer there's a genuine command line for the rest of the workflow. Run your framework's own CLI, fire off database migrations, clear caches, script a deploy. Cron is there as well, so anything you can type by hand can also be put on a timer without waiting on us to set it up.

Yes. The modules most applications ask for are sitting there waiting: GD and Imagick for image work, mbstring and intl for multibyte and internationalised text, cURL for outbound requests, PDO with the MySQL drivers for database access, and OPcache, zip, bcmath and plenty more besides. You toggle them per PHP version, in the control panel. Since the list belongs to whichever release you have picked, one site can get the modules it wants while nothing else on the account notices. That same screen handles the core php.ini values that catch out a busy app, memory_limit and max_execution_time among them, along with the upload size limits, so you can match a CMS or framework's stated requirements to the letter. Flick most extensions on and they take effect; no support ticket involved. Should your code lean on something more obscure, our team will check whether it is available and help you turn it on, rather than leaving you to guess whether the module is there at all.

Almost certainly. Laravel, Symfony, CodeIgniter and Slim all behave themselves, and so do the big content and commerce platforms: WordPress, Drupal, Joomla, Magento. They are ordinary PHP applications, and this is an ordinary, well-equipped PHP stack. Getting an install to go smoothly is mostly a matter of matching the environment to what the software recommends. Set the PHP version it supports. Enable the handful of extensions its documentation lists. Raise memory_limit, or the upload size, if the requirements page asks for more. After that, deploy however suits you: a one-click installer for the popular platforms, or Git and Composer for a framework project or code you wrote yourself. A genuine CLI plus cron covers the scheduled work these systems lean on, from queue processing through to nightly maintenance. Not sure whether one particular app will fit? Ask our support team, who have almost certainly seen it before and can advise.

No single switch is responsible here; the parts work together. NVMe SSD storage strips the disk latency out of every file read and database query, so a page assembles fast. OPcache holds your compiled PHP bytecode in memory, which spares the server from recompiling scripts on each request, and that is a big saving on framework-heavy code. Caching at server level shortens the route to a rendered page for anyone coming back a second time. Object caching lifts pressure off the database for values your application looks up again and again. Beneath all of it, CloudLinux puts every account in 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 behaves at its busiest the way it behaves when things are quiet. Tune OPcache, the realpath cache and your PHP version to suit the workload, and you will wring out the last of the response time.

Yes — free managed migration covers your code, MySQL database, cron jobs and configuration files, not just what's in your public folder. Our team verifies the migrated app actually connects to its database and loads correctly before your domain is pointed across, so there's no gap where visitors see a broken site.

Daily backups run automatically and capture your files and databases together, so a bad deploy or a corrupted table has a recent recovery point. Restores are self-serve from the control panel, meaning you don't need to open a support ticket and wait to roll back a change.

Yes, every domain includes a free SSL certificate that renews itself automatically, so forms, logins and any checkout pages your PHP app serves stay encrypted without you needing to track an expiry date.

Every plan carries a 30-day money-back guarantee, which is enough time to deploy your actual app, run it under real traffic and test a release cycle before deciding to stay.

Pricing displays automatically in your local currency through geo-currency detection, but billing is settled in USD by Bohzo Ltd, the UK-registered company behind Hosting Cheap. That keeps invoices consistent even though what you see at checkout adapts to your location.

Signals worth watching are sustained high CPU from background jobs, needing root access for a system-level dependency, or database performance that would benefit from dedicated tuning. VPS plans start at $13.52/mo and dedicated servers from $149.99/mo for apps that have outgrown shared resources.