Laravel Hosting
Laravel hosting with the toolchain in place from the start
A genuine SSH shell, Composer ready, Git deploys, your choice of PHP 8.x, Redis, queue workers and cron — all on quick NVMe cloud servers from $2.42/mo.
$2.42
Entry price, billed annually
PHP 8.x
The release you run is your call
SSH
Git, Composer and Artisan waiting for you
Redis
Behind cache, sessions and queues
Your Toolkit
SSH, Composer and Git are running before your first sign-in
A serious toolchain is what Laravel assumes, and that's what waits for you here. Connect over SSH and the lot answers: composer install for the vendor directory, git pull to fetch the latest release, Artisan for migrations and cache warming. It is your local routine, pointed at production.
- Composer on the PATH from the start
- A real shell for Artisan and the logs
- git clone and pull from your repo
- No build hoops on the server
Made For Laravel
The things an Artisan app really needs
Composer is already on the PATH
Composer is in place, PATH set, before your account is handed over. composer install, composer update and composer require each work first time, with no download and no hunt for a binary.
A real shell, not an imitation
Because the SSH is genuine, Artisan commands, log tailing, cache clears and the usual housekeeping behave precisely as they would on any Linux box you have worked on.
Deploy straight from the repository
Pull over SSH from GitHub, GitLab or Bitbucket. Shipping a release amounts to git pull, composer install, then a migrate. Three commands, and no surprises in them.
Workers and scheduled work
Hold queue:work open for jobs and notifications. One cron entry then calls schedule:run, and Artisan decides for itself what happens to be due.
The PHP 8.x build is your call
Hop between current 8.x releases when it suits you, and tune the memory limits, the execution time and OPcache on a per-site basis to whatever your Laravel version demands.
Redis on every tier
Redis can hold the cache, the sessions and the queue. Do that and the heavy pages stay quick, the background jobs keep draining, and real traffic changes neither.
Pricing
Pick whichever Laravel plan fits you
One project or a hundred, the kit on every tier is identical: SSH, Composer, Git and Redis.
Sprint
One site, live within minutes, sitting on the lowest tier we run
$2.42/mo
$29.04 today · billed annually
the price never jumps at renewal
- SSD storage
- 10 GB
- Websites
- 1
- Bandwidth
- 500 GB
- CPU / RAM
- 1 core / 2 GB
- Databases
- 25 MySQL
- Year one of your domain name is charged at nothing
- SSL at no charge, reissued before it ever expires
- We take the site off your previous host and land it here, no charge
- Describe the site to the AI builder in the panel, then publish
- WordPress Toolkit comes with it, plus a fresh backup every day
- Real SSH access, and Git and Composer are preinstalled
- Softaculous installs 240+ apps in one click
- ImunifyAV+ sweeps every site for malware
- NVMe SSD storage behind a LiteSpeed cache
- Mailboxes on your own domain, included
- MailChannels gets your outbound mail delivered
- cPanel at its current release, staffed support 24/7
- Your account goes live minutes after checkout
The order gets finalised over at Hosting Cheap, the shared billing system that sits behind all of our brands.
Turbo
Twenty-five sites on a single account, none of them throttled
$4.66/mo
$55.92 today · billed annually
the price never jumps at renewal
- SSD storage
- 20 GB
- Websites
- 25
- Bandwidth
- 1 TB
- CPU / RAM
- 1 core / 2 GB
- Databases
- 50 MySQL
- Nothing to pay for the domain name in its first year
- A free certificate that reissues itself well before expiry
- Your site comes off the old host and settles onto ours, at no cost
- Tell the AI builder in the panel what you want, then hit publish
- WordPress Toolkit is bundled, with a daily backup alongside it
- Genuine SSH, plus Git and Composer set up in advance
- Softaculous installs 240+ apps in one click
- ImunifyAV+ sweeps every site for malware
- NVMe SSD storage behind a LiteSpeed cache
- Mailboxes on your own domain, included
- MailChannels gets your outbound mail delivered
- cPanel on its newest build, with people answering 24/7
- Your account goes live minutes after checkout
The order gets finalised over at Hosting Cheap, the shared billing system that sits behind all of our brands.
Nitro
200 GB of NVMe, and enough processing power to use every bit
$7.08/mo
$84.96 today · billed annually
the price never jumps at renewal
- SSD storage
- 200 GB
- Websites
- 100
- Bandwidth
- 2 TB
- CPU / RAM
- 2 cores / 4 GB
- Databases
- 100 MySQL
- The domain name's first year carries no charge at all
- WordPress Toolkit Deluxe comes in without an extra fee
- Backups run every 6 hours, and Imunify360 stands out in front
- CloudLinux Pro brings PHP X-Ray, which points at the slow code
- Push code in Node.js, Python or Ruby, each one already wired up
- Priority tickets answered whatever the clock says
- A certificate at no cost, renewing itself ahead of expiry
- Our engineers move the site over from your old host, and charge nothing
- An AI builder is thrown in: state what you want, then publish
- NVMe SSD storage behind a LiteSpeed cache
- A full command line, with SSH, Git and Composer on board
- Softaculous installs 240+ apps in one click
- Your account goes live minutes after checkout
The order gets finalised over at Hosting Cheap, the shared billing system that sits behind all of our brands.
Behind The Scenes
Queues and cron, grinding away out of sight
The moment an app grows past demo stage, background work stops being optional. Hold an Artisan queue worker open so jobs, notifications and large exports run clear of the web request. Then add a single cron entry firing schedule:run every minute. Laravel's scheduler takes care of the rest, and no sprawling crontab is required.
- queue:work clears the backlog
- One cron entry runs schedule:run
- Mail, alerts and exports leave the request
- Redis-backed queues drain fast
Compare Tiers
What comes at every level
Upgrading is a couple of clicks, for the day the app and its traffic want more room.
| What's included | Sprint | Turbo | Nitro |
|---|---|---|---|
| SSD storage allowance | 10 GB | 20 GB | 200 GB |
| Sites per account | 1 | 25 | 100 |
| Processor and memory | 1 core / 2 GB | 1 core / 2 GB | 2 cores / 4 GB |
| MySQL databases | 25 MySQL | 50 MySQL | 100 MySQL |
| SSH, Composer and Git | |||
| Switch PHP 8.x freely | |||
| Redis included | |||
| Workers and cron jobs |
Built For Speed
PHP 8.x and Redis do the heavy lifting
Speed begins with the runtime and with whatever sits behind the cache. Current PHP 8.x builds carrying OPcache hold compiled code ready to fire, and Redis keeps cache entries, sessions and queued jobs in memory, which lets a dynamic page assemble quickly. Under the whole arrangement, NVMe-class storage keeps migrations, assets and database queries moving along.
- Current PHP 8.x, OPcache active
- Redis serving cache, sessions and queues
- Every app on NVMe-class disks
- Memory and execution limits per site
Who Runs Here
Fitted to real Laravel projects
Products and side projects
Get an Artisan app in front of real users without a heavy bill at the start, then climb a tier once traffic asks for it. Your deploy routine does not change.
APIs and back-end services
Composer, Redis and a real shell sit behind Laravel APIs and Sanctum-protected back ends here, which beats working inside a locked-down panel.
Freelancers and small studios
A whole book of client Laravel projects fits here, running on Git deploys and staging-friendly workflows, driven from SSH and a control panel you already know.
Launch Sequence
Repository to production, three moves and done
- 1
Take a tier and sign in
Whichever you choose out of Launch, Pro and Elite, your next move is an SSH session. Composer, Git and PHP 8.x are sitting there, ready for the first command.
- 2
Clone it and set it up
Clone the project with Git, run composer install, fill out .env, and let Artisan handle key:generate and migrate against your MySQL database.
- 3
Start the workers and cron
Fire up a queue worker for the background jobs, then add a single cron line that calls schedule:run once a minute. Every scheduled task hangs off that one entry.
Release Ritual
The Artisan commands worth running at each release
Bake these into each deploy so config, routes and views load from cache rather than being rebuilt on every request.
php artisan config:cache
Fold the entire config directory into a single cached array, and Laravel stops parsing those files again on each request.
php artisan route:cache
Compile every route into one file, and matching stays instant even where the app carries hundreds of endpoints.
php artisan view:cache
Precompile the Blade templates while you deploy, so nobody arriving first after a release ends up paying the compilation cost.
php artisan event:cache
Cache the event listeners once discovered, and the framework stops rescanning your whole codebase for them at each boot.
php artisan optimize
Warm framework and package caches in one go, which drops the app into production trim from a single command.
php artisan queue:restart
Ask the running workers to complete whatever job they hold, then relaunch, so the next code to execute is the code you shipped a moment ago.
Included
Standard on every Laravel plan
- A genuine SSH shell
- Composer ready before your first login
- Deploys through git clone and pull
- PHP 8.x releases you can switch
- The whole Artisan command set
- Redis behind cache, sessions and queues
- Persistent queue workers
- Cron wired straight to schedule:run
- As many as 100 MySQL databases
- Free SSL, reissued automatically
- SSD storage of the NVMe class
- Help to hand at 3am
Is your Laravel app stranded elsewhere?
Carry the repository, database and .env over with Git and SSH — our team helps keep the switch quiet and clean.
Move My App AcrossCommon Questions
Laravel hosting questions
Is Git over SSH the way to deploy here?
Deployment here works the way you already deploy at home, because every plan carries a full SSH shell and this is precisely what the platform was built to do. Start by cloning the repository out of GitHub, GitLab or Bitbucket. composer install pulls the vendor directory down, and your production values go into .env. Two Artisan calls finish the setup, php artisan key:generate for the application key and php artisan migrate for the schema. From then on a release is a short, dull list: git pull for new commits, composer install where a dependency has moved, php artisan migrate for anything fresh, then a cache clear so nothing stale hangs about. What you have is a real shell, not a fenced panel, so tail a log, correct storage permissions or re-run a command whenever you need to. Point the document root at the public folder, and the application answers over HTTPS.
Do I have to install Composer myself?
No. Composer comes with the account and is already on the PATH, so nothing needs fetching, extracting or configuring before your first deploy. As soon as provisioning finishes you can connect over SSH, and composer install, composer update, composer require and composer dump-autoload all run against the correct PHP binary. For Laravel that covers virtually everything, since the framework and almost its entire ecosystem, starter kits and Sanctum and Horizon among them, arrive through Composer instead of living inside your repository. composer.json and composer.lock stay in charge, which means the versions you tested locally are the ones serving production traffic. Need Composer aimed at one specific PHP release? That works too, because PHP is set per site. Managing dependencies on the server feels the same as managing them on your laptop.
Which PHP release does the app run on?
Any current PHP 8.x build you like, chosen name by name from the control panel. Why that matters: a minimum PHP version is declared by every Laravel release, and recent ones tend to want 8.1 or above, while an older long-term-support project might still be happiest on an earlier 8.x build. No single runtime gets forced over the entire account. Give each name its own and a legacy client site can share a plan with a brand-new app, no argument between them. The version is only half of it. memory_limit for heavy Artisan jobs and imports, max_execution_time for slow work, OPcache holding compiled code resident: those settings belong to you as well. A change applies immediately and reverses just as fast, so an upgrade costs nothing to test. Try it on a staging name, let the test suite pass, then switch production over with one click.
How do queues and scheduled tasks run?
Precisely as the Laravel documentation lays it out, with nothing platform-specific for you to relearn. Queued work wants php artisan queue:work held open as a persistent worker, so jobs, notifications, mailables and large exports run away from the web request rather than leaving a visitor watching a spinner. Put Redis behind that queue and the jobs get picked up and finished fast, even under genuine load. Scheduling is where you drop the wall of cron lines. Declare it all in Laravel's scheduler inside the application, then give the server one cron entry calling php artisan schedule:run every minute. Off that single line Laravel decides what is due, whether an hourly digest, a nightly cleanup or a weekly report, and runs it. After each deploy, fire php artisan queue:restart so the workers pick up your new code.
Can Redis back cache, sessions and queues?
Yes. Cache, sessions and queues will all take Redis, which is where most production Laravel apps end up sooner or later. Point the cache driver there and expensive query results, rendered fragments and computed values come back out of memory rather than being rebuilt on every request. Shift sessions across and logged-in users stay quick and consistent as concurrency climbs. Aim the queue connection at Redis and jobs are queued and worked with very little overhead, so your workers hold pace through a rush instead of falling behind it. The whole thing goes through the ordinary cache, session and queue driver entries in .env, and nothing bespoke is needed at our end. Redis lives in RAM rather than on disk, so pages that used to drag tighten up and background work stops stacking the moment traffic rises.
Can we serve the app out of Laravel's public directory?
Yes, and it happens to be the correct way to serve Laravel. The framework puts a single entry point inside public, while your application code, .env and storage all live above the web root where no request can touch them. Set that name's document root to the project's public folder in the control panel, and traffic then runs through index.php exactly as Laravel intends. Add the free self-reissuing certificate and the app answers over HTTPS with tidy URLs, no index.php cluttering the address bar. Permissions on storage and bootstrap/cache take one line over SSH, after which caching, sessions and uploads behave from the very first request. Several apps on a single account? Give each name its own document root pointed at its own public folder, which keeps the projects properly separate while they share one quick NVMe server.
More hosting to explore
The whole application library
Whatever the panel can install in one click: forums, content platforms, store software and more besides.
Web Hosting
Ordinary cPanel hosting, riding the NVMe platform that carries these plans.
PHP Hosting
A handful of PHP 8.x releases, switched with one click, plus Composer and SSH.
Business Hosting
Extra CPU and RAM once a Laravel app has grown out of the plan it started on.
Cloud VPS
Root access and resources set aside, for the app that has earned a machine to itself.
Ship your Laravel app live today.
SSH, Composer, Git, PHP 8.x and Redis ready to go, with queue workers and cron squared away.
See Laravel PlansLaravel is a pleasure to develop and painfully easy to deploy wrongly. The document root has to hit /public, the scheduler needs its cron line and the queue needs a worker that survives, all of which is handled here without a ticket. Hosting & Domains owns the hardware underneath: NVMe drives, LiteSpeed in front, and a network desk that never shuts.
It is tuned for PHP developers shipping Laravel work, so what other hosts bill separately is standard here: certificates, site moves, nightly snapshots and answers from the people running the servers.
Laravel with its plumbing pre-fitted
Composer is at the SSH prompt, the document root is yours to point, and cron drives the scheduler every minute. Queue workers are kept alive by the process manager, .env sits safely outside the web root, and PHP 8.x with OPcache keeps the framework moving.
The hardware carries the weight: 100% NVMe storage, LiteSpeed over HTTP/2, and a 99.9% uptime SLA our monitoring desk stands behind. Quick pages please visitors and search engines equally.
The price of a Laravel-ready plan
No second price waits in year two. The listed rate is the invoiced rate, this term and every term after, and any opening offer shows its renewal figure beside it. Every hosting plan carries a 30-day money-back guarantee, so trying it risks nothing more than an afternoon.
Laravel needs no specialist platform bill. It runs on the business shared plans, and when the queue gets serious, a KVM VPS with root begins at $13.52 a month.
Laravel on the platform
Applications sit on NVMe storage behind LiteSpeed in our London datacentre, with code and database backed up each night. Deploy over Git, run the migrations, and let the monitoring cover the rest.
We do not wait for a customer to report an outage. Fleet monitoring runs minute by minute and wakes an engineer first, so what usually reaches you is the fix rather than the fault.
- SSH access to Composer, Git and Artisan
- Scheduler on cron, queue on live workers
- Redundant network paths and conditioned power
- We own, service and replace the hardware
Good to Know
More that's built in
CI-friendly deployments
git pull, composer install, artisan migrate: by hand or straight from CI, down a single SSH connection.
No renewal surprises
This year's bill equals next year's bill. That is the entire policy.
99.9% uptime, under SLA
The figure is in the SLA rather than only the marketing, and our monitoring desk answers for it.
A panel that stays out of the way
Everyday tools are two clicks deep at most, and none of them is held back for a bigger tier.
Scale up without relocating
A larger plan is one confirmation away, and you pay only the difference from the day you switch.
Free to leave any time
Standard panels and standard backups make leaving simple whenever you choose. Most customers never do.
Getting Going
Getting going takes three steps
- 1
Order in minutes
Take a business tier, or a VPS if root is on the list.
- 2
Wire the domain
Aim the document root at /public and attach the domain.
- 3
Start serving traffic
Deploy over Git and Composer, then add the scheduler's one-minute cron line.
In Every Plan
Thrown in without an extra charge
- 30 days in which to change your mind on any hosting plan
- Set your own document root
- Automatic supervision of queue workers
- One-click installer covering 240+ apps
- Accounts provisioned minutes after checkout
- Upgrade tiers without your files going anywhere
- Canadian-registered company, pricing in US dollars
- Shaped around PHP developers shipping Laravel work
Still Curious
Questions that keep coming up
Can shared hosting cope with Laravel queues and the scheduler?
It can. Add the scheduler's one-minute cron line and run the queue workers under the process manager so they respawn on failure. Genuinely heavy queues, thousands of jobs a minute, belong on a VPS, and our desk says so rather than selling you a plan that will struggle.
How soon can Laravel hosting be running?
The panel login reaches you within minutes. If the app currently lives elsewhere, we copy it across first, test it, and only then repoint the DNS.
Do certificates cost anything?
Free, installed, and renewing by itself. You would only buy a certificate for a wildcard or for a validated seal that procurement insists on.
What if Laravel hosting turns out not to suit me?
The plan carries a 30-day money-back guarantee. Say so inside the month and the refund is processed, with no exit interview and no hand-off to a retention team paid to argue.
Keep reading
PHP Hosting
PHP 5.6–8.4 with OPcache, switchable per site.
Business Hosting
Shared plans with SSH, Node and Python included as standard.
VPS Hosting
Root-access KVM cloud servers from $13.52/mo.
Handpicked from the Resource Library
Deploying with Git
Push to deploy, the workflow Laravel was built around.
Web Application Hosting: Our Picks
Queues, databases, SSH access. Judge a host against what your application asks for.
Creating a MySQL Database
Database setup comes first, and every fresh Laravel install begins there.