Laravel Cloud is the right default for most new apps in 2026 because it removes AWS account management while still giving you real servers under the hood. Choose Forge if you already run VPS infrastructure and want direct control over provisioning. Choose Vapor if your workload is genuinely spiky and you can tolerate cold starts in exchange for true scale-to-zero billing.

All three platforms exist to solve the same problem: getting a Laravel application from git push to a production URL without hand-rolling Nginx configs, queue workers, and TLS renewal scripts. But they make very different trade-offs on infrastructure ownership, cost predictability, and operational overhead — and the wrong choice compounds as your app grows. This guide breaks down where each platform actually fits, based on how they're architected, not just their marketing pages.

What Is Laravel Cloud, and How Is It Different From Forge and Vapor?

Laravel Cloud is Laravel's fully managed platform, launched publicly on February 24, 2025, alongside Laravel 12, and announced by creator Taylor Otwell at Laracon US 2024. It runs your application on containerized, horizontally scalable infrastructure on Amazon EC2, but abstracts away the AWS account entirely — you never touch IAM, VPCs, or EC2 consoles.

Where Forge is a control panel that provisions and manages servers you still technically own (in your own AWS/DigitalOcean/Linode account), Laravel Cloud owns the infrastructure layer itself. And where Vapor is serverless-first (built on AWS Lambda), Laravel Cloud is closer to "traditional compute with modern ergonomics" — it runs long-lived containers, not functions, which means no cold starts for your web tier and full compatibility with things like long-running queue workers and WebSocket connections out of the box.

Pricing is usage-based: Laravel Cloud starts with a $5/month plan and pay-as-you-go compute from roughly $0.01/hr, plus serverless Postgres billed separately from around $0.04/hr, according to Laravel's official pricing page. That structure matters for budgeting — it behaves more like a metered utility bill than a fixed hosting invoice.

What Is Laravel Forge Actually For?

Forge, Laravel's original deployment tool (in production since 2014), is not a hosting provider — it's a provisioning and management layer on top of infrastructure you already pay for separately (a DigitalOcean droplet, an AWS EC2 instance, a Linode VM, or your own bare-metal box). Forge handles server hardening, Nginx/PHP-FPM configuration, SSL via Let's Encrypt, queue worker supervision, scheduled cron jobs, and zero-downtime deployments via a simple dashboard or API.

The core trade-off: Forge gives you a real, persistent server you can SSH into, install arbitrary system packages on, and tune at the OS level. That's valuable if your app has dependencies Cloud/Vapor don't support well — custom binaries, specific PHP extensions, long-running non-HTTP processes, or compliance requirements that mandate infrastructure you control directly. The cost is that you're still responsible for capacity planning: if traffic spikes 10x, someone has to resize the droplet or add a load-balanced server, whether that's a human or a script you wrote.

Forge plans are flat-rate ($12–$39/month for the panel itself), separate from the underlying server cost you pay your cloud provider directly — so your total bill is Forge's fee plus whatever DigitalOcean or AWS charges for the boxes.

What Is Laravel Vapor, and When Does Serverless Make Sense?

Vapor deploys Laravel applications as AWS Lambda functions behind API Gateway, with SQS for queues and DynamoDB for caching in the default configuration. It is genuinely serverless: there is no persistent server to patch, and at zero traffic, you pay effectively nothing beyond storage and idle AWS resource minimums.

That model is ideal for workloads with unpredictable or bursty traffic — a marketing campaign landing page, an internal tool used a few hours a day, or a multi-tenant SaaS where most tenants are dormant most of the time. Vapor auto-scales concurrently far beyond what a fixed server fleet could handle without pre-provisioning.

The trade-offs are real, though: Lambda cold starts add latency to the first request after idle periods, execution has a hard timeout (Lambda functions max out at 15 minutes, which rules out long-running jobs without workarounds), and you inherit AWS-specific constraints — no persistent local filesystem, limited support for some PHP extensions, and a steeper debugging curve when something goes wrong inside the Lambda execution environment. Vapor itself is a paid product on top of your AWS bill, so total cost is Vapor's subscription plus AWS usage, similar in structure to Forge's model.

How Do Laravel Cloud, Forge, and Vapor Compare on Cost at Scale?

At low, steady traffic, Forge is usually cheapest in absolute dollar terms because you're paying flat-rate panel fees plus one small VPS. At spiky, low-average traffic, Vapor tends to win because scale-to-zero means you're not paying for idle capacity between traffic bursts. At moderate-to-high, fairly steady traffic — the profile of most B2B SaaS and internal business apps — Laravel Cloud's usage-based compute plus managed database and managed scaling typically comes out cheaper than the engineering time it would take to replicate that reliability manually on Forge.

The variable that matters most isn't the platform's list price — it's engineer-hours. A two-person startup team burns far more effective cost self-managing Forge server capacity during a traffic spike than they would paying Laravel Cloud's usage premium. A well-staffed platform team with existing AWS expertise, conversely, can often run Forge or raw EC2 cheaper than any managed option, because their time is already allocated to infrastructure work.

Which Platform Should a CTO Choose for a New Laravel App in 2026?

For a new product launch with an uncertain team size and traffic pattern, Laravel Cloud is the pragmatic default in 2026: it removes AWS account sprawl, supports the full Laravel feature set (queues, WebSockets, scheduled tasks, real Postgres) without Lambda's constraints, and its usage-based pricing scales down gracefully for early-stage traffic. PHP itself remains a safe long-term bet for this decision — W3Techs reports PHP still powers roughly 71.8% of all websites with a known server-side language as of mid-2026, meaning the hiring pool, tooling, and platform investment around Laravel aren't going anywhere.

Choose Forge instead when you have existing infrastructure investment, specific OS-level requirements Cloud/Vapor can't satisfy, or an ops-capable team that wants direct server access as a design choice, not a fallback.

Choose Vapor when your traffic is genuinely bursty and mostly idle — internal tools, seasonal campaigns, low-traffic multi-tenant apps — and you can architect around Lambda's execution-time and cold-start constraints from day one, rather than retrofitting them later.

The wrong move is picking based on brand familiarity alone. Match the platform to your traffic shape and team's operational bandwidth, and revisit the decision only when one of those two variables changes materially — not because a newer platform launched.

Frequently Asked Questions

Is Laravel Cloud built on top of Laravel Forge or Vapor?

No. Laravel Cloud is a separate, ground-up platform built by the Laravel core team, running on containerized infrastructure on Amazon EC2. It does not use Forge's provisioning model or Vapor's Lambda-based serverless architecture, though it borrows lessons from both.

Can I migrate an existing Forge-hosted app to Laravel Cloud?

Yes. Because Laravel Cloud runs standard containerized PHP rather than Lambda functions, most Forge-hosted apps migrate with minimal code changes — the main work is environment configuration, database migration, and DNS cutover, not rewriting queue jobs or removing filesystem dependencies the way a Vapor migration would require.

Does Laravel Vapor support WebSockets and long-running processes?

Not natively in the way a persistent server does. Lambda's execution model caps function runtime at 15 minutes and has no persistent process, so WebSocket servers and long-running queue workers typically need external services (like Pusher, Ably, or a separate always-on component) rather than running directly inside Vapor.

Is Laravel Forge still worth using in 2026 with Laravel Cloud available?

Yes, for teams that want or need direct server control — custom system packages, specific compliance postures, or infrastructure already provisioned in a particular cloud account. Forge hasn't been deprecated; it serves a genuinely different use case than a fully managed platform.

Which platform is cheapest for a low-traffic side project?

Usually Forge with a small VPS, since the flat panel fee plus a $5-$12/month droplet is predictable and low. Vapor can be cheaper still if traffic is close to zero most of the time, since Lambda billing approaches zero at idle, but Vapor's own subscription fee needs to be factored in.

Do I need AWS expertise to use Laravel Cloud?

No — that's the core value proposition. Laravel Cloud runs on AWS infrastructure but manages provisioning, scaling, SSL, and database management without requiring you to hold or configure an AWS account directly, unlike Vapor, which deploys into your own AWS account and assumes some familiarity with Lambda's execution model.