Google "best hosting for Laravel" and the top results rank Cloudways next to DigitalOcean next to Laravel Forge — a managed platform, a bare VPS, and a deployment tool in the same numbered list. That's like asking "which is better: Eloquent, MySQL, or phpMyAdmin?" They're different layers of the same stack. Comparing them as competitors tells you nothing about what you should actually buy.

The reality: there is no product called "Laravel hosting." What exists is a stack you assemble from two or three separate services — a server, a management layer, and sometimes a deployment pipeline — and every combination has a different price tag, a different ops burden, and different ceilings you'll hit at 2 AM when something breaks.

As one developer on Laracasts put it: "With shared hosting, it is not possible to run supervisor to manage queue workers." That's the floor. Everything above it is a set of trade-offs nobody in the SERP top 10 actually calculates for you. So let's do that.

The Three Layers Every Laravel App Needs

Before comparing anything, you need to understand what you're buying. Every Laravel deployment sits on three layers:

Layer 1 — Server infrastructure. The actual machine running your code. DigitalOcean, Vultr, Hetzner, AWS EC2. You pick a size, you pick a region, you pay $6–$48/mo depending on specs. This layer gives you compute, storage, and a network connection. It gives you nothing Laravel-specific.

Layer 2 — Server management. The thing that turns a blank Ubuntu box into a Laravel-ready environment. Nginx configuration, PHP version management, SSL certificates, Supervisor for queue workers, cron for scheduled commands. Laravel Forge is the dominant option here ($12–$39/mo). Ploi and RunCloud are alternatives. Or you do it yourself for $0 and a weekend of initial setup.

Layer 3 — Deployment pipeline. How code gets from your repo to the server. GitHub Actions, Envoyer, Forge's built-in deployer, or git pull over SSH. Some management tools bundle this; some don't.

Products like Cloudways and Laravel Cloud bundle two or three layers into one bill. That's their value proposition — but it also means you can't swap one layer without replacing the whole stack, and the bundled price is always higher than assembling your own.

Layer 1: Server Infrastructure

For Laravel specifically, your server needs SSH access, enough RAM for Composer and Artisan (1 GB minimum, 2 GB if you're running queues alongside the web process), and the ability to install PHP extensions. Every VPS provider on this list delivers that from their cheapest tier.

At the $6/mo tier, DigitalOcean and Vultr are interchangeable. Same specs, same price, similar network performance in US regions. Vultr's High Performance line ($7/mo) gets you dedicated AMD EPYC cores instead of shared — a $1/mo upgrade that actually matters for Laravel apps doing heavy Eloquent queries or image processing.

Hetzner is the outlier. €5.49/mo gets you 2 vCPUs and 4 GB RAM — the same specs that cost $24/mo on DigitalOcean. The catch is bigger than latency: the CX line is not sold from Hetzner's US datacenters at all. CX23 and the ARM CAX plans are offered only from Falkenstein, Nuremberg and Helsinki. Hetzner does run US locations in Ashburn and Hillsboro, but they carry a separate and more expensive catalog — the cheapest instance you can order there is about $20.49/mo, which puts it within 15% of a DigitalOcean Droplet rather than a third of one. So this row is a European value play specifically. If your users are in North America, either accept transatlantic latency or price Hetzner from its US catalog, not from this table. Verified per datacenter against Hetzner's price API on 2026-07-30.

Layer 2: Server Management — The Forge Question

Laravel Forge is the default answer here, and for good reason. It provisions servers on DigitalOcean, Vultr, Hetzner, AWS, or any custom provider over SSH. It handles nginx, PHP, MySQL/PostgreSQL, Redis, Supervisor, SSL via Let's Encrypt, and zero-downtime deployments. For a Laravel developer, Forge eliminates roughly 80% of server administration.

Three tiers:

• Hobby — $12/mo ($120/yr annual). One server. Basic deployments, SSL, scheduling. No monitoring, no database backups through Forge.
• Growth — $19/mo ($199/yr annual). Unlimited servers. Server monitoring, database backups, deployment notifications. This is the tier where Forge becomes a complete management layer.
• Business — $39/mo ($399/yr annual). Everything in Growth plus team management, audit logs, and priority support. Worth it if 3+ developers touch the same infrastructure.

The $7/mo gap between Hobby and Growth buys you monitoring and automated database backups. If the app generates revenue, Growth is the right tier. You will want those backups at some point, and you'll want them already configured when that point arrives.

The Support Problem

Forge's biggest weakness isn't a feature gap — it's a support boundary. One Trustpilot reviewer described the experience bluntly: "Laravel Forge has unfortunately become a total nightmare… customer support is unacceptable."

The underlying issue is structural, not just staffing. Forge's support policy makes it explicit: "[Forge] only provides guidance for core Forge features… unable to provide guidance for custom server configurations." If your problem lives inside the Forge dashboard, they'll help. If it's an nginx tuning issue, a PHP-FPM memory leak, or a Supervisor process that won't restart — anything on the server itself — you're on your own.

For developers comfortable with SSH and basic Linux administration, this is a reasonable boundary. Forge handles the scaffolding; you handle the edge cases. But here's what I've seen happen more than once: a developer picks Forge because they don't want to deal with servers. For six months, everything is fine — Forge provisions, deploys, renews SSL, and the developer forgets the server exists. Then PHP-FPM starts leaking memory at 3 AM, the site goes down, they open a ticket, and the reply is "this falls outside Forge's support scope." That's the moment they realize Forge is a management tool, not a managed service. The gap doesn't announce itself. It waits for the worst possible night.

Alternatives to Forge

Ploi and RunCloud fill a similar role at similar price points. Neither has Forge's depth of framework integration — things like automatic Horizon configuration and native Pulse monitoring support that come from being built by the same team that builds Laravel. For most projects, Forge remains the path of least friction. But alternatives exist if you've been burned by the support boundary.

The All-in-One Options

Cloudways — Managed but Walled

Cloudways bundles server infrastructure and management into one product. The Standard DigitalOcean 1 GB plan starts at $11/mo; the Premium tier — NVMe storage, faster processors — runs $14/mo. Either way you get a managed stack: PHP, MySQL, Redis, nginx, SSL, and a deployment pipeline. No separate Forge subscription. No SSH setup. You deploy from a dashboard.

For a standard Laravel app — routes, controllers, a few scheduled commands, maybe a basic queue — Cloudways works well. The problems start when your queue architecture gets specific. As one user reported: "queue:work redis command is hardcoded into supervisor config, modifying requires root ownership."

Cloudways gives you a managed server. "Managed" means they control Supervisor. You can run queue workers, but you can't customize the Supervisor configuration without root access that Cloudways doesn't grant. For apps where the default queue setup is sufficient, this never matters. For apps with multiple queue connections, custom retry logic, or workers that need specific memory limits — and most production Laravel apps get there eventually — this ceiling is hard.

Laravel Cloud — Zero Ops, Premium Price

Launched in February 2025, Laravel Cloud is Taylor Otwell's answer to a different question: what if you didn't manage a server at all? No VPS to provision, no nginx to configure, no Supervisor to babysit. You push code, Cloud runs it.

The pricing is usage-based: $0.16 per vCPU-hour for compute, $0.20 per GB-month for MySQL storage, plus a base plan fee. A production app with steady traffic will land somewhere between $100 and $200/mo. That's 3–10x what a Forge + VPS stack costs for equivalent compute.

Whether that premium is worth it comes down to one number: your hourly rate. If you spend 5+ hours per month on server maintenance with Forge — updates, debugging Supervisor, SSL renewals, capacity planning — and your time is worth $40/hr, Cloud's premium costs less than the ops time it eliminates. If you enjoy server management or your app's traffic is predictable and low, you're paying for convenience you don't need.

Laravel Cloud is also still young. The feature set evolves monthly, documentation has gaps, and the community knowledge base that exists around Forge (8+ years of Stack Overflow answers, blog posts, tutorials) simply doesn't exist yet for Cloud. Early adopter tax is real.

Vapor — Serverless, Niche

Laravel Vapor runs your app on AWS Lambda. $39/mo for the platform, plus AWS usage fees. The right tool for apps with extreme traffic spikes and near-zero baseline load — a ticket sale that goes from 0 to 50,000 concurrent requests in 30 seconds, then back to nothing.

The wrong tool for apps that need persistent connections (WebSockets), long-running queue workers (Lambda caps at 15 minutes per execution), or predictable monthly bills. Vapor is a specialized instrument. If your app doesn't fit its constraints, no amount of configuration will make it fit.

TCO Reality Check

Every "best Laravel hosting" article compares individual product prices. Nobody compares full stack costs. This is what you actually pay when you add everything up:

The number to anchor on is $43/mo — Forge Growth plus a 4 GB VPS. That's the production baseline where you have monitoring, automated backups, enough RAM for queues alongside the web process, and full control over the server. Below that number, you're either doing ops yourself (Hetzner DIY at ~$6.49/mo) or accepting managed-platform limitations (Cloudways at $14/mo). Above it, you're paying for the luxury of not thinking about infrastructure (Cloud) or solving a scaling problem most apps never have (Vapor).

The Cloudways row stands out — $11/mo on Standard, $14/mo on Premium — cheaper than even the DIY-managed Forge stack. For a portfolio site, a content-driven Laravel app, or anything where your queue workers just send emails and process webhooks, it's genuinely the best value. The $4–$7/mo you save over the equivalent Forge Hobby + DO 1 GB stack comes with a ceiling on server-level customization, and whether that ceiling matters depends entirely on where your app goes in the next 12 months.

What I'd Actually Pick

Side project or learning: Forge Hobby + DigitalOcean 1 GB. $18/mo. A real production environment with zero-downtime deployments and SSL. $12/mo to never manually configure nginx is the best trade in this market.

Production SaaS under $10K MRR: Forge Growth + Vultr 4 GB. $43/mo. Monitoring, database backups, enough headroom for background jobs. When you need more compute later, you scale the Vultr instance without touching your Forge configuration.

Agency managing 5+ client sites: Forge Business at $39/mo covers unlimited servers with team management. Per-client cost is just the server ($6–$48/mo depending on the project) since Forge's flat rate covers everything.

Funded startup where developer time costs $150K+/yr: Laravel Cloud. The $100–$200/mo premium disappears when you calculate the engineering hours it replaces. But be honest about it — are you actually spending those hours on server ops, or buying convenience for a problem you haven't encountered yet?

What I'd avoid: Shared hosting for any Laravel project — the $3/mo you save costs you Supervisor, reliable cron, SSH debugging, and Composer memory. Cloudways for anything with complex queue architectures. Vapor unless your traffic pattern specifically demands serverless.

Verdict

There is no best hosting for Laravel. There's a stack — server, management layer, deployment pipeline — and the right combination depends on your budget, your tolerance for server ops, and your app's actual requirements today. Not its hypothetical requirements in two years.

If I had to pick one default: Forge Growth + a $24/mo VPS on DigitalOcean or Vultr. $43/mo total, full server control, production-grade monitoring, and a clear upgrade path in both directions. You can downgrade to Hobby if money gets tight, or migrate to Laravel Cloud if ops time becomes the real bottleneck. It's the stack that works for the widest range of Laravel projects without locking you into a platform you can't customize or a bill you can't predict.

One caveat: this entire framework assumes a single-server Laravel app. If you're running a multi-server setup — separate database server, Redis cluster, load-balanced web nodes — the cost math changes completely, and Forge's per-server model starts to look expensive compared to Cloud's bundled infrastructure. The TCO table above stops being useful once you outgrow a single box.

The mistake I see most often isn't picking the wrong provider. It's not calculating the full stack cost before committing, then being surprised three months later when the real bill is double what the landing page advertised. Now you have the numbers. Pick the row that matches your budget and your willingness to SSH into a box at midnight, and stop reading listicles.

FAQ

Can I run Laravel on shared hosting?

You can deploy the files. You can't run Supervisor for queue workers, you can't reliably execute artisan schedule:run via cron on most shared hosts, and you can't SSH in to debug production issues. If your app uses queues, scheduled tasks, or anything beyond basic request-response — shared hosting is a dead end. And if your app truly is just a brochure site with a contact form, you probably don't need Laravel.

Is Laravel Cloud worth it over Forge + VPS?

Math it out. Forge + a $24/mo VPS costs $43/mo. Cloud runs $100–$200/mo for comparable compute. That's a $57–$157/mo premium, or $700–$1,900 per year. If you spend more than 2–3 hours per month on server maintenance and your time is worth $50+/hr, Cloud saves money on net. If your server mostly runs itself between deployments — which describes most Laravel apps after initial setup — you're paying for peace of mind. Whether that's worth $700+/yr is a personal call, not a technical one.

Forge Hobby or Growth?

Growth. $7/mo more buys server monitoring and automated database backups. The monitoring alerts you before your users do. The backups are for the night you run a migration at 11 PM that drops a column you shouldn't have. Hobby is fine while the app doesn't generate revenue. The moment it does, upgrade immediately. Don't wait for the incident that convinces you.

Can I use Forge with Hetzner to save money?

Yes — Forge supports Hetzner as a server provider. Hetzner CX23 (€5.49/mo, about $6.49, for 2 vCPU / 4 GB RAM) plus Forge Hobby ($12/mo) gives you a production-capable stack for roughly $18.49/mo — still under the $24 a bare DigitalOcean Droplet costs before you add a panel. Two caveats, and the first one is a hard blocker rather than a latency trade-off: the CX line is sold only from Germany and Finland. Hetzner's US locations (Ashburn, Hillsboro) run a separate catalog starting around $20.49/mo, so this $18.49 stack is only available if you host in Europe. Second, Hetzner's support covers infrastructure only — even more hands-off than DigitalOcean. For projects targeting European audiences, it is still the best deal on this page; for US-hosted projects it is not on the table.

What about Ploi or RunCloud instead of Forge?

Both work. They handle the same core job — provisioning, SSL, Supervisor, deployments — at similar price points to Forge. Where they fall short is first-party integration depth: Forge automatically configures Horizon, natively supports Pulse monitoring, and its deployment recipes understand Laravel's storage/ symlinks and .env handling out of the box. The decision rule is simple: if Forge's support boundary burned you on a specific incident and you need more hand-holding on server-level issues, try Ploi or RunCloud. If you've never hit that boundary, Forge's ecosystem advantage — 8 years of community answers for every edge case — is worth more than a few dollars saved.

How much RAM does a Laravel app actually need?

Fresh install with PHP-FPM, MySQL, and Redis fits in 1 GB — barely. Composer's update command can spike to 1.5 GB on projects with 80+ packages. Add a queue worker and baseline usage sits at 1.2–1.8 GB. Call 2 GB the honest minimum for production with web + queue + Redis on the same server, and 4 GB the starting point if you'd rather not think about memory for the first year.