Deploy a Django app and its PostgreSQL database with your AI, over MCP (2026)
Your AI knows Django inside out. Connected to while over MCP, it also deploys your app, with its PostgreSQL database backed up every day, in France, with no Dockerfile or server to manage.
By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 19, 2026.
The short version. Over MCP, your AI deploys your Django app and its PostgreSQL database with while, a French PaaS, with no Dockerfile or server to manage. What matters, like deleting a database, waits for a person’s approval.
Prerequisites
- A Django app, with a requirements.txt file.
- 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:
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:
apiVersion: while/v1
project: mon-appli
services:
- name: web
port: 8000
databases:
- name: main
Then it adds gunicorn and WhiteNoise to requirements.txt, a /health route that returns 200, and a Procfile that applies the migrations before each start:
web: python manage.py migrate --noinput && python manage.py collectstatic --noinput && gunicorn monsite.wsgi --bind 0.0.0.0:$PORT
It sets up settings.py for production, following Django’s deployment checklist1: DEBUG turned off, the secret key and ALLOWED_HOSTS read from the environment, the database read from DATABASE_URL, your app’s address in CSRF_TRUSTED_ORIGINS, and your static files served by WhiteNoise. Your app is installed, your pytest tests run, and then it starts.

Set up Django behind PgBouncer
You, to your AI: Check that Django works properly behind PgBouncer.
DATABASE_URL goes through PgBouncer in transaction mode. Your AI turns off server-side cursors, as Django recommends2:
DATABASES["default"]["DISABLE_SERVER_SIDE_CURSORS"] = True
Run a management command every night
You, to your AI: Run the clearsessions command every night at 3 am.
Your AI declares a scheduled job that runs python manage.py clearsessions at that time, with the same code and the same database. If it fails, your AI is notified.
Query your database from your AI
You, to your AI: How many people signed up this week?
Your AI reads your database in SQL through while’s MCP server, with your permissions on the data, and it can’t write to it.
Restrict your app to your colleagues
You, to your AI: Restrict the app to people in the company.
Your AI makes the service internal:
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.
Move to your own domain
You, to your AI: Put the app 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, and then your AI puts it into production.
Fix a vulnerability in your dependencies
You, to your AI: Fix the vulnerabilities in our dependencies.
Your app’s dependencies are checked against known vulnerabilities at every deployment, then every day. Your AI is warned of a serious vulnerability, and it updates the package involved.
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.
In the docs: PostgreSQL databases, Scheduled jobs, Internal access, Custom domain, Previews and Versions and rollback.
Next steps
Sources
- Django, the deployment checklist, accessed November 2, 2026
- Django, server-side cursors behind transaction pooling, accessed November 2, 2026