Scalingo vs while: which one to choose when your AI agent deploys?
Scalingo and while both host your apps in France. Scalingo stands out on compliance. while stands out on what your AI agent can do: it deploys over MCP, 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 Scalingo and while
| What matters | Scalingo | while |
|---|---|---|
| Who it’s for | Teams with strong security and compliance requirements1 | People who build their apps with an AI agent, solo or as a team |
| Your AI agent | No official MCP server: your agent goes through the command line | Connected over MCP, with OAuth: it deploys, creates the database, reads the logs and fixes things |
| What protects production | Team roles, including a collaborator with limited permissions | Sensitive actions, like deleting a production database, wait for a person |
| The database | Managed PostgreSQL, backed up every day, with point-in-time recovery over 7 to 30 days3 | PostgreSQL in while, backed up every day, with point-in-time recovery |
| Who opens your app | IP address filtering, in preview and on request | Everyone, a password, or the company account with the Pro plan |
| In France | Yes4 | Yes, with Nextmap, a French company |
| To get started | €7.20 for the container and €7.20 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
Scalingo, a French PaaS built for compliance
Scalingo deploys your code with git push, without a Dockerfile, in nine languages, and runs it in France7,4. It is ISO 27001 certified, offers health data hosting, and responds to critical incidents in under 15 minutes on average1.
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 Scalingo to while
Take over your app
You, to your agent: Move our Scalingo app to while.
Your agent writes while.yaml from your code. A Node.js, Python or Go app starts without a Dockerfile, just as on Scalingo.
Copy your PostgreSQL database
You, to your agent: Copy our PostgreSQL database to while.
Your agent exports the database with pg_dump, then loads it into while.
Carry over your variables
You, to your agent: Carry over our environment variables.
Your agent carries your settings over to while. You enter your secret keys yourself: it never sees them.
Which one to choose
- Choose Scalingo if you host health data, or if you need SecNumCloud-qualified infrastructure, on request.
- Choose while if your AI agent deploys your apps, and you want to stay in control without reviewing every command.
Next steps
Sources
- Scalingo, home page (compliance, support), accessed November 2, 2026
- Scalingo, pricing, accessed November 2, 2026
- Scalingo, database backups, accessed November 2, 2026
- Scalingo, regions, accessed November 2, 2026
- Scalingo, creating an account (email or GitHub), accessed November 2, 2026
- Scalingo for AI, accessed November 2, 2026
- Scalingo, the PaaS (git push, buildpacks), accessed November 2, 2026