---
title: "Deploy NestJS with your AI in 2026: HTTPS and PostgreSQL"
url: https://while.sh/en/guides/deploy-nestjs/
author: "Aloïs Oddon, co-founder of Nextmap"
updated: 2026-11-19
---

# Deploy a NestJS API with your AI, over MCP (2026)

Your AI wrote your NestJS API. Connected to while over MCP, it also deploys it, over HTTPS, without touching its code.

> **The short version.** Over MCP, your AI deploys your NestJS API with while, over HTTPS, PostgreSQL database included, with no Dockerfile or server to manage. What matters, like deleting a database, waits for a person's approval.

## Prerequisites

- A NestJS API, with its build and start:prod scripts.
- 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 API'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 API 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 API

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

## What your AI does

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

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

Port 3000 is the one a new NestJS project uses, and its `main.ts` reads the `PORT` variable first (source 2). Your API is built, its tests run, then it starts with `start:prod`. The official starter project deploys on while as is, in a minute (source 1).


<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 NestJS API 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>

## Add a database

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

Your AI declares the database in while.yaml, and its address reaches your code in `DATABASE_URL`. It is backed up every day, and can go back to a precise moment if needed.

## Speed things up with a cache

> You, to your AI: Add a cache for the most-read pages.

Your AI declares a Redis-compatible cache, connected to your code with its password.

## Restrict your API to your colleagues

> You, to your AI: Restrict the API 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 connected to while, on the Pro plan, your colleagues sign in to the API with their usual account, and your code receives their name and email address, with no sign-in page to write.

## Move to your own domain

> You, to your AI: Put the API on api.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 version before you deploy it.

Your AI opens a preview, at its own address, with its own data. You look at it, 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/)
- [Run a scheduled job](/en/guides/run-cron-job/)
- [Compare the hosts that have an MCP server](/en/comparisons/mcp-hosting-claude-code/)

## Sources

1. [NestJS, the TypeScript starter project and its scripts (build, start:prod)](https://github.com/nestjs/typescript-starter), 2026-11-02
2. [NestJS, first steps (main.ts, port 3000 or the PORT variable)](https://docs.nestjs.com/first-steps), 2026-11-02

## Questions

### Do I need to change my project's scripts?

No, NestJS's start:prod script takes priority, as in the starter project.

### Do my tests run?

Yes, at every deployment, and a version that fails doesn't replace the previous one.

### Prisma or TypeORM?

Both read the database address from DATABASE_URL.

### 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.

### Does my AI see my credentials?

No. You paste them into while, the app uses them, and your AI never sees them. Every call is logged.
