PHP hosting built to match your codebase

You're free to run any current PHP 8.x release, all the way up to PHP 8.4, and the version is set per domain rather than tied to one account-wide default. Older 7.x builds remain on offer too, so a long-running legacy project and a freshly built one can live on the same hosting account without conflict. Setting the version site-by-site matters in practice: newer CMS platforms and framework releases typically expect PHP 8.2 or above, whereas an aging plugin or custom script might only be tested against an earlier build. Switching takes effect instantly and reverses just as fast, so nothing forces you to move every site to a new version on the same day — each one can be migrated at its own pace. As new PHP releases gain official support we add them, giving you a clear path to a current, maintained version well ahead of your existing one reaching end of life.

Switching takes one click and nothing more. Open the PHP selector inside your control panel, pick the release you want for that domain, and it takes effect right away — no ticket to file, no maintenance window to schedule. Since the setting applies per domain, you can trial an upgrade on a staging copy first: switch it to the newer version, put your app through its paces, and only move production once you're satisfied. Should a release cause any friction — an outdated function call, a plugin that hasn't updated yet — reverting is equally instant, so you're never trapped on a version giving you trouble. That same control panel screen is also where extensions and core settings for the chosen version live, letting you turn on exactly the modules your app calls for. In short, staying current with PHP takes a couple of minutes, not a whole afternoon.

Yes — Composer is pre-installed on every plan and runs over SSH, so handling PHP dependencies feels identical to working on your local machine. Sign in and composer install, composer update, composer require and composer dump-autoload execute right away against whichever PHP version you've chosen for that domain. That matters for modern PHP development, since Laravel, Symfony and a huge number of standalone libraries are distributed through Composer rather than downloaded manually. Your own composer.json and composer.lock stay in your repository, so the exact package versions you verified locally are what ends up running in production. Beyond Composer, you get a genuine command line for everything else in your workflow — running your framework's CLI, firing off database migrations, clearing caches and scripting deployments. Cron support means anything you'd normally trigger by hand can also be scheduled to run automatically, with no setup required from us.

Yes. The extensions most projects reach for — GD and Imagick for handling images, mbstring and intl for multibyte and localized text, cURL for outbound calls, PDO with the MySQL drivers for database work, along with OPcache, zip, bcmath and others — can be switched on per PHP version straight from your control panel. Since the available list follows the version you've picked, you can equip one site with what it needs without touching anything else on the account. That same panel is where you tweak the core php.ini values that trip up busy applications — memory_limit, max_execution_time and upload size caps — so you can meet a CMS or framework's stated requirements exactly. Most extensions activate immediately with no ticket needed. For anything less common your app depends on, our support team can check availability and walk you through enabling it, so you're never left wondering if a module exists.

Very likely, yes. Laravel, Symfony, CodeIgniter and Slim all run cleanly, along with the leading content and store platforms — WordPress, Drupal, Joomla and Magento — since they're standard PHP software running on a fully equipped standard PHP stack. Getting a smooth install mostly comes down to matching your environment to what the software asks for: pick the PHP version it supports, switch on the extensions it lists, and raise memory_limit or the upload cap if its docs call for it. From there, deploy however suits you — a one-click installer for the well-known platforms, or Git plus Composer for a framework build or custom code. A genuine CLI and cron cover the scheduled work these systems depend on, from queue workers to nightly cleanup tasks. Not sure whether a particular app will fit? Our support team has likely handled it before and can point you in the right direction.

Speed here comes from several layers working together, not one setting. NVMe SSD storage trims the disk latency behind every file read and database query, so pages come together quickly. OPcache holds your compiled PHP bytecode in memory, meaning the server doesn't recompile your scripts on each request — a meaningful gain on framework-heavy applications. Server-level caching shortens the trip to a rendered page for repeat visitors, while object caching eases the load on your database for values your app requests again and again. Underneath it all, CloudLinux gives every account its own resource lane, so a neighbouring site's runaway script can never quietly starve yours of CPU or memory during a traffic surge — your app runs the same at its busiest as it does in a quiet moment. Fine-tuning OPcache, the realpath cache and your PHP version for your particular workload squeezes out whatever response time is left on the table.