---
title: "Deploy Astro with server rendering and your AI in 2026"
url: https://while.sh/en/guides/deploy-astro-ssr/
author: "Aloïs Oddon, co-founder of Nextmap"
updated: 2026-11-19
---

# Deploy an Astro site with server rendering with your AI, over MCP (2026)

Your Astro site renders some pages on demand. Connected to while over MCP, your AI deploys it in France with the Node adapter, without a Dockerfile, and you choose who can open it.

> **The short version.** Over MCP, your AI deploys your server-rendered Astro site with while, in France, with the Node adapter. No Dockerfile, no server to manage. What matters, like deleting a database, waits for a person's approval.

## Prerequisites

- An Astro site that renders pages on demand: 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 site'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 site 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 site

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

## What your AI does

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

```yaml titre="while.yaml"
apiVersion: while/v1
project: mon-site
services:
  - name: web
    port: 4321
    health:
      path: /
    env:
      HOST: 0.0.0.0
```

Your site is built, then started by Astro's standalone server, which reads `HOST` and the port it receives in `PORT` (source 1). Your AI also checks that the `start` script in your package.json runs `node ./dist/server/entry.mjs`, and not the development server.


<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 an Astro site with server rendering 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 your site to your colleagues

> You, to your AI: Restrict the site 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 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 site to our customer, with a password.

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

## Move to your own domain

> You, to your AI: Put the site on app.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 static site](/en/guides/deploy-static-site/)
- [Deploy a SvelteKit app](/en/guides/deploy-sveltekit/)
- [Put your app on your own domain](/en/guides/custom-domain/)

## Sources

1. [Astro, the Node adapter (standalone mode, HOST and PORT)](https://docs.astro.build/en/guides/integrations-guide/node/), 2026-11-02

## Questions

### Do I need to write a Dockerfile?

No. Astro with its Node adapter is recognized, built and started by its standalone server.

### What about a fully static Astro site?

It deploys like a static site: its dist folder is served with an HTTP cache.

### Where is my site 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.
