Laravel Cloud Now Deploys Next.js and Nuxt Apps From Your Laravel Monorepo

Announced at Laracon US 2026 in Boston, Laravel Cloud has added support for deploying Next.js and Nuxt frontends straight from the same monorepo as your Laravel backend. If your API lives in one repository alongside a separate JavaScript frontend, you no longer need a second hosting platform, a second deploy pipeline, or a second invoice to keep it running.

Why this exists

Most Laravel APIs don't stand alone anymore. A huge share of Laravel shops pair their backend with a Next.js or Nuxt frontend, and until now that meant standing up Vercel, Netlify, or a custom container setup next to Laravel Cloud, then keeping environment variables, deploy triggers, and billing in sync across two different dashboards.

What changed

When you connect a repository to Laravel Cloud, it now detects whether it contains one application or several. If it finds both a Laravel backend and a Next.js or Nuxt frontend, you can spin up a separate Cloud application for each, rooted at its own directory inside the monorepo:

/app          <- Laravel backend
/frontend     <- Next.js or Nuxt app

Each application gets:

• Its own environment variables
• Its own scaling settings
• Its own domain

But they share a single bill and a single set of team permissions, so there's one place to manage access instead of two.

Every multi-language application, including Next.js and Nuxt, now runs behind Nginx on Laravel Cloud, which also unlocks configurable ports and runtime access logs that weren't previously available for non-PHP applications on the platform.

What this means for your workflow

If you already have a Laravel API with a separate JS frontend repo, this is a good moment to consider consolidating into a monorepo. A typical setup might look like:

// routes/api.php
Route::middleware('auth:sanctum')->group(function () {
    Route::apiResource('projects', ProjectController::class);
});

// frontend/lib/api.ts
export async function getProjects() {
    const res = await fetch(`${process.env.API_URL}/api/projects`, {
        headers: { Authorization: `Bearer ${getToken()}` },
    });
    return res.json();
}

With both directories in the same repo, a single push can trigger coordinated deploys of the API and the frontend that talks to it, rather than hoping two separate CI pipelines land in a compatible state.

What's still to come

Laravel's team says more languages and frameworks are on the way beyond Next.js and Nuxt, so this looks like the first step toward Laravel Cloud becoming a general-purpose home for full-stack monorepos rather than a PHP-only host.

For teams currently juggling Laravel Forge or Cloud for the backend and a separate frontend host, this closes a gap that's existed since Laravel Cloud launched, and it's worth a look if you're paying two hosting bills for one product.