diff forge laravel cloud
Forge vs Laravel Cloud
Forge sets up and manages servers in your own cloud account, while Laravel Cloud is a managed platform that runs Laravel apps without servers for you to look after.
At a glance
- Built from
- 5 articles the community read
- Updated
- Nov 2026
- Read time
- 5 min
- Pricing
- how billing works, no figures
diff --short
The short version
Whether you want to own and look after servers, or hand infrastructure to a managed platform
Pick Forge if
- You want root access to your servers and the freedom to install anything on them
- You run non-PHP services such as a Next.js or Nuxt.js front end next to your apps 14
- You want to self-host a WebSocket server like Soketi rather than pay for Pusher 5
- You host many small sites and want to pack them onto a few servers you already pay for
- You prefer to choose your own cloud provider and keep the servers in your account
Pick Laravel Cloud if
- You would rather not handle server patching and want fixes applied for you, as with the 27-hour PHP and Node.js rollout 2
- Your traffic is uneven and you want scaling to be a setting rather than a project
- You already use Herd and want to deploy straight from it 3
- Your app is a fairly standard Laravel app without unusual system dependencies
Teams with a Laravel app plus a few non-PHP services, and no one keen on running servers, are not settled by either list. Deploy a staging copy to Cloud, check that every service has a home there, and compare the bill against a Forge server sized for the same load.
diff --table
Side by side
numbered notes link to the sources below
| Forge | Laravel Cloud | |
|---|---|---|
| What it is | A service that provisions and manages servers for you. | A managed platform that runs Laravel apps for you. |
| Where it runs | On servers in your own provider account, such as DigitalOcean, AWS or Hetzner. | On infrastructure run by Laravel, with no servers to log into. |
| Setup | Create a server, pick a type such as App or Web, then add sites and a deploy script 4. | Connect a repository, pick a region and attach resources. Herd 2 can deploy straight to Cloud 3. |
| Server access | Full SSH and root access. | No server access. You work through the platform's settings. |
| Non-PHP workloads | Can host Next.js, Nuxt.js and Soketi as Forge guides show 145. | Built around Laravel apps. Support for mixed stacks needs checking. |
| Scaling | Resize or add servers and set up a load balancer yourself. | Handled by the platform through settings. |
| Security patching | The server is yours to keep updated. Forge was affected during the PHP and Node.js rollout 2. | The Laravel team patched every Cloud app in place within about 27 hours 2. |
| Community material | Years of tutorials and deploy scripts assume a Forge server. | Newer, with fewer community guides so far. |
| Billing | Forge subscription plus a separate provider bill for servers. | One bill from Laravel, combining a plan with charges based on usage. |
What each is
Laravel Forge is a server management service. You connect an account at a provider such as DigitalOcean, AWS, Hetzner or Vultr, or point Forge at a server you already have. Forge then provisions it with Nginx, PHP, a database and the other usual parts. The server sits in your provider account and you have root access to it. Forge handles the configuration and deploys on top of that.
Laravel Cloud is a managed platform run by the Laravel team. You connect a git repository and Cloud builds and runs the app on infrastructure you never log into. Databases, caches, queue workers and scaling are settings on the application. Servers are not something you manage.
The practical split is ownership. With Forge you own a machine that Forge helps you run. With Cloud you own an application that Laravel runs.
Setup
On Forge, the first step is creating a server. You pick a provider, region, size and server type, and Forge installs the stack over SSH. The server type affects what gets installed. Forge's own Nuxt.js guide tells readers to use an "App" or "Web" server so that Nginx is present 4. Once the server exists, you add a site, link a repository and edit the deploy script. That script is a plain shell script, usually running composer install, php artisan migrate --force and any front-end build steps.
You also make some infrastructure choices up front. Whether the database lives on the app server or on its own machine, and whether you need a load balancer, are decisions you make at the start and can change later with more work.
On Cloud, you create an application from a repository, choose a region and attach resources such as a database or cache from the dashboard. There is no server to size in the traditional sense. Compute is set per environment. Laravel Herd 2 can also deploy straight to Laravel Cloud from the local development tool 3, which shortens the path from a local site to a running one for people already on Herd.
Forge setup takes longer and asks more of you, but every step can be seen and changed. Cloud setup is shorter, and the things it hides are also things you cannot reach into.
Day-to-day use
A typical Forge day looks like running a small fleet of servers. Push-to-deploy runs your script on each push. Queue workers and the scheduler are set up from the dashboard. SSL certificates come from Let's Encrypt. You can still SSH in to tail logs, change PHP settings or install something Forge does not know about. That access is a large part of Forge's appeal. You can run things that are not Laravel apps at all. Forge's own guides cover deploying a Next.js app 1, a Nuxt.js site 4 and Soketi, an open-source WebSocket server compatible with the Pusher protocol, as an alternative to paid Pusher when using Laravel Echo 5.
The cost of that freedom is upkeep. The server and its packages are yours. PHP version upgrades, disk space, database tuning and how the server behaves under a traffic spike stay with you, even though Forge makes many of those jobs easier. Scaling means resizing or adding servers and wiring up a load balancer.
On Cloud, daily work is mostly pushing code and watching deploys and metrics in the dashboard. Scaling is a setting rather than a project. The platform team also handles patching underneath you. When PHP and Node.js vulnerabilities were disclosed, the Laravel team patched every Cloud app in place within about 27 hours 2. The same post mortem covers what broke on Forge, Envoyer and Vapor during that rollout 2. That is a reminder that the Forge, Envoyer and Vapor model leaves more moving parts between a fix being released and your app running it.
The tradeoff is reach. Cloud is built around Laravel applications. If you need a custom system package, an unusual daemon or a non-PHP service next to the app, you are working within what the platform supports. On Forge you would just install it. How far Cloud stretches for mixed stacks is worth testing against your own app before you commit.
Ecosystem
Both are first-party Laravel products, so both track new Laravel releases and conventions closely. They sit in different parts of the lineup.
Forge has been around for years and sits next to Envoyer, which handles zero-downtime deploys, and Vapor, which runs serverless on AWS Lambda. A lot of community tutorials, deploy scripts and blog posts assume a Forge server. Some of these show it hosting JavaScript front ends 14 and WebSocket servers 5 next to PHP apps. Because the server is ordinary Ubuntu with Nginx, most general Linux knowledge carries over directly.
Cloud is the newer product, and recent first-party tooling is being connected to it. Herd 2's deploy feature targets Cloud 3. There are fewer community guides and long-running war stories for Cloud than for Forge. Some questions that Forge users can answer by searching, Cloud users will need to put to support or test themselves.
Moving between them is possible in both directions for a standard Laravel app. Moving away from Forge is often the easier direction, since nothing about the server is proprietary. Moving to Cloud means checking that every service you run on the box has a counterpart on the platform.
Cost
The two bill in different ways, which makes a direct comparison awkward.
With Forge you pay twice. Forge charges a subscription by plan, and your cloud provider charges separately for the servers, storage and bandwidth Forge manages. The provider bill depends on what you provision, not on traffic. A server you sized too large costs the same whether it is busy or idle, and a server sized too small stays small until you change it. Several sites can share one server, which keeps cost per site low for agencies and side projects.
Cloud bills through Laravel, combining a plan with charges based on the compute, databases and other resources your applications use. Costs follow usage more closely, which helps with uneven traffic. It also makes the monthly total harder to predict, especially for apps with heavy queue work or large databases.
Current prices for both products change often enough that you should read them from each pricing page rather than from an article. Model a month of your real traffic on each before deciding. For Forge, include the provider bill and the hours someone spends looking after servers. For Cloud, include the resources that scale with load.