AWS Amplify vs while: which one to choose when your AI agent deploys?
AWS Amplify deploys your sites and Next.js apps on every push, on AWS’s CDN. With while, your AI agent deploys the app, its PostgreSQL database and its access settings, in France, 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 AWS Amplify and while
| What matters | AWS Amplify | while |
|---|---|---|
| Who it’s for | Sites and Next.js or Nuxt apps, on AWS’s CDN1 | People who build their apps with an AI agent, solo or as a team |
| Your AI agent | AWS’s general MCP server, which calls the whole API within your IAM permissions2 | Connected over MCP, with OAuth: it deploys, creates the database, reads the logs and fixes things |
| What protects production | Your agent’s AWS permissions, an optional read-only mode, and your approval in your AI tool8 | Sensitive actions, like deleting a production database, wait for a person |
| The database | No managed PostgreSQL: Amplify connects to an existing PostgreSQL database3 | PostgreSQL in while, backed up every day, with point-in-time recovery |
| Who opens your app | A username and a password per branch, with no code4 | Everyone, a password, or the company account with the Pro plan |
| In France | Yes, one region in France5 | Yes, with Nextmap, a French company |
| To get started | Free up to a cap, for 12 months at most, then pay-as-you-go6 | 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
Amplify, your sites on AWS’s CDN
Amplify deploys your site or your Next.js app on every push, with a preview for each pull request and no downtime during the update, and serves it from more than 600 locations around the world1,7. You can protect a branch with a password without a line of code4.
With while, your AI agent does the rest
- No server to maintain. No system to update, no disk to watch, no certificate to renew: your agent deploys, and the rest is taken care of.
- Your databases are backed up for you. Every day, with point-in-time recovery, and a production backup tested every day.
- 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.
Moving from AWS Amplify to while
Take over your app
You, to your agent: Move our Amplify app to while.
Your agent takes over your code, writes while.yaml and deploys the app.
Copy your database
You, to your agent: Copy our 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 AWS Amplify if your team already lives in AWS, and your app is a site or a Next.js app served all around the world.
- Choose while if your app, its API and its database must run in the same place, in France, deployed by your AI agent without breaking anything.
Next steps
Sources
- AWS Amplify Hosting, overview, accessed November 2, 2026
- AWS, the AWS MCP server is generally available, accessed November 2, 2026
- Amplify, connecting to an existing PostgreSQL or MySQL database, accessed November 2, 2026
- Amplify Hosting, password-protecting a branch, accessed November 2, 2026
- AWS Amplify, regions, accessed November 2, 2026
- AWS Amplify, pricing, accessed November 2, 2026
- AWS Amplify Hosting, product page, accessed November 2, 2026
- AWS, the Agent Toolkit (permissions, read-only), accessed November 2, 2026