Deploy Next.js and Nuxt Apps on Laravel Cloud
Laravel Cloud now supports deploying Next.js and Nuxt frontends directly alongside your Laravel backend. Same repository, same platform, same bill — no more juggling two separate hosting accounts and two deployment pipelines.
The Problem It Solves
Most Laravel APIs don't stand alone. Teams typically pair them with a customer-facing frontend, admin dashboard, or storefront built in Next.js or Nuxt. Until now, that frontend lived somewhere else: a separate host, a separate deployment workflow, and a separate invoice. Every release meant coordinating two deploys, watching two dashboards, and debugging environment mismatches between the API URL your frontend expected and the one your backend actually exposed.
With Next.js and Nuxt support on Laravel Cloud, you push once and both the frontend and backend build, deploy, and scale from the same repository.
How It Works: Monorepo-Aware Deployments
Next.js and Nuxt deployments run on the same mechanism as Laravel Cloud's monorepo support. When you create a new application, Cloud analyses your repository and determines whether it contains one application or multiple. If it finds more than one — for example, a Laravel backend and a Next.js frontend — it shows you the top-level directories and lets you pick which one each application should deploy from.
For a repository with both a backend and a frontend:
- Create a Cloud application for the backend, attach your repository, and select the backend directory as the root.
- Create a second Cloud application for the frontend, attach the same repository, and select the frontend directory as the root.
Every directory in the repository remains available during the build, so your frontend can still reference shared packages or sibling folders if needed.
Framework-Aware Configuration
Each application is a fully independent Cloud resource with its own environment variables, instances, scaling settings, domains, and attached services. Because Cloud is framework-aware, it exposes different configuration options based on each application's runtime — your Next.js or Nuxt app is configured differently from your Laravel backend without manual intervention.
This independence also means you can size and scale each application on its own terms. Frontends and backends tend to have different traffic patterns, so treating them as separate deployable units is the right model.
What Changed Under the Hood
- Nginx for all runtimes. Every multi-language application, including Next.js and Nuxt, now runs behind Nginx — the same web server Cloud already uses for PHP.
- Configurable ports. Ports are no longer hardcoded to a framework default.
- Runtime access logs. Request-level logs are now visible in the dashboard for non-PHP applications.
- Faster JavaScript builds. Build times for JavaScript applications have been improved.
- Framework picker updated. When creating a new application, Next.js and Nuxt appear alongside Laravel and Symfony in the framework selector.
One Platform, One Bill
Teams can deploy Next.js and Nuxt frontends on every Laravel Cloud plan at no additional cost. Instead of managing two sets of infrastructure and two sets of team permissions, everything lives in one Cloud organisation:
- One bill for the entire stack.
- One place to grant Admin or Developer access across all applications.
- No per-seat charges on a separate frontend platform.
This is particularly valuable for agencies running multiple client sites, each with its own frontend, and for solo founders who don't want to learn a second infrastructure stack just to put a UI in front of their API.
Key Takeaways
- Next.js and Nuxt deployments are now available on all Laravel Cloud plans at no extra cost.
- Both frameworks use the same monorepo mechanism: attach one repository, select different root directories per application.
- Each application scales independently with its own environment variables, domains, and instances.
- Nginx now backs all runtimes, enabling configurable ports and access log visibility.
- Team access and billing are unified under a single Cloud organisation.
Getting Started
Sign up for Laravel Cloud, connect your repository, create a second application rooted at your frontend directory, and deploy it alongside your existing Laravel app. Refer to the official Next.js quickstart and Nuxt quickstart docs for full configuration options.
Source: Deploy Next.js and Nuxt apps on Laravel Cloud — Laravel Blog, July 28, 2026.
