Laravel Hosting 2026: Forge, Laravel Cloud, Vapor, or Self-Managed?

For a long time, the answer to "Which hosting for Laravel?" was straightforward: your own server, provisioned with Laravel Forge, on Hetzner or DigitalOcean. Since the launch of Laravel Cloud in February 2025 — alongside Laravel 12 — that has changed. For the first time, there is a fully managed platform operated by Laravel itself that requires no traditional server. Laravel teams now have four relevant options, and the right choice depends heavily on the project.

What has not changed: caution is still warranted with traditional shared hosting. Missing SSH access, no control over PHP modules, and limited configuration options make it practically unusable for serious Laravel applications.

Which hosting options exist for Laravel today?

The four paths we actually use in our projects in 2026 — each with its strengths and the scenarios it is designed for:

When is Laravel Cloud the right choice?

Laravel Cloud is the most interesting development in Laravel hosting of the past few years — and on many projects it is now the first option we evaluate. The platform abstracts away everything that is tedious about traditional server management: provisioning, security updates, SSL management, queue workers, backups, scaling. What remains is a git push — the rest takes care of itself.

The characteristics we find particularly relevant:

• Hibernation down to zero. Applications that nobody is currently using shut down automatically and incur no compute costs. On the next request, they spin back up within seconds. For prototypes, internal tools, and small customer portals this is a game-changer — the starter tier has no base fee.

• Preview environments per pull request. Every PR automatically gets its own production-like environment with its own database. Reviewers can click into the change and test it live, without anyone having to deploy manually. This visibly changes the review process — once you have it, you do not want to go back.

• Managed queue and worker clusters. Starting with the Growth tier, queue workers scale automatically with the backlog. You do not have to manage Horizon configuration, process supervision, or load balancing yourself.

• No additional expertise required. If you know Laravel, you can work with Laravel Cloud. There is no need to learn AWS, Docker, Terraform, or Kubernetes on top, just to get an app into production.

Concretely, we recommend Laravel Cloud in these scenarios:

• New SaaS products and MVPs. When you do not yet know whether your product will take off, the combination of auto-hibernation and usage-based billing is unbeatable. As long as there are no users, you pay nothing. Once the product scales, the platform scales with it.

• Internal tools and customer portals with irregular traffic. Exactly the kind of applications that tie up server capacity all day even though they are only used in the morning and evening benefit greatly from hibernation. Plus: less administrative overhead.

• Teams without a dedicated infrastructure role. If nobody in your organisation is permanently responsible for server operations, Laravel Cloud removes that risk completely. You no longer have a single point of failure resting on the one colleague who still remembers how the provisioning script works.

• Projects with strong review cultures. The per-PR preview environments from the Growth tier onward are a real productivity lever. If you rely on feature branches and pull-request reviews seriously, that alone is often worth the price difference.

When we do not recommend Laravel Cloud: for projects with very steady, high traffic (for example an established customer portal with reliably utilised workers) a traditional Forge server can be more economical, because you pay a fixed monthly rate rather than by usage. And for projects with special infrastructure requirements — custom system packages, specific network setups, on-premise connections — Cloud is too abstract. In those cases, you want the control of your own server.

You can find the official documentation and pricing information at cloud.laravel.com — the starter tier includes 5 USD of free credit and works without a credit card, so there is no risk in giving it a try.

Requirements for good Laravel hosting (on your own server)

If you choose your own server — with or without Forge as a management layer — these three fundamentals should be in place. With Laravel Cloud and Vapor, all of these points are already covered by the platform and you do not need to think about them further.

Application and database backups

It is not just business-critical applications that should be backed up regularly. While the source code exists in the repository alongside the server installation, other parts of the application need to be secured separately through backups.

With Laravel Cloud, database backups are already integrated into the platform (point-in-time recovery depending on the tier). Vapor also uses managed RDS databases with automated snapshots. In both cases, however, it remains relevant that uploads in the storage bucket (typically S3) should be backed up separately — for example with versioning and lifecycle policies. The following recommendations therefore apply primarily to your own servers, but the underlying principles do not change:

Hosting as reselling?

In the agency world, hosting reselling is a widespread approach that promises healthy margins with minimal effort. For clients, however, this model carries some risks: when the agency handles both development and hosting, the client enters a dependency relationship. In the event of disputes, the agency could deny access to the server.

With Laravel Cloud, this principle is particularly easy to put into practice: you set up your own Cloud organisation, bill directly with Laravel, and we join your organisation as a technical administrator. Once the collaboration ends, you revoke our access — the entire infrastructure stays in your hands.

Conclusion: which Laravel hosting option fits your project?

The days of a single standard answer to "Which hosting?" are over. The choice now clearly depends on the project — and when in doubt, a brief assessment is worthwhile before you commit technically.

• New SaaS product, MVP, or unpredictable traffic? Laravel Cloud. The combination of hibernation, usage-based billing, and per-pull-request preview environments is unbeatable for this scenario. Start without a credit card, with the starter tier suitable for real production use.

• Established product with steady traffic and cost pressure? Forge on your own VPS at Hetzner or DigitalOcean. With consistent load, the fixed monthly rate of a small server is often cheaper than usage-based billing, and you retain full control.

• Viral traffic spikes or deeply integrated AWS architecture? Laravel Vapor. Serverless execution on AWS Lambda scales from zero to thousands of requests per second without you needing to size a server. The prerequisite is AWS experience on the team.

• Special infrastructure, on-premise connections, or regulatory requirements? Your own VPS — possibly without Forge if very specific setups are required. Laravel Cloud and Vapor abstract away too much when your requirements sit below the framework level.

Depending on the project, we work with all four options and support our clients both with running traditional servers and with migrations to Laravel Cloud or Vapor. If you are unsure which path is right for your project, get in touch — half an hour of orientation at the start often saves weeks in operations later.