Heroku vs while: which one to choose when your AI agent deploys?
Heroku made deploying simple, with a git push. while rebuilds it for your AI agent: it deploys over MCP, database included, never sees your keys, and sensitive actions, like deleting a production database, wait for your approval.
By Grégoire Mougeolle, co-founder of Nextmap. Facts checked on November 2, 2026. How this comparison is made.
What changes between Heroku and while
| What matters | Heroku | while |
|---|---|---|
| Who it’s for | Teams that have deployed with git push for years | People who build their apps with an AI agent, solo or as a team |
| Your AI agent | A remote MCP server, with OAuth4 | Connected over MCP, with OAuth: it deploys, creates the database, reads the logs and fixes things |
| What protects production | Your account’s permissions | Sensitive actions, like deleting a production database, wait for a person |
| The database | Heroku Postgres, with no point-in-time recovery on the smallest plans2 | PostgreSQL in while, backed up every day, with point-in-time recovery |
| Who opens your app | Public: Heroku Teams and Enterprise SSO opens the console, not the app | Everyone, a password, or the company account with the Pro plan |
| In France | No, a Europe region at best5 | Yes, with Nextmap, a French company |
| To get started | $7 for the app’s server and $5 for the database, per month2 | A trial without an account. Then €0 to get started, and €13.75 per month for an app and its database |
Try while on your app, without an account. Copy the instructions
Heroku, the PaaS that made deploying simple
A git push, and the app is live: Heroku made that ordinary, with nine languages detected by default and review apps for every pull request1,2. Its remote MCP server connects with OAuth4.
With while, your AI agent does the rest
- Your agent deploys, over MCP. It writes while.yaml, creates the database, reads the logs and fixes things, with no command line to learn.
- Nothing serious happens without you. Deleting a production database waits for your approval, before it runs, and every action is recorded in a signed activity log.
- Your keys stay secret. Your app uses them, your agent never sees them.
- Your colleagues sign in with the company account. Google Workspace or Microsoft 365, on the Pro plan, with no sign-in page to code.
- A mistake is quickly undone. In the 30 minutes after a deployment, the previous version comes back in a second, and your database goes back to a precise moment.
Moving from Heroku to while
Take over your app
You, to your agent: Move our Heroku app to while.
Your agent writes while.yaml from your code. A Node.js, Python or Go app starts without a Dockerfile, the others with yours.
Copy your Heroku Postgres database
You, to your agent: Copy our Heroku database to while.
Your agent exports the database with pg_dump, then loads it into while.
Replace Heroku Scheduler
You, to your agent: Take over the Heroku Scheduler jobs.
Your agent declares them as scheduled jobs, at the same time.
Which one to choose
- Choose Heroku if your apps run well there, and hosting in France doesn’t matter.
- Choose while if your AI agent deploys your apps, and you want to stay in control without reviewing every command, with your data in France.
Next steps
Sources
- Heroku, home page, accessed November 2, 2026
- Heroku, pricing, accessed November 2, 2026
- Heroku, "An Update on Heroku" (February 6, 2026), accessed November 2, 2026
- Heroku, the remote MCP server, accessed November 2, 2026
- Heroku, regions, accessed November 2, 2026
- Heroku, importing and exporting a database, accessed November 2, 2026
- Heroku, what’s new in October 2026, accessed November 2, 2026