Trade Desk
Laravel hosting plans — Hosting somebody else's Laravel app without inheriting their pager
The build is finished and the client wants you to keep it running — the real question is what that costs you per month and who gets woken when the queue stops.
Straight answer first
Put an ordinary client app on Business hosting with SSH, Composer and per-site PHP, and move it to a VPS the moment queues and long-running daemons appear — both routes are on our shelf, and the second is a line you can bill for.
The decision is commercial as much as technical. A Laravel site on a shared-class account costs you almost nothing per client and can be administered from a panel. A Laravel site with Horizon, websockets and a supervisord tree is a managed server in all but name, and pricing it as though it were a website is how studios end up doing free operations work for years.
Written by the Hosting Seller staff · Checked 24 August 2026
99.9%
Uptime target behind your SLA
24/7
Engineers on call for you
Free
SSL on every client site
NVMe
Disks under every account
Written for studios and resellers who build in Laravel and then get asked to keep the thing alive. The framework is not the hard part. The hard part is that an application, unlike a brochure site, has a running process, a queue and a deploy step, and each of those is a support ticket waiting to become somebody's responsibility.
The Laravel scheduler hangs off a single cron entry that drives everything else. A host with genuine cron and shell access lets the framework behave as designed; a host without them turns every scheduled job into a workaround you will still be maintaining long after you have forgotten why it exists.
The account shape a client app actually needs
Four things decide whether a Laravel site is comfortable on a shared-class account: SSH, Composer, a current PHP with the usual extension list, and real cron. Business Standard carries all four, with PostgreSQL beside MySQL and a hundred addon domains, which is generous room if you are running several client projects side by side.
What it does not carry is root. No supervisord, no custom system packages, no long-lived socket server. Know that boundary before you quote, because discovering it during a launch week is expensive in a way no hosting bill has ever been.
Who holds the deploy key
Decide early whether the client's developers get SSH or whether every release goes through you. Both are defensible; only one of them is compatible with charging a retainer for uptime. Hand out shell access and you have handed out the ability to break production at midnight and telephone you about it at half past.
The practical middle ground is a deploy user with its own key, a Git remote and a documented release command. Staging copies mean the change gets proved on a clone before it touches the live site, which is also the answer to give a client who asks why a release takes twenty minutes rather than two.
What this client costs you every month
Business Standard is one flat monthly figure billed annually. Put a single substantial client app on it and that figure is your entire cost of goods for the account; spread three modest ones across its hundred addon domains and the cost per app falls to a third of it. Set your retainer against that number, not against what the client imagines hosting costs.
Bill the attention separately from the platform. Hosting is a predictable figure; a framework upgrade, a queue that needs re-plumbing or a third-party API that changed under you is time, and time is the thing studios routinely give away because it arrived dressed as a hosting problem.
The point where one client earns its own server
Horizon, websockets at volume, a resident daemon or a system package the framework needs — any of those and the account should become a VPS with root. Say so plainly and price it as an upgrade rather than absorbing it, because the alternative is one client quietly consuming the margin from all the others.
Nothing about that move needs to be dramatic. Shared, VPS and dedicated all sit under one roof here, the migration is done by our staff at no charge, and the client experiences it as a maintenance window rather than a change of supplier.
The supplier writing this would like the account
No league table, no referral fee, no pretence of neutrality. We host, we would like to host for you, and stating it up front is cheaper than the alternative — which is you finding out later and wondering what else was staged.
NVMe disks and LiteSpeed caching sit on the shelf at every price point rather than being reserved for whichever tier we would prefer to sell you.
- Tests you can run before you commit a client
- One trade price, held at renewal
- Free migration for the sites you already host
- A refund policy with no small print
Why Hosting Seller
On every plan, as standard
The toolchain switched on already
SSH, Composer, Git and real cron are fittings on the plans built for developers, not an upgrade you request per account.
Postgres beside MySQL
Business Standard carries both, so a client app with a Postgres schema does not force you onto a server you never wanted to manage.
Matched to this verdict
The Business Standard plan is this page's recommendation made concrete — one flat price, essentials included, upgradeable in place.
A ladder you can move a client up
Shared, VPS and dedicated under one supplier means growth is an upgrade conversation, not a migration project you have to sell twice.
Staging on the account
Clone, break, prove, push. A release process you can describe to a client without either of you having to cross your fingers.
A supplier with a company number
IGI Security Services Ltd, registered in England and Wales — the paper trail your own client would want you to have checked.
First Steps
From choosing to live
- 1
Draw the root line before you quote
List what the app needs to run: queues, daemons, system packages. If any of them wants root, the answer is a VPS and the quote should say so on day one.
- 2
Decide who deploys
Either the client's developers get a deploy user and the release is theirs, or every change comes through you and the retainer reflects it. Leaving it vague is how uptime becomes free.
- 3
Prove it on a clone first
Move one app across free, run a fortnight of real releases against staging inside the money-back window, and only then plan the rest of the book.
In the Box
Packed with every plan
- SSH, Git and Composer switched on from the start
- Real cron, so the Laravel scheduler runs as it was designed to
- PHP versions chosen per site from the panel
- PostgreSQL sitting alongside MySQL on Business plans
- Staging copies for proving a release before a client sees it
- Site migrations handled by our staff at no charge
- LiteSpeed caching running at the server rather than as a plugin
- A 99.9% uptime target, watched by monitoring day and night
- Nothing added at setup — no joining fee, ever
- The renewal price on the tag matches the order price
Across the Counter
Things people ask us all the time
Can I give a client's developer SSH without giving away the account?
Yes, and you should. Issue a deploy user with its own key scoped to that site rather than sharing the account login. It keeps the release path auditable, it survives the developer leaving, and revoking access becomes one command instead of a password change that breaks four other things.
How many client Laravel apps sensibly share one Business account?
It depends on traffic rather than count. The allowance runs to a hundred addon domains, but PHP workers and database load are what actually run out. Two or three busy apps, or a larger number of quiet ones, is the honest shape — and the first symptom of overloading is slow admin pages, not an outage.
Who is on the hook when a queue stops overnight?
Whoever your contract says, which is why the contract should say. Our engineers cover the platform at any hour: the server, the network, the panel. The application layer is yours or the client's, so decide which, write it down, and price it accordingly.
Does moving a client from shared to VPS mean starting again?
No. Both sit with the same supplier, our staff do the transfer at no charge, and it is usually finished inside a day with the old account still serving until the new one takes the traffic. The client sees a maintenance note; they do not see a change of provider.
Read next
Dedicated Server Value
When a client workload outgrows shared hosting: what a real machine costs and what should already be in the price.
Joomla vs WordPress
Two content systems compared for the studio that has to support whichever one the client picks.
Laravel Hosting
Composer, SSH and Git deploys on hosting shaped for Laravel apps.
Web Hosting
cPanel hosting on NVMe disks, with SSL, migration and year-one domain included.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Host the app, and bill for it properly.
SSH and Composer switched on, staging on the account, free migrations and one price that does not move at renewal.
See Laravel Hosting plans