Laravel Hosting
All an Artisan deploy needs, already unpacked and waiting
A real SSH shell, Composer on the path, Git deploys, PHP 8.x you choose, Redis, plus queue workers and cron — sitting on fast NVMe cloud servers from $2.42/mo.
$2.42
Launch plan, billed annually
PHP 8.x
Set the release yourself
SSH
Composer, Git and Artisan
Redis
Cache, sessions and queues
The Toolchain
Composer, SSH and Git, in place before you turn up
A proper toolchain is what Laravel expects, and that is what sits on the counter here. Open SSH and Composer is waiting: composer install to fill the vendor directory, git pull to fetch the newest release, Artisan for migrations and for warming caches. It is the same routine you run locally, only this time pointed at production.
- Composer preinstalled and on the path
- A shell for Artisan and log tailing
- Clone and pull from your own repo
- No extra build step on the server
Why It Fits
Tooling that an Artisan app expects to find
Composer waiting in your PATH
Installed and sitting on the path before the account is even created, which means composer install, composer update and composer require all answer the very first time you type them. Nothing to fetch. Nothing to chase down.
A shell, not a substitute for one
Because the SSH is genuine, Artisan commands, tailing a log, clearing a cache and the ordinary housekeeping all work as they would on any Linux box you have ever sat in front of.
Deploys come from your repo
Pull straight out of GitHub, GitLab or Bitbucket over SSH. Releasing comes down to git pull, composer install and a single migrate, and it is those commands every single time.
Queues and the scheduler
Leave queue:work running to handle jobs and notifications, and let one cron entry call schedule:run. What is due gets worked out by Artisan from there.
Choose your PHP 8.x build
Hop between current 8.x releases whenever it suits, and set memory limits, execution time and OPcache on a per-site basis so they match what your Laravel version asks for.
Redis on every plan
Aim cache, sessions and queues at Redis. Heavy pages then stay responsive, and background jobs go on clearing, even after genuine traffic turns up.
Price Tags
Choose your Laravel plan
One project or a hundred, the toolkit is the same at every tier: SSH, Composer, Git and Redis included.
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.
Background Work
Queue workers and cron, ticking over where nobody sees
Once an app is past its first week, background processing becomes a necessity. Keep an Artisan queue worker alive so jobs, notifications and large exports run off the web request, then add one cron entry that fires schedule:run every minute. From there, Laravel's own scheduler takes over, and you are spared a long list of individual cron lines to maintain by hand.
- queue:work keeps chewing through jobs
- One cron line drives schedule:run
- Mail, notifications and exports leave the request
- Queues on Redis empty fast
Tier By Tier
What each tier gives you
Moving up takes a couple of clicks, for whenever the app and its traffic outgrow the shelf they are on.
| What you get | Launch | Pro | Elite |
|---|---|---|---|
| SSD space | 10 GB | 20 GB | 200 GB |
| Websites allowed | 1 | 25 | 100 |
| Cores & memory | 1 core / 2 GB | 1 core / 2 GB | 2 cores / 4 GB |
| MySQL database count | 25 MySQL | 50 MySQL | 100 MySQL |
| Shell, Composer & Git | |||
| Swap the PHP 8.x release | |||
| Redis on the plan | |||
| Queue workers & cron |
Keeping Pace
Pace comes from PHP 8.x and Redis
Speed begins with the runtime, and with whatever is backing the cache. Current PHP 8.x builds paired with OPcache keep compiled code sitting ready to run, while Redis holds cache entries, sessions and queued jobs in memory, so dynamic pages assemble quickly. Below all that, NVMe-class storage keeps migrations, asset delivery and database queries all moving briskly along.
- Recent PHP 8.x builds, OPcache on
- Redis for cache, sessions and queues
- NVMe-class storage under every app
- Memory and execution time set per site
Best Suited To
Built around the way Laravel work really goes
SaaS builds and side projects
Get an Artisan app in front of users without a hefty opening bill, then step up a tier once traffic shows up. Your deploy routine stays the same throughout.
APIs and service backends
Laravel APIs and Sanctum-guarded backends, held up by Composer, Redis and a proper shell instead of some locked-down panel handed to you.
Freelancers and small studios
Running several Laravel builds for clients? SSH and a familiar panel drive the whole shelf, with Git handling releases and staging fitting neatly into how you already work.
First Deploy
From repository to production in three moves
- 1
Choose a plan and open a shell
Pick Launch, Pro or Elite, then sign in over SSH. Composer, Git and PHP 8.x are sitting there already, waiting on your first command.
- 2
Clone the repo and wire it up
Pull the project down using Git, run composer install, fill in .env, and hand key:generate and migrate to Artisan, working against your MySQL database.
- 3
Start the queue and the scheduler
Start a queue worker to take the background jobs, then add a single cron line running schedule:run every minute. The rest of your timetable hangs off that one line.
Deploy Day
The deploy-day Artisan commands
Run these as part of a release so the app boots from cached config, routes and views instead of rebuilding them on every request.
php artisan config:cache
Collapse the entire config directory into a single cached array, and Laravel stops reading and parsing those files on each request that arrives.
php artisan route:cache
Compile the route table down to one file, and matching stays fast even where an app carries several hundred endpoints of its own.
php artisan view:cache
Build the Blade templates while deploying, so whoever arrives first after a release is not the one paying for that compilation.
php artisan event:cache
Cache the event listeners once discovered, and the framework stops scanning your whole application for them at every boot.
php artisan optimize
Warm the framework caches and the package caches together, so one command puts the app into production shape.
php artisan queue:restart
Tell the running workers to finish whatever job they hold, then restart clean, so the code that executes is the code you just deployed.
In The Box
Included with every Laravel plan here
- A genuine SSH shell
- Composer installed before you log in
- Git clone and pull deploys
- PHP 8.x releases you can swap
- The Artisan CLI, all of it
- Redis for cache, sessions and queues
- Queue workers that stay running
- A cron entry for schedule:run
- Up to 100 MySQL databases
- Free SSL, reissued automatically
- NVMe-class SSD storage
- Support you can reach at 3am
Laravel app parked with a different host?
Bring the repository, the database and your .env across over SSH and Git — our team will help make the move a quiet one.
Move My App OverFAQs
Laravel hosting, answered
Can I deploy over SSH and Git?
That is the route we expect you to take. A full SSH shell comes with every plan, so deploying here is the same Git workflow you already run locally. Clone out of GitHub, GitLab or Bitbucket into the account, run composer install to bring the vendor directory down, then copy your production values into .env. Artisan closes out the setup: php artisan key:generate for the application key, php artisan migrate for the tables. Every release afterwards is that same short list of commands. git pull for new commits, composer install if dependencies have shifted, php artisan migrate for anything fresh, and a cache clear to drop what has gone stale. This being a real shell rather than a restricted panel, you can tail a log, fix permissions on storage, or rerun a command when something wants a closer look. Aim the document root at the public folder and the app answers over HTTPS.
Will I have to install Composer first?
No. Composer ships with the account and is already on the path, so nothing wants downloading, unpacking or configuring ahead of your first deploy. As soon as provisioning finishes, open SSH and composer install, composer update, composer require and composer dump-autoload all run against the correct PHP binary. With Laravel that is more or less the whole game, since the framework itself and almost everything you bolt onto it (starter kits, Sanctum, Horizon and the rest) arrives through Composer rather than sitting in your repository. Authority stays with composer.json and composer.lock, so the exact versions you tested on your own machine are the versions that end up serving requests. Want Composer running against one particular PHP release? Covered, since the PHP version is set per site. Dependency management on the server, in other words, behaves the way it does on your laptop.
What PHP version does my Laravel app end up on?
Whichever site you are looking at, the control panel decides its runtime, and what we keep on the shelf are the current PHP 8.x releases. It matters, because each Laravel release states the minimum PHP it will accept. Anything recent tends to ask for 8.1 upwards; a long-term-support project of some age might still be tied to an earlier 8.x build. So instead of a single runtime pushed across the whole account, you choose domain by domain, and an elderly client site can share a plan with a brand-new build while neither gets in the other's way. The dials Laravel cares about are yours too: memory_limit when Artisan jobs and imports get heavy, max_execution_time for the slow stuff, OPcache to keep compiled code sitting in memory. Changes take effect at once and can be undone, so an upgrade is cheap to test. Try it on a staging domain, watch the test suite pass, then click production across.
How do queues and the scheduler work here?
Just as the Laravel documentation describes it, with nothing platform-specific to pick up. Queued work needs a persistent worker kept alive by php artisan queue:work, so jobs, notifications, mailables and large exports happen away from the web request instead of leaving a visitor staring at a spinner. Back that queue with Redis and the jobs get picked up and cleared quickly, even under genuine load. Scheduled work will not have you maintaining a wall of cron lines either. Everything is registered in Laravel's own scheduler, inside your application code, and the server wants exactly one cron entry running php artisan schedule:run every minute. From that single line, Laravel works out what is due and runs it, be it an hourly digest, a nightly cleanup or a weekly report. After each deploy, run php artisan queue:restart so the workers pick up your new code.
Is Redis available for cache and queues?
Yes: cache, sessions and queues, which between them cover the arrangement most production Laravel apps settle on. Aim the cache driver at Redis and expensive query results, rendered fragments and computed values come back out of memory rather than being rebuilt on every request. Shift sessions over and signed-in users stay quick and consistent as concurrency climbs. Set the queue connection to Redis and jobs are enqueued and processed with very little overhead, so workers hold pace when a rush arrives instead of dropping behind. All of it goes through the ordinary cache, session and queue driver entries in your .env file, and nothing custom is wanted at our end. Since Redis keeps this data in RAM rather than on disk, pages that once felt sluggish sharpen up noticeably, and background processing stops piling up the moment traffic spikes.
Is the document root able to sit on Laravel's public folder?
Yes, and it is how a Laravel app deserves to be served. One entry point is exposed inside public; your application code, your .env and storage all sit above the web root, where nobody can request them directly. Set that domain's document root to the project's public folder in the control panel, and requests then travel through index.php exactly as Laravel intends. Add free auto-renewing SSL on top and the app answers over HTTPS, with clean URLs and no index.php cluttering the address bar. Permissions on storage and bootstrap/cache take a single line over SSH, so caching, sessions and uploads behave properly from the very first request. Several apps on one account? Every domain gets a document root of its own, pointed at its own public folder, which keeps the projects cleanly apart while they share the same fast NVMe server.
More hosting worth a look
The whole application catalogue
One-click installs by the panel-load, spanning CMSes, forum software and shop platforms alike.
Web Hosting
Our ordinary cPanel accounts, sitting on the very same NVMe stack as these plans.
PHP Hosting
A choice of PHP 8.x releases, swapped in one click, with Composer and a shell.
Business Hosting
Extra CPU and RAM, for the Laravel app that has outgrown its starter plan.
Cloud VPS
Root access and dedicated resources, for an app that has earned a server to itself.
Ship your Laravel app today.
SSH, Composer, Git, PHP 8.x and Redis on the counter, with queue workers and cron already sorted.
Compare Laravel PlansLaravel is easy to develop and easy to deploy badly. The document root has to point at /public, the scheduler wants a cron entry and the queue wants a worker that stays alive — all of which are set here without opening a ticket. The hardware underneath belongs to Hosting Seller: NVMe drives, LiteSpeed out front, and a network desk staffed at every hour of the day.
We built it for PHP developers who build on Laravel, so the extras most hosts charge for are simply included: certificates, site transfers, daily copies and answers from people who run the servers.
Laravel with the parts it expects
Composer sits at the SSH prompt, the document root is yours to set, and cron runs the scheduler every minute. Queue workers are kept alive by the process manager, .env stays outside the web root where it belongs, and PHP 8.x with OPcache keeps the framework quick.
The hardware does the heavy lifting: 100% NVMe storage, LiteSpeed serving over HTTP/2, and a 99.9% uptime SLA our monitoring desk answers for. Quick pages keep visitors and search engines equally content.
What a Laravel plan costs
There is no second price waiting in year two. What the tag says is what the invoice says, this term and the next, and any introductory rate carries its renewal figure beside it. Every hosting plan carries a 30-day money-back guarantee, so trying us out costs you an afternoon at worst.
Laravel does not need a specialist platform invoice. It runs on the business shared plans, and if the queue gets serious, a KVM VPS with root starts at $13.52 a month.
How Laravel is served
Applications sit on NVMe storage behind LiteSpeed in our London datacentre, with daily backups of code and database. Deploy over Git, run your migrations, and let the monitoring watch the rest.
Nobody here waits for a customer to report an outage. Monitoring watches the fleet minute by minute and wakes an engineer first, so you usually hear about the fix rather than the fault.
- Composer, Git and Artisan over SSH
- Cron for the scheduler, workers for the queue
- Conditioned power and more than one network path
- Hardware we own, maintain and replace
Worth Knowing
What else you get in the box
Deploys that fit your pipeline
git pull, composer install, artisan migrate — by hand or from CI, over the same SSH connection.
Renewal-safe pricing
What you pay this year is what you pay the next. That is the whole policy.
99.9% uptime, in writing
The uptime figure sits in the SLA rather than in the marketing, and the monitoring desk answers for it.
A panel that makes sense
Everything you need day to day is two clicks away, and none of it is hidden behind a higher tier.
Move up without moving out
Bigger plans are one confirmation away, and you only pay the difference from the day you switch.
Nothing holding you here
Standard backups and standard panels mean you can leave whenever you like. Most people simply do not.
Starting Out
From order to live in three steps
- 1
Order in two minutes
Take a business tier, or a VPS if you want root as well.
- 2
Set the domain
Set the document root to /public and point the domain at it.
- 3
Start serving
Deploy with Git and Composer, then add the scheduler's one-minute cron line.
On the Shelf
Also included, no extra charge
- Every hosting plan comes with 30 days to change your mind
- A document root you set yourself
- Queue workers kept alive automatically
- 240+ applications on the one-click installer
- Account live within minutes of checkout
- Move up a tier without moving your files
- Registered in the UK, priced in US dollars
- Built for PHP developers who build on Laravel
Still Asking
Other questions that keep coming up
Do queues and the scheduler work on shared hosting?
Yes. Add the one-minute cron entry for the scheduler and run queue workers under the process manager so they restart if they die. Very heavy queues — thousands of jobs a minute — belong on a VPS, and our desk will say so rather than sell you a plan that struggles.
How long does setting up Laravel hosting take?
You will be logging into the panel within minutes. If your app lives somewhere else today, we copy it here first, test it, and only then move the DNS.
Is there a charge for certificates?
Free, fitted and self-renewing. The only reasons to buy a certificate here are a wildcard or a validated seal for procurement.
What if Laravel 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
PHP Hosting
PHP 5.6–8.4, OPcache, a version per site.
Business Hosting
Shared plans with SSH, Node and Python on the shelf.
VPS Hosting
KVM cloud servers with root from $13.52/mo.
Pulled from the Resource Library
How to Deploy with Git
The deployment workflow a Laravel project expects.
Best Web Application Hosting
Judge a host on app criteria: SSH, queues, databases.
How to Create a MySQL Database
That database step in every fresh Laravel install.