Leave Heroku without rewriting your app, with your AI (2026)
Is your Heroku bill climbing? Connected to while over MCP, your AI takes your app as it is, copies your database, and deploys it in France.
By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 19, 2026.
The short version. Over MCP, your AI takes over your Heroku app, copies the database and carries over your variables. Heroku’s Node.js example ran unchanged. What matters, like deleting a database, waits for a person’s approval.
Prerequisites
- An app on Heroku, in Node.js, Python or Go.
- Access to your Heroku account, to export the database.
- 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: 5006
health:
path: /
Heroku’s Node.js example ran on while without a single line changed2.

Copy your Heroku Postgres database
You, to your AI: Copy our Heroku database to while.
Your AI exports the database with pg_dump, then loads it into while.
Carry over your variables
You, to your AI: Carry over our Heroku config vars.
Your AI carries your settings over to while. You enter your secret keys yourself: your AI never sees them.
Replace Heroku Scheduler
You, to your AI: Bring over the Heroku Scheduler jobs.
Your AI declares them as scheduled jobs, at the same times.
Move to your own domain
You, to your AI: Put the app on www.acme.com.
Your AI declares the domain, 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.
In the docs: Scheduled jobs, Custom domain, Versions and rollback and Variables and secrets.
Next steps
Sources
- Heroku Dev Center, runtime principles (the port given by PORT), accessed November 1, 2026
- Heroku on GitHub, the Node.js example with Express (node-js-getting-started), accessed November 1, 2026
- Heroku Dev Center, config vars, accessed November 1, 2026