Laravel Cloud vs a VPS: When Managed Laravel Hosting Is Actually Worth It

Laravel Cloud used to have a real barrier to entry for a solo project. The Production plan started at $20 a month before you even used anything, which put it well above what most side projects and early-stage apps actually need. That changed with a pricing update that added a genuinely usage-based entry tier, and I think it is worth revisiting whether Laravel Cloud now makes sense next to a plain VPS for a small project.

What changed in the pricing

The current Sandbox plan on Laravel Cloud starts at $0 in base cost, with usage-based charges on top and hibernation enabled by default, meaning your app scales down and stops costing anything meaningful when nobody is actually hitting it. That is a real shift from the old model, where the cheapest real plan assumed a always-on production workload. Laravel's own announcement of the pricing put it plainly.

How much does Cloud cost? Our Sandbox plan is $0 + usage. Hibernation puts your application to sleep when it's not receiving requests, keeping costs low. It's the perfect plan for getting started. Our Production plan starts at $20 / month and includes autoscaling, custom

— Laravel (@laravelphp) February 24, 2025

Since that announcement, Laravel Cloud has kept adding real infrastructure features rather than just marketing polish, including a generally available managed MySQL offering with daily backups and configurable retention. Taylor Otwell walked through the current state of the platform directly at this year's Laracon keynote.

What you actually get that a VPS does not hand you for free

A bare VPS gives you full control and, at steady state, is usually the cheaper option in raw dollars. But every guide on this site about backing up a server, monitoring a cron job, renewing a certificate, or hardening SSH exists because none of that comes for free on a VPS. You are the one responsible for it.

Laravel Cloud folds a lot of that responsibility into the platform itself. Managed MySQL with automated backups removes the need to set up your own restic-to-R2 pipeline. Zero-downtime deploys and preview environments remove a chunk of the deployment tooling you would otherwise assemble yourself. Autoscaling on the Production tier means a traffic spike does not require you to notice it and resize a droplet by hand.

The catch: hibernation has a real cold-start cost

Scaling to zero is where the Sandbox plan's low cost actually comes from, and I think it is worth being honest about what that trades away. When your app has been idle and a request finally comes in, that request has to wake the application back up before it can respond, which means a real, noticeable delay on that first hit. For a personal project or an internal tool, that is a fine trade. For anything client-facing where a stranger's first impression is that cold-start delay, I would test it directly before committing to that tier for something that actually matters to a visitor.

A rough cost comparison

Take a small, low-traffic Laravel app. On a VPS, a Hetzner or DigitalOcean box in the $5 to $6 a month range runs it comfortably, at a fixed cost that does not move with traffic, but only after you have set up your own backups, monitoring, SSL renewal, and deployment process, using the same kind of setup covered across our VPS guides on this site.

On Laravel Cloud's Sandbox plan, the same low-traffic app might land close to that same $0 to $5 range in usage charges, since hibernation keeps idle time free. The real difference shows up as traffic grows. A VPS's fixed monthly cost stays flat until you outgrow the box entirely and have to resize it yourself. Laravel Cloud's usage-based pricing climbs more gradually and automatically, without you touching a dashboard, at the cost of paying a premium per unit of actual usage compared to owning the hardware outright.

Who should pick which

If you already run other VPS-hosted projects and are comfortable with the operational side, a VPS is very likely still the cheaper long-term option for anything with steady, predictable traffic, and you keep full control over the stack. If you are prototyping something new, want to ship without setting up backups and monitoring from scratch, or your project's traffic is genuinely unpredictable and bursty, the new Sandbox tier removes the cost excuse that used to make Laravel Cloud an easy no for a small project.

FAQ

Does the Sandbox plan support a custom domain?
Yes, custom domains are supported on the current entry-level plan, which was not always the case with earlier free tiers on similar platforms.

Can I move a project from a VPS to Laravel Cloud later without a rewrite?
Generally yes, since Laravel Cloud runs standard Laravel applications rather than requiring a different framework or a proprietary runtime. The main work is usually around environment configuration and any server-specific customizations you built directly into your VPS setup.

Is the managed MySQL offering suitable for a production app?
Laravel Cloud's own documentation describes it as production-ready, with sizing options and daily automated backups, so it is built for more than just testing.

What happens if my app outgrows the Sandbox plan?
You move to the Production tier, which starts at $20 a month and adds autoscaling and other features meant for a workload that needs to stay consistently responsive rather than hibernate between requests.

Does hibernation affect scheduled jobs or queue workers?
A hibernating application is not actively running, so anything relying on it being awake at a specific scheduled time is worth checking carefully against the platform's current documentation before relying on it for time-sensitive background work.

Bottom line

The old version of Laravel Cloud was easy to dismiss for a small project on cost alone. The current Sandbox plan removes that excuse, and the real decision now comes down to whether you would rather pay a bit more per unit of usage to skip the operational work, or keep the lower fixed cost of a VPS and own that work yourself. Neither answer is wrong, but it is a genuine choice now, not a foregone conclusion based on price.

Sources: Laravel Cloud, official pricing page; Laravel Cloud documentation, Plans and Pricing; Laravel, Everything We Announced at Laracon US 2025. Verified against official Laravel documentation on September 7, 2026.