Skip to main content

PHP Hosting

PHP Hosting With Real Version and Extension Control

Switch PHP versions per site, enable the extensions your framework needs, and run Composer without fighting a locked-down default configuration.

Multi

PHP versions selectable per site

NVMe

SSD with LiteSpeed for PHP speed

$2.09/mo

Starting PHP hosting price

24/7

Support for extension and config help

In short

PHP hosting needs to support selecting a specific PHP version per site, enabling or disabling extensions like GD, Imagick, or intl, adjusting php.ini settings such as memory_limit and upload_max_filesize, and running Composer to manage framework dependencies. Hosting Cheap runs PHP on NVMe SSD with LiteSpeed for performance, a cPanel-style panel offering per-site PHP version selection and extension toggles, and web hosting plans from $2.09/mo with 24/7 human support for configuration questions.

PHP hosting sounds like a commodity until a project actually needs PHP 8.2 for a modern Laravel app while an older client site on the same account still depends on PHP 7.4 syntax that would break on the newer version - at which point per-site version control stops being a nice-to-have and becomes the deciding factor in whether a host even works. The same goes for extensions: a project using Imagick for image manipulation, intl for locale-aware formatting, or a specific database driver simply won't run if the host doesn't expose a way to enable it.

Composer has also become close to mandatory for any modern PHP project, whether it's Laravel, Symfony, WordPress with Composer-managed plugins, or a custom framework, which means SSH access or a Composer-aware panel matters as much as raw PHP support. Hosting Cheap's cPanel-style panel gives per-site PHP version selection, extension and php.ini control, and Composer support, all running on NVMe SSD with LiteSpeed caching so switching PHP versions doesn't come at the cost of performance.

Per-site PHP version selection

Different PHP projects age at different rates - a five-year-old client site built against PHP 7.4 might break on 8.x due to deprecated function signatures, while a fresh Laravel install requires a current PHP version to even install its dependencies through Composer. Hosting that locks every site on an account to a single PHP version forces an impossible choice between breaking the old site or blocking the new one.

A cPanel-style panel with per-site PHP version selection avoids that entirely, letting one hosting account run PHP 7.4 for a legacy site and PHP 8.2 or newer for a current project simultaneously, each isolated from the other's requirements.

Extension and php.ini control that frameworks actually need

Modern PHP frameworks and CMS platforms lean on specific extensions - GD or Imagick for image processing, intl for locale-aware date and currency formatting, mbstring for proper multi-byte string handling, and various database drivers depending on the project. Hosting that doesn't expose a way to toggle these extensions on a per-site basis turns a five-minute configuration change into a support ticket or, worse, a dead end that blocks a project from working at all.

The same applies to php.ini directives like memory_limit, upload_max_filesize, and max_execution_time, which frequently need adjusting for anything from a WordPress media-heavy site to a Laravel app processing large file uploads or long-running import jobs.

Composer support for framework dependency management

Composer has become the standard way PHP projects manage their dependencies, whether that's Laravel pulling in its ecosystem of packages, Symfony components, or a WordPress site using Composer to manage plugins as code rather than through the admin panel. Running composer install or composer update reliably requires either SSH access or a panel-integrated Composer tool, along with enough memory_limit headroom that a large dependency tree doesn't hit a wall mid-install.

NVMe SSD storage speeds up Composer's dependency resolution and file writes noticeably compared to slower storage, which matters on projects with large vendor directories or frequent deployment cycles.

Performance tuning across PHP versions

PHP performance isn't just about the language version - opcode caching, the underlying web server's handling of PHP requests, and disk speed for autoloading classes all factor in, and LiteSpeed's PHP handling is built to perform well across the PHP versions it supports rather than favoring only the newest one. That matters for accounts running a mix of legacy and current PHP versions across different sites, since neither should feel like the neglected option.

Daily backups and free auto-renewing SSL round out the practical side of PHP hosting, protecting a site's code and database from a bad update while keeping every version of a project's PHP-rendered pages served securely.

PHP Hosting: Multiple Versions & Extensions

Version and extension control, not a locked default

PHP projects age differently and frameworks demand different extensions, which is why per-site PHP version selection and extension control matter more than raw hosting price alone. A cPanel-style panel makes both straightforward to manage.

NVMe SSD with LiteSpeed keeps every supported PHP version performing well, and Composer support means Laravel, Symfony, and Composer-managed WordPress projects all have what they need to install dependencies reliably.

  • Select a different PHP version per site from one hosting account
  • Toggle extensions like GD, Imagick, intl, and mbstring as needed
  • Adjust php.ini settings including memory_limit and upload_max_filesize
  • Run Composer to manage Laravel, Symfony, or plugin dependencies

Why Hosting Cheap

What you get

Per-site version control

Run different PHP versions for a legacy site and a current framework project on one account.

Extension flexibility

Enable GD, Imagick, intl, mbstring, and other extensions your framework or CMS requires.

Adjustable php.ini limits

Change memory_limit, upload_max_filesize, and max_execution_time to match your project's needs.

Composer-ready

Install and update dependencies for Laravel, Symfony, or Composer-managed WordPress projects.

Consistent performance

NVMe SSD and LiteSpeed keep every supported PHP version fast, not just the newest one.

Configuration support

24/7 human support helps with extension, php.ini, or Composer configuration questions.

How It Works

Get set up in a few steps

1

Choose your hosting plan

Pick a web hosting plan from $2.09/mo sized for your PHP project's traffic and storage needs.

2

Set your PHP version and extensions

Select the PHP version per site and enable the extensions your framework or CMS requires.

3

Install dependencies and launch

Run Composer to install your project's packages, confirm php.ini limits, and go live.

Included

Everything you need, on every plan

  • Confirm per-site PHP version selection is available on your plan
  • Check that the extensions your framework needs can be enabled
  • Verify memory_limit and upload_max_filesize meet your project's requirements
  • Confirm Composer can be run via SSH or a panel-integrated tool
  • Test performance across each PHP version your sites actually use
  • Enable daily backups before running major dependency updates
  • Confirm free SSL is active and auto-renewing on each domain

FAQ

Frequently asked questions

Can I run different PHP versions for different sites on one account?

Yes, per-site PHP version selection lets one hosting account run, for example, PHP 7.4 for a legacy site and PHP 8.2 or newer for a current Laravel or Symfony project simultaneously.

Can I enable PHP extensions like Imagick or intl?

Yes, the cPanel-style panel allows toggling common PHP extensions per site, which is often required for image processing, locale-aware formatting, or specific database drivers a framework depends on.

Can I adjust php.ini settings myself?

Yes, settings like memory_limit, upload_max_filesize, and max_execution_time can be adjusted per site to match what a WordPress media library, Laravel import job, or file upload feature needs.

Does this hosting support Composer?

Yes, Composer is supported for installing and managing dependencies for Laravel, Symfony, Composer-managed WordPress plugins, and custom PHP projects.

Will an older PHP version run slower than a newer one?

LiteSpeed's PHP handling is tuned to perform well across supported PHP versions, so an account running a mix of legacy and current PHP sites doesn't have to sacrifice performance on the older version.

What does PHP hosting cost?

Web hosting with PHP version and extension control starts from $2.09/mo, with 24/7 human support available for configuration questions.

Get PHP hosting with real version control

Per-site PHP versions, extension toggles, and Composer support from $2.09/mo with 24/7 support.

Get Started