We know your Laravel API rarely stands alone. Most teams pair it with a customer-facing frontend, dashboard, storefront, or onboarding flow built in Next.js or Nuxt, all pointed at the same API. Now you can deploy your frontend alongside your Laravel backend, on the same platform, with the same bill.
Until now, your frontend may have lived elsewhere, on a separate hosting account with its own deployment pipeline, environment variables, and bill. Every release meant coordinating two deploys, watching two dashboards, and debugging environment mismatches between the API URL your frontend expects and the one your backend actually exposes.
With Next and Nuxt deployments on Laravel Cloud, you push once, and both the frontend and the backend build, deploy, and scale from the same repository.
Read the Next.js and Nuxt deployment docs to get started.
How Next.js and Nuxt Deployments Work on Laravel Cloud
Next and Nuxt deployments run on the same mechanism as Laravel Cloud's new monorepo support. When you create a new application, Cloud analyzes your repository and determines whether it contains a single application or multiple applications. If it finds more than one, such as a Laravel backend and a Next.js or Nuxt frontend, it shows you the top-level directories and lets you pick which one the application should deploy from.
For a repository with both a backend and a frontend, you create a separate Cloud application for each one, attach the same repository to both, and select a different root directory during setup for each. Every directory in the repository remains available during the build, so your frontend can still reference shared packages or sibling folders if needed, even though only its own directory is deployed.
Framework-Aware Deployments
Each application you create is a fully independent Cloud resource: its own environment variables, instances, scaling settings, domains, and attached services, even though the two share a single repository. Because Cloud is framework-aware, it exposes different configuration options based on each application's runtime, so your Next.js or Nuxt app is configured differently from your Laravel backend without you having to do that work by hand.
That independence is also what makes the model fit a frontend and a backend well in practice. They tend to have different traffic patterns, so deploying them as separate applications means you can size and scale each one on its own terms instead of treating the whole repository as a single unit.
What Changed Under the Hood
Multi-language deployments needed more than a framework detector, so we shipped the infrastructure to support them.
Every multi-language application, including Next.js and Nuxt, now runs behind Nginx, the same web server Cloud already uses for PHP. That standardization makes two other changes possible: ports are configurable rather than hardcoded to a framework default, and runtime access logs are now visible in the dashboard, where there was previously no request-level visibility into a non-PHP application at all.
JavaScript build times are faster, too. When you create a new application, Cloud now lists Next.js and Nuxt alongside Laravel and Symfony in the framework picker, so you know upfront what you can deploy before you connect a repository.
One Platform and One Bill for Your Whole Stack
Now you can bring your stack back together. Teams can deploy their Next and Nuxt frontends on every plan at no additional cost. Instead of stitching together two sets of infrastructure decisions, you can deploy your frontend application and backend application from the same Cloud organization. Teams get one bill for everything, and one location from which to manage who has Admin or Developer rights to every application in the organization.
That matters most for the people managing access, not just the people writing code. An engineering lead who previously granted two separate sets of team access, one for the frontend host and one for the Cloud organization, now grants one.
A team running a dozen client sites on a single VPS, each with its own Next.js or Nuxt frontend, can consolidate every one of those frontends under the same account instead of paying a separate per-seat bill on another platform for each client.
For a founder shipping solo, that means no second infrastructure stack to learn just to put a frontend in front of the API. For a team that has run Laravel Cloud for years, it means modernizing the frontend without leaving the platform they already trust.
Deploy Your Whole Application from Laravel Cloud
You already trust Laravel Cloud to run your backend. Now you can run the full application experience, from backend to frontend, all from the Laravel ecosystem you already trust. Unify your existing Next and Nuxt frontends on the same cloud platform to benefit from one home for applications, one deploy workflow, and one unified bill.
When you are ready to try it, sign up for Cloud, connect your repository, create a second application rooted at your frontend directory, and deploy it alongside the Laravel app you already have running there. Read the Next.js and Nuxt framework docs for the full configuration options, or start with the quickstart if this is your first Cloud application.