PHP Hosting
Ask for a given PHP release and that is what runs
Any current PHP version, changed per domain with one click, plus Composer, SSH and the extensions your project expects — all of it on quick NVMe servers.
$2.42
Price tag, billed annually
PHP 8.4
On the shelf now
1-click
Swap the release
Composer
Waiting in your PATH
Pick Your Release
Several PHP releases, one account
Two projects rarely want the same runtime. Instead of nailing every site to one release, the decision sits with you, domain by domain, and the control panel lets you change your mind whenever it suits.
Run the upgrade on a staging domain, satisfy yourself that it holds together, and only then bring production over. If a release starts playing up, a single click returns it to where it was.
- Current builds up to PHP 8.4
- A separate release for each domain
- One-click swaps, instant rollback
- Older 7.x builds still in stock
What You Are Buying
Set up around the way PHP work actually happens
Stock every release you still need
An old 7.x job and a fresh PHP 8.4 build share one account without complaint. Each domain gets handed the runtime its code was actually written against, not a compromise between the two.
A single click changes the version
Your panel has a PHP selector that fixes the release for each domain on its own. Give the newer build a go. If anything creaks, roll back in seconds.
Composer is already unpacked
Composer is already installed and answers over SSH the first time you log in, which means fetching packages and getting autoloading wired takes none of your setup time.
The extension shelf is well stocked
GD, mbstring, cURL, intl, OPcache, PDO, Imagick and plenty more sit there for you to enable or tune by hand. Nobody raises a ticket. Nobody waits.
Response times that hold up
NVMe drives, OPcache and LiteSpeed-grade caching all push the same way, which keeps pages landing fast when the visitor count climbs without warning.
Every account in its own lane
CloudLinux fences your CPU and memory allocation off from everyone else's. A script running wild on a neighbour's site stays a neighbour's headache, not yours.
Price Tags
PHP plans, plainly priced
The version selector, Composer and SSH sit on every tier. The only decision left is how much resource and how many sites you need.
Launch
Room for a single website, live today, at the plainest price we quote anywhere
$2.42/mo
$29.04 today · billed annually
the renewal price is the same
- SSD storage
- 10 GB
- Websites
- 1
- Bandwidth
- 500 GB
- CPU / RAM
- 1 core / 2 GB
- Databases
- 25 MySQL
- We register your domain name and charge nothing for the first year
- Your SSL certificate costs nothing, and we reissue it before expiry
- Sitting with another host? We move the site over at no charge
- An AI site builder comes with it: describe the site, then publish
- WordPress Toolkit included, and a backup runs daily
- SSH, Git and Composer at the command line
- Softaculous puts 240+ apps up in one click
- ImunifyAV+ watches every site for malware
- NVMe SSD underneath, LiteSpeed cache in front
- Mailboxes on your own domain, included
- MailChannels carries your outbound mail
- The latest cPanel, and real people to answer
- The account is live minutes after you order
Orders are rung up on Hosting Cheap, which is the billing platform behind our checkout.
Pro
One account, and enough shelf space on it for twenty-five separate sites
$4.66/mo
$55.92 today · billed annually
the renewal price is the same
- SSD storage
- 20 GB
- Websites
- 25
- Bandwidth
- 1 TB
- CPU / RAM
- 1 core / 2 GB
- Databases
- 50 MySQL
- First year of domain registration is on us, with nothing to pay
- SSL comes free, with a fresh certificate issued before the old lapses
- Already with another provider? We carry the site over and bill nothing
- An AI site builder is thrown in: say it, publish it
- WordPress Toolkit, plus a backup taken for you daily
- SSH, Git and Composer at the command line
- Softaculous puts 240+ apps up in one click
- ImunifyAV+ watches every site for malware
- NVMe SSD underneath, LiteSpeed cache in front
- Mailboxes on your own domain, included
- MailChannels carries your outbound mail
- The latest cPanel, and real people to answer
- The account is live minutes after you order
Orders are rung up on Hosting Cheap, which is the billing platform behind our checkout.
Elite
200 GB of NVMe storage, with enough processing power behind it to keep up
$7.08/mo
$84.96 today · billed annually
the renewal price is the same
- SSD storage
- 200 GB
- Websites
- 100
- Bandwidth
- 2 TB
- CPU / RAM
- 2 cores / 4 GB
- Databases
- 100 MySQL
- We register your domain name, free for the first year
- WordPress Toolkit Deluxe sits on the plan, nothing added
- Imunify360 watches the account, and a backup lands every 6 hours
- CloudLinux Pro with PHP X-Ray, which traces the slow code
- Python, Node.js and Ruby runtimes, installed and ready
- Priority support, whatever hour you need it
- An SSL certificate at no cost, renewed by us ahead of its expiry
- Currently parked with another host? We migrate the site for nothing
- An AI site builder is bundled in. Describe the thing, publish it
- NVMe SSD underneath, LiteSpeed cache in front
- SSH, Git and Composer at the command line
- Softaculous puts 240+ apps up in one click
- The account is live minutes after you order
Orders are rung up on Hosting Cheap, which is the billing platform behind our checkout.
The Toolkit
Composer, the extensions and a shell, waiting for you
Everything you reach for on a normal day is already in place before your first login. Pull dependencies down with Composer, switch on whichever extensions your framework lists, and edit the PHP settings with your own hands. There is no ticket for anyone to open.
Given SSH, a real command line and cron scheduling, your deploys, your migrations and your background jobs act exactly as they would on the laptop in front of you.
- Composer usable over SSH on day one
- GD, Imagick, mbstring, intl, cURL and the rest
- OPcache and PDO switched on
- memory_limit and upload caps in your hands
Response Times
PHP that stays on its feet when load arrives
Speed comes from a stack, never from one switch. NVMe drives cut the wait out of disk reads, OPcache parks compiled scripts in memory, and caching on the server side deletes whole steps between the incoming request and the finished page.
CloudLinux holds accounts apart from one another, which means the CPU and memory printed on your price tag belong to you and nobody else. Your app runs the same at the busiest hour as it does at three in the morning.
- NVMe SSD storage
- Bytecode cache plus object cache
- Whole-page caching on the server
- CloudLinux resource isolation
Settings You Control
The PHP settings you are free to adjust yourself
Every value that tends to trip a busy application is editable per site from your panel — no ticket, no queue, no waiting on us.
memory_limit
Push it higher when a data-heavy dashboard, the Magento backend, or a chunky report and PDF job would otherwise hit the ceiling partway through the work.
max_execution_time
Hand slow work a longer leash: bulk imports, image processing, a database migration of real size. None of it should be cut short before the job has finished.
upload_max_filesize & post_max_size
Raise both at once and big media files, backup archives and CSV feeds make it through, rather than stalling against a limit with no warning.
OPcache
Hold compiled bytecode in memory, then set its size and its timestamp checks so a production site is not rebuilding the identical scripts on every single request.
realpath cache
Open it wider for framework apps pulling in thousands of files, so PHP can read those paths out of memory instead of trekking back to disk every time.
max_input_vars
Bump it up for admin screens and forms posting hundreds of fields in a single go, so no value vanishes without trace the moment somebody hits submit.
Good Fit For
Software that tends to settle in well here
Framework projects
Laravel, Symfony, CodeIgniter and Slim find the CLI, the cron entries and the Composer support they assume will be there.
Content sites and shops
WordPress, Drupal, Joomla and Magento each get the PHP release their documentation names, with the memory headroom it asks for.
In-house and legacy code
Hand-rolled PHP, ageing codebases and in-house APIs hold on to the precise runtime and the extensions they were written against.
First Steps
Checkout to serving, in minutes
- 1
Pick a plan
Pick a tier, attach a domain. Every level carries the complete PHP version selector, including the cheapest, so it is not held back for the expensive plans.
- 2
Set the release
In the panel, set the PHP version against that domain, then tick whichever extensions your software says it needs.
- 3
Deploy with Composer
Come in over SSH, fire composer install, drop in your cron entries and push the code. From there the stack is answering traffic.
On The Ticket
What comes in the box
- Several PHP releases to choose from
- Per-domain version swaps in one click
- Composer installed before you arrive
- SSH and Git access on every plan
- Bytecode and object caching
- The usual PHP extensions on request
- memory_limit and upload caps you set
- Cron scheduling and a real CLI
- Space for up to 100 MySQL databases
- Free SSL, reissued automatically
Scaling Up
Move up a tier when traffic demands it
Begin on something small, then climb once the numbers argue for it. A larger plan raises your limits with no reinstall involved: the PHP release, the extensions, the databases and the files all cross over just as they stood.
- Change plans in a few clicks
- Up to 100 MySQL databases
- Higher limits the day you need them
- Code and data stay put
Asked Often
What people usually ask about PHP hosting
Which PHP releases can I actually run?
Every current PHP 8.x build is on the shelf, right up to PHP 8.4, and you choose per domain rather than once for the entire account. The older 7.x builds are stocked as well, so a legacy site that has been running for years and something you began last week can live side by side under one login without a row. Choosing site by site matters more than it first appears. Newer CMS platforms and framework releases tend to want PHP 8.2 or higher, whereas an ageing plugin, or a script somebody wrote a long time ago, might only ever have been tested against an earlier build. A switch takes effect at once and reverses at the same speed, so nothing forces you to march every site onto a new release in one afternoon. Move each one when it is ready. When a new release reaches official support we add it to the shelf, which leaves a clear route onto a maintained version well before the build you are on stops receiving fixes.
What does it take to switch a site onto another PHP release?
A single click covers the whole job. Open the PHP selector inside your control panel, pick the release you want for that domain, and it takes effect there and then, with no ticket to raise and no maintenance window to book. Because the setting belongs to the domain rather than the account, an upgrade can be rehearsed properly: aim a staging copy at the newer release, put the app through its paces, and promote production only once the thing behaves. Should a release cause friction, a function that has been removed, say, or a plugin whose author has not kept up, dropping back is just as immediate. Nothing strands you on a version that is causing grief. That same screen carries the extensions and the core settings for whichever release you landed on, so enabling the modules an app wants happens during the same visit. Staying current with PHP is a two-minute errand here, not an afternoon's project.
Is Composer part of the deal?
Yes, on every plan, already installed and reachable over SSH, which makes dependency work feel much as it does on your own laptop. Log in and composer install, composer update, composer require and composer dump-autoload all fire straight away against whichever PHP release that domain is pointed at. For modern PHP this counts, since Laravel, Symfony and a vast number of standalone libraries ship through Composer rather than as a zip you download and unpack by hand. Your composer.json and composer.lock live in the repository and remain in charge, so the versions you checked locally are the versions that end up serving real traffic. Put Composer aside and there is still a proper command line for everything else in the routine: running a framework's CLI, firing migrations, clearing caches, scripting a deploy. Cron sits alongside it. Anything you would otherwise kick off by hand can run to a schedule, with nothing for us to arrange at our end.
Can I switch extra PHP extensions on myself?
You can, straight from the panel, without asking a soul. The modules most projects want are already stocked: GD and Imagick for images, mbstring and intl for multibyte and localised text, cURL for outbound requests, PDO with the MySQL drivers for database work, then OPcache, zip, bcmath and a long tail of others behind them. What appears follows the PHP release you chose for that domain, so a single site can be kitted out precisely as it needs while nothing else on the account is disturbed. The same screen carries the php.ini values that trip up demanding software: memory_limit, max_execution_time and the upload caps. Meeting a CMS or a framework's stated requirements therefore comes down to matching the numbers printed in its documentation. Most extensions wake up the moment you enable them. For something more obscure that your app leans on, support will check whether it is available and talk you through switching it on, so you are never guessing whether a module exists at all.
Will my existing framework or CMS run here?
Very probably. Laravel, Symfony, CodeIgniter and Slim all run without drama, and so do the larger content and commerce platforms: WordPress, Drupal, Joomla and Magento. They are ordinary PHP software sitting on an ordinary PHP stack that happens to be fully equipped. A clean install mostly reduces to matching your environment to the requirements page. Choose the PHP release the software supports, enable the extensions it lists, and raise memory_limit or the upload cap where the docs ask for more. Deployment after that is your call: the one-click installer for the well-known platforms, or Git and Composer for a framework build or code of your own. A genuine CLI and cron between them handle the scheduled work these systems lean on, from queue workers through to the nightly tidy-up. Not sure a particular app will fit? Ask us. Odds are somebody here has set it up before and can give you a straight answer.
Where does the speed come from?
It comes from several layers each doing a share of the work, not from one magic setting. NVMe SSD storage strips disk latency out of every file read and every database query, so a page assembles quickly. OPcache holds compiled PHP bytecode in memory, which stops the server recompiling your scripts on each request, and that shows up plainly on framework-heavy applications. Caching at server level shortens the trip to a rendered page for anyone visiting twice, while object caching saves the database from answering an identical question over and over. Under all of it, CloudLinux hands each account its own ration of CPU and memory, so a neighbour having a rough day cannot quietly swallow yours mid-surge. Busy hour, quiet hour, your app behaves the same. With that groundwork laid, tuning OPcache, the realpath cache and the PHP release to suit one particular workload picks up whatever response time is still lying around.
More hosting worth a look
The whole application catalogue
The whole one-click install list in the panel, covering CMSes, forums and shop software.
Web Hosting
Our ordinary cPanel accounts, which run on the very NVMe stack these plans use.
Laravel Hosting
Artisan, Composer, Git deploys and Redis, all laid out the way Laravel expects.
Business Hosting
More CPU and more RAM in your ration, for hungry PHP software and heavier traffic.
Cloud VPS
Root access and resources of your own, for when a shared account runs out of room.
Get your PHP project live this afternoon.
Choose a plan, set the release, deploy over SSH with Composer — and reach a person on support if anything needs sorting.
See PHP PlansMost of the web still runs on PHP, and most PHP problems come down to the wrong version or a missing extension. Both are a dropdown here. Every account here sits on NVMe storage behind LiteSpeed, in our London datacentre watched by the same engineers who answer the tickets.
Made for developers working in the web's steadiest language. Free SSL, a free move from your current host, a daily backup and round-the-clock support are all in the price, with nothing waiting at the till.
PHP 5.6 through 8.4, your choice per site
Switch versions per site in the panel, enable the extensions an application needs, and set memory limits and execution times yourself. OPcache keeps compiled code in memory, LiteSpeed serves the result, and Composer, Git and cron sit at the SSH prompt for anything the panel does not cover.
Underneath, every app gets identical treatment — NVMe drives instead of spinning disks, LiteSpeed instead of a plain web server, and a 99.9% uptime figure written into the terms.
What PHP hosting costs here
Billing ought to be boring: one figure, stated up front, repeated at renewal, with promotions marked plainly instead of buried in a footnote. Every hosting plan carries a 30-day money-back guarantee, so trying us out costs you an afternoon at worst.
A legacy application on 5.6 and a new one on 8.4 can share a plan from $2.42 a month. No premium developer tier, no charge for switching versions, no extra fee for the command line.
How PHP is served
PHP runs per user on NVMe-backed accounts, so one busy site cannot spend another's memory. New releases are packaged and made available by our engineers as they land, so you are never left waiting for a version.
The unglamorous work — patching, monitoring, hardware replacement, filtering — is in the price and done by us. That is most of what you are actually buying.
- PHP 5.6 to 8.4, switchable per site
- OPcache, extensions and limits in your hands
- DDoS filtering at the network edge
- Patching handled by our own engineers
Worth Knowing
What else you get in the box
Legacy apps still welcome
Old code that wants an old version is not a problem here. Put that site on 5.6 and the next one on 8.4.
Transfers cost nothing
Our team brings your existing app across for nothing, usually within a day.
Yesterday is always there
Daily snapshots run on their own, so a bad update costs you minutes instead of data.
Someone at the counter
The queue is staffed by engineers around the clock, and answers usually arrive within 15 minutes.
Same price next year
Plans renew at the figure you joined on, with no second price waiting in year two.
99.9% uptime, in writing
Redundant our London datacentre, automatic failover and monitoring that pages an engineer before you notice.
Starting Out
From order to live in three steps
- 1
Choose your tier
Pick the tier that suits the applications you run.
- 2
Bring your domain
Point the domain and let the certificate fit itself.
- 3
Open for business
Set the PHP version per site, then deploy over Git or SFTP.
On the Shelf
Also included, no extra charge
- Every hosting plan comes with 30 days to change your mind
- Per-site PHP version and extension control
- Composer, Git and cron over SSH
- Automatic daily backups on every plan
- a 99.9% uptime target credited against the SLA
- Support answered by people, 24 hours a day
- NVMe storage as standard, not as an upgrade
- Renews at the figure you signed up on
Still Asking
Other questions that keep coming up
Can I change PHP version without breaking the site?
Change it on a staging copy first — cloning is a click — and switch the live site once it behaves. If something needs an extension that is not enabled, turn it on in the panel; if it is not listed at all, ask our desk and we will usually add it for you.
Is there a wait after I order?
Straight away. Orders provision themselves, and if you would rather we set things up, the desk is staffed at whatever hour you happen to be reading this.
Does the renewal price differ from the sign-up price?
It renews at the price you joined on. Where a first-term promotion applies, its renewal figure is printed next to it before you order, so there is nothing to discover later.
What if PHP hosting is not the right fit?
There is a 30-day money-back guarantee on the plan. Ask inside the month and you get your money back: no exit interview, and nobody transferring you to a team whose job is talking you out of it.
Read next
Laravel Hosting
Composer, queues and cron ready on arrival.
Web Hosting
cPanel on NVMe from $2.42/mo, SSL and the move included.
Business Hosting
Shared plans with SSH, Node and Python on the shelf.
Pulled from the Resource Library
How to Change Your PHP Version
Per-site version switching, safely.
What is PHP?
Plain English on the language behind most of the web today.
What is OPcache?
That invisible layer of speed sitting under every PHP site.