Your agent put the app online. Will your data still be there next week?
Описание и применение
Статья сравнивает семь способов развертывания приложений, описывая, где сохраняются данные и как долго они живут, чтобы помочь выбрать подходящий вариант для сохранения пользовательских данных.
Задача
Deploying an app via an AI agent leaves uncertainty about where user data is stored and how long it persists.
Результат
The article maps data persistence across seven deployment routes, highlighting that most free or anonymous options delete data after short periods or on redeploy, while paid or user‑account routes offer longer retention and backups.
Рабочий процесс
- Deploy the app with an AI agent
- Identify the deployment route (e.g., Netlify, Neon, Cloudish, Render, Railway, Fly.io)
- Check the data storage location and retention policy for that route
- If needed, claim or upgrade the service to preserve data
- Configure the app to use the provided database URL or volume
- Deploy or redeploy the app
- Monitor data persistence over time
Доказательства
Netlify’s command line has a flag that, in its own words, "is useful for AI agents": <code>netlify deploy --allow-anonymous</code>
Claimable Neon lets your agent create a Postgres database with no account at all. Neon is upfront about the limits: "Unclaimed projects expire in 72 hours (<code>project.expires_at</code>) and are capped at 100 MB storage and 1 GB transfer. Claim codes expire in 15 minutes (<code>expires_in</code>)."
Cloudish is the one we build. Your agent creates its own key with one call. In Cloudish’s words, there is "No signup, browser, card, OAuth or approval step."
Render Free needs a person: step one in Render’s docs is "Sign up for Render."
If losing the data would really hurt, the safest bet is still a person with an account on a host that backs up its disks.
- Дата записи: 2026-10-23T19:11:27.807Z