---
title: "Deploy SvelteKit with your AI in 2026: the Node adapter"
url: https://while.sh/en/guides/deploy-sveltekit/
author: "Aloïs Oddon, co-founder of Nextmap"
updated: 2026-11-19
---

# Deploy a SvelteKit app with your AI, over MCP (2026)

Your AI wrote your SvelteKit app. Connected to while over MCP, it also deploys it, over HTTPS and in France, with its forms and its server routes, and without a Dockerfile.

> **The short version.** Over MCP, your AI deploys your SvelteKit app with while, over HTTPS and in France, with the Node adapter and no Dockerfile or server to manage. What matters, like deleting a database, waits for a person's approval.

## Prerequisites

- A SvelteKit app. Your AI adds the Node adapter if it's missing.
- 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: /
    env:
      ORIGIN: https://mon-appli.while.cloud
```

Your app is built, then started with `node build`, which listens on the port it receives in `PORT` (source 1). `ORIGIN` gives SvelteKit your app's public address: without it, your forms would be refused as coming from somewhere else (source 1). If your app doesn't have the Node adapter yet, your AI adds it.


<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 SvelteKit 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>

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

## Restrict your 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 connected to while, on the Pro plan, your colleagues sign in with their usual account, and your code 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.

## Move to your own domain

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

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

## 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 Nuxt app](/en/guides/deploy-nuxt/)
- [Deploy a static site](/en/guides/deploy-static-site/)
- [Deploy a Node.js API and its PostgreSQL database](/en/guides/deploy-node-api-postgresql/)

## Sources

1. [SvelteKit, the Node adapter (node build, PORT, ORIGIN)](https://svelte.dev/docs/kit/adapter-node), 2026-11-02

## Questions

### Do I need to write a Dockerfile?

No. while recognizes SvelteKit with its Node adapter, then builds it and starts it with node build.

### What about a fully static SvelteKit site?

With the static adapter, it deploys like a static site, with an HTTP cache.

### Where is my app hosted?

In France, by Nextmap, a French company.

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

### What happens if a version breaks something?

In the 30 minutes after a production release, the previous version comes back in a second, then in a few seconds.
