Laravel Forge vs Laravel Cloud: Which One Actually Fits Your Project

I get asked this a fair bit, usually by someone who's read that Laravel Cloud exists and wonders if it makes Forge obsolete. It doesn't. I run projects on both right now, and the honest answer is that they solve different problems. Picking the wrong one doesn't break your app, but it does mean you're paying for flexibility you don't need, or fighting for control you were never going to use anyway.

What Forge actually gives you

Forge isn't hosting. It's a tool that provisions and manages a server for you, on whatever provider you point it at: DigitalOcean, Hetzner, Vultr, AWS EC2, wherever. It installs Nginx, PHP, your queue workers, sets up cron, wires up deployments from git, and gives you a dashboard to manage all of it without SSHing in for every small change.

The server is yours. You rent the box, you own what's on it, and you can put anything on it, custom PHP extensions, a specific version of ImageMagick, a background process that has nothing to do with Laravel. I've used Forge for projects that needed unusual software combinations that a managed platform simply wouldn't allow.

The cost is predictable because it's tied to the box, not your traffic. A £20 a month droplet costs £20 a month whether it serves 500 requests or 50,000, right up until it can't cope and you need a bigger box.

What Laravel Cloud actually gives you

Laravel Cloud is a fully managed platform. There's no server to think about at all. You push code, it builds, deploys and scales automatically. Databases, queues, object storage and caching are all managed for you, and billing is based on what you actually use rather than a box size you have to guess in advance.

For an MVP or a new product with unpredictable traffic, that's genuinely useful. You're not paying for a server sized for peak load that sits mostly idle. And when I don't want to think about OS patching, PHP version upgrades or disk space alerts at 2am, Cloud takes that off my plate entirely.

Where Forge still wins

• Cost at steady, predictable scale. If you know roughly what your traffic looks like, a fixed-price server is usually cheaper than usage-based billing over a year.
• Full control over the environment. Odd dependencies, legacy PHP versions, custom cron jobs, multiple apps sharing one box. Forge doesn't stop you doing any of it.
• Ownership. The server, the database, the backups, all of it sits on infrastructure the client actually controls. If I'm not around, another developer can SSH in and see exactly what's there. That matters more than people think when you're weighing up who actually owns the code and infrastructure behind your software.
• Data residency and specific compliance needs. If a client needs data sat on a specific provider or region for contractual reasons, provisioning your own server gives you that certainty directly.

Where Laravel Cloud still wins

• Zero server maintenance. No patching, no disk alerts, no "why did the queue worker die overnight" debugging. That's real time saved on smaller projects.
• Spiky, unpredictable traffic. A product launch, a marketing campaign, a seasonal spike. Cloud scales with it automatically instead of you needing to resize a server manually and hope you got the timing right.
• Speed to get something live. This is where it overlaps with the work I do turning an AI-built prototype into something production-ready. If a client has come from Lovable, Bolt or Replit and needs infrastructure that just works without weeks of DevOps setup, Cloud gets it there faster. I've written before about taking an AI-built prototype safely into production, and the hosting decision is part of that conversation every time.
• Fewer moving parts to hand over. For a small team without any DevOps knowledge, Cloud is less to explain and less that can go wrong through neglect.

The trade-offs nobody puts in the marketing copy

Cloud's usage-based billing cuts both ways. It's brilliant when traffic is low or spiky in your favour, but a runaway queue job or a scraper hammering your API can turn into a bill you didn't expect. On Forge, the same problem just slows your server down. Annoying, but capped.

Forge assumes someone is actually watching the server. Security patches, PHP version upgrades, disk space, none of that happens on its own. If nobody's maintaining it, a Forge server quietly rots in a way a managed platform won't let happen.

And Cloud, being newer and more opinionated, fits Laravel's own conventions closely. That's mostly a strength, but it means workloads that don't fit the standard shape (unusual background processes, third-party binaries, non-standard queue setups) are more awkward to force in.

How I actually decide

For a new SaaS MVP with traffic I can't predict yet, I lean towards Cloud. It removes a category of decisions I'd otherwise have to guess at before launch. For an established business running a steady internal system or an integration-heavy platform where I know the load and want full control over the stack, Forge on a properly sized server is usually cheaper and gives more room to do exactly what the project needs. Some clients end up on both at different points as the project matures, and that's fine. The infrastructure should follow the project's actual needs, not a preference I picked once and never revisit.

If you're weighing this up for your own build, it's worth having the conversation before the app is written, not after. Get in touch through my contact page and I'll give you a straight answer on which one fits, based on what you're actually building.