Laravel Forge vs Laravel Cloud

Connecting a provider and spinning up a server takes under 10 minutes. Getting a site deployed with the right environment variables, queue workers, and SSL sorted takes closer to 30. Not painful, but not instant either.

Auto-deploy on push to a branch is a first-class feature. Pull request preview environments are not - you need a GitHub Action (forge-previewer or similar) to get that. For most client projects this is a non-issue; for agencies used to Vercel-style PR previews, it is a gap.

The Forge CLI is capable - you can deploy, switch servers, manage sites, and tail logs from the terminal. It covers the common workflows but is not as polished as something like the Vercel CLI.

The 2025 Forge redesign is a significant improvement. Server list, site management, deployments, queues, and cron jobs are all well organized. Day-to-day operations are fast once you learn the layout.

Forge can absolutely serve static files via Nginx, but it is not optimized for static-first workflows the way Vercel or Netlify are. There is no built-in CDN layer, no automatic cache invalidation, and no edge distribution out of the box.

No native PR preview environments. Community workarounds exist (forge-previewer GitHub Action, Laravel Harbor) but they require setup and do not match the seamlessness of Vercel or Netlify.

Forge runs deployment scripts you define - npm install, npm run build, php artisan etc. so you can handle any build pipeline. It is manual configuration rather than automatic framework detection.

Supports any framework that runs on PHP or Node.js behind Nginx. Laravel is first-class. Astro, Next.js, or pure static sites work but require manual Nginx configuration - no magic zero-config detection.

Forge does not support serverless functions. Everything runs on persistent VPS instances. If you need serverless, look at Laravel Cloud (Vapor) or Vercel.

This is Forge's strongest suit. Laravel APIs, WebSocket servers, Node.js backends, Python workers - anything that needs a persistent process is completely at home. No timeouts, no cold starts, no artificial limits.

Forge does not manage Docker containers natively. You can install Docker on a Forge-provisioned server and run containers manually, but there is no Compose integration or container orchestration in the UI.

Queue workers (via Supervisor) and cron jobs are first-class UI features. You can configure workers per site, set restart policies, and define named cron schedules - all without touching a config file directly.

No built-in CDN. You get whatever your VPS provider delivers from its single datacenter. For performance-critical marketing sites you would front Forge with Cloudflare or a separate CDN.

No edge compute support. Forge is a centralized VPS management tool by design.

Zero cold starts. Your PHP-FPM process and application stay warm and resident. Response times are consistent under normal load.

Response times are entirely dependent on your VPS size and location. A well-tuned Forge server on a nearby DigitalOcean or Hetzner node is fast and consistent. You control the variables.

Forge installs and manages MySQL or PostgreSQL on the same server (or a dedicated database server) and handles automated backups on the Business plan. It is not a fully managed cloud database service - you own the instance - but for most client projects it is more than adequate.

No built-in object or file storage. You use whatever the VPS disk provides, or configure S3/R2 separately. Not a Forge concern - just configure your Laravel filesystem driver.

Because you control your own VPS, you can co-locate your app and database server in the same datacenter with zero latency between them. This is a meaningful advantage over platforms that restrict database region choices.

Environment variables are managed per site through the Forge dashboard and can be synced to the .env file on deploy. Straightforward and reliable. No advanced secret management, but covers all practical agency use cases.

Redirects are configured via Nginx rules, which you can edit directly in the Forge dashboard. More powerful than a rules UI, but requires knowing Nginx syntax.

Custom HTTP headers are configured via the Nginx config editor. Fully capable, not as point-and-click as Vercel headers config.

You can run staging and production as separate Forge sites (even on the same server). Environment variable management is per-site. It works well but requires manually maintaining two sites rather than having an environment abstraction layer.

Flat monthly subscription ($12/$19/$39). No usage meters, no bandwidth charges, no surprise invoices. You know exactly what Forge costs. Your VPS bill is also predictable - you pick a fixed-size server.

Zero overage risk from Forge itself. Your VPS provider may charge for bandwidth overages on very high-traffic servers, but that is a separate billing relationship you control.

For agencies managing 5-20+ client projects, the math is compelling. A $19/mo Growth plan manages unlimited servers. A $6/mo Hetzner VPS can comfortably run several Laravel sites. Total cost for a medium client project can be under $25/mo including both Forge and VPS.

No free tier. Forge requires a paid subscription from day one. The Hobby plan at $12/mo is inexpensive but not free.

Forge itself has been extremely stable over many years. Your application uptime depends on your VPS provider. Hetzner and DigitalOcean have both been highly reliable in our experience. You are not dependent on a single PaaS vendor's incident calendar.

Zero-downtime deployments (added in 2024) use atomic symlink swaps, so the previous release directory is preserved and can be re-linked manually if needed. There is no one-click rollback button in the UI - you would re-deploy from a previous Git SHA.

Forge surfaces Nginx error logs and deployment logs in the dashboard. For application logs you use Laravel's standard logging (storage/logs or a log aggregation service). Not as seamless as Vercel's real-time log streaming but workable.

The Business plan includes a server monitoring agent that alerts on CPU, memory, and disk thresholds. For deeper observability - APM, query tracing, error tracking - you integrate external tools like Sentry, Blackfire, or Better Uptime.

Minimal lock-in. Forge configures standard Ubuntu servers with standard Nginx and PHP-FPM. If you cancel Forge, your servers keep running exactly as configured. Nothing is proprietary.

Migrating away from Forge means switching to a different provisioning tool (Ploi, manual setup, etc.) while your servers and applications remain untouched. No data migration needed.

Everything Forge sets up is open standards: Nginx, PHP-FPM, MySQL, PostgreSQL, Redis, Supervisor, Let's Encrypt SSL. No proprietary runtime formats or deployment manifests.

Works well for PHP-based marketing sites (Statamic, WordPress) on a VPS. For pure static Astro or Next.js marketing sites, a CDN-first platform like Vercel or Netlify is a better fit unless you are already running a Forge server for the same client.

The ideal environment for full-stack Laravel web apps. Long-running processes, queues, databases, cron jobs, WebSockets - all handled. This is where Forge is inarguably the right choice.

Excellent for agencies. A single Growth plan manages unlimited client servers. Onboarding a new client project is fast once you have your provisioning workflow dialed in. Cost transparency makes client billing straightforward.