---
title: "Deploy Next.js with your AI in 2026: without Vercel, in France"
url: https://while.sh/en/guides/deploy-nextjs/
author: "Aloïs Oddon, co-founder of Nextmap"
updated: 2026-11-19
---

# Deploy a Next.js app with your AI, over MCP (2026)

Your AI wrote your Next.js app. Connected to while over MCP, it also deploys it, over HTTPS, and you choose who can open it: everyone, your customers or your colleagues.

> **The short version.** Over MCP, your AI deploys your Next.js app with while, over HTTPS, open to everyone or to your colleagues, with no Dockerfile or server to manage. What matters, like deleting a database, waits for a person's approval.

## Prerequisites

- A Next.js app.
- An AI that works in a terminal: Claude Code, Codex, Cursor or Gemini CLI.

## Step 1: Give your AI this message

Open your AI in your app's folder, and paste this message into it:

```text titre="The message to give your AI"
Connect to while with my account (while.sh/agents), then put my app on while.
```

Without an account, your AI deploys your app as a trial, in one request. To keep it, open the link it gives you and create your account.

With your account, your AI adds while's MCP server itself. If it asks you to, restart it. On the first call to while, a page opens in your browser. In Claude Code, if it doesn't open, type /mcp, choose while, then Authenticate. On that page, choose your app, or "A new app", then click Authorize.

## Step 2: Open your app

Your AI gives you your app's address, for example `https://mon-appli.while.cloud`, over HTTPS.

## What your AI does

It writes while.yaml at the root of your app:

```yaml titre="while.yaml"
apiVersion: while/v1
project: mon-appli
services:
  - name: web
    port: 3000
    health:
      path: /
```

Port 3000 is the port of `next start`, which reads the `PORT` variable (source 1). Your app is built, its tests run, and then it starts. It only receives visitors once its home page is ready.


<figure class="illus"><img src="/illustrations/guide-cadre-production-1200.webp" srcset="/illustrations/guide-cadre-production-768.webp 768w, /illustrations/guide-cadre-production-1200.webp 1200w" sizes="(min-width: 48rem) 46rem, 100vw" width="1536" height="1024" loading="lazy" decoding="async" alt="What your AI does to put a Next.js app in production on while: the while.yaml file, the build and tests, the HTTPS address, the PostgreSQL database backed up every day and a person's approval, in France" /><figcaption>Your AI writes while.yaml, while builds and serves the app over HTTPS, and the previous version stays ready.</figcaption></figure>

## Restrict the app to your colleagues

> You, to your AI: Restrict the app to people in the company.

Your AI makes the service internal:

```yaml titre="while.yaml"
    access: internal
```

Then it asks for the Access role for your domain, @acme.com, on this app, and a person in your organization approves it.

Once your Google Workspace or Microsoft 365 is linked to while, on the Pro plan, your colleagues sign in with their usual account, and your app receives their name and email address, with no sign-in page to write.

## Share with a customer, protected by a password

> You, to your AI: Open the app to our customer, with a password.

Your AI makes the app private. Then, on the app's page in while, you create a link that lasts 1, 7 or 30 days, with a password your AI will never see.

## Add a database

> You, to your AI: Add a PostgreSQL database for bookings.

Your AI declares the database in while.yaml, and its address reaches your app in `DATABASE_URL`. It is backed up every day. The details are in the guide to the Node.js API and its PostgreSQL database.

## Put the app on your domain

> You, to your AI: Put the app on planning.acme.com.

Your AI declares the domain, you add the DNS records it gives you, and the HTTPS certificate follows.

## See a new version before you deploy it

> You, to your AI: Show me the new page before you deploy it.

Your AI opens a preview, at its own address, with its own data. You look at it, and then your AI puts it into production.

## Go back to the previous version

> You, to your AI: Go back to the previous version.

In the 30 minutes after a production release, the previous version comes back in a second. After that, it takes a few seconds. Once the previous version is back, your AI reads what broke in while's logs, fixes it and deploys again.

## Next steps

- [Deploy a Node.js API and its PostgreSQL database](/en/guides/deploy-node-api-postgresql/)
- [Restrict your app to people in your company](/en/guides/internal-tool-company-sign-in/)
- [Compare the hosts that have an MCP server](/en/comparisons/mcp-hosting-claude-code/)

## Sources

1. [Next.js, the next command and its options (next start, PORT)](https://nextjs.org/docs/app/api-reference/cli/next), 2026-11-01

## Questions

### Do I need to change my code to leave Vercel?

No. A Next.js app that starts with next start works as it is, and your AI carries over your environment variables.

### Do I need to write a Dockerfile?

No. Your Next.js app is detected as a Node app, built and started without a Dockerfile. If your project has one, it is used to build the image.

### Does my Next.js app receive the name of the signed-in person?

Yes. When it is restricted to your company, it receives the name and email address of the signed-in person, with no sign-in page to write.

### What if my app isn't built with Next.js?

Express, NestJS, Nuxt, Vite with React, an Astro site and a Go server deploy the same way.

### Where do my app and its data run?

In France, at Nextmap. The database is backed up every day, with a way back over 14 days, once a person approves.
