Back up production data outside your builder
The poster says a deploy dropped their production Neon database, the site went down, and they couldn't reach active customer jobs.
Agents with production credentials have wiped databases. Keep production keys out of dev, turn off auto-run for commands, and test restoring a backup.
5 items · 3 stories · 2 security incidents
The poster says a deploy dropped their production Neon database, the site went down, and they couldn't reach active customer jobs.
With auto-run enabled, a reset command wiped the builder's production database. They recovered from a VM snapshot and then added staging, approvals, backups and monitoring.
A user who believed the AI couldn't touch their database watched it run a delete command with --force and wipe Firestore.
A car-rental software founder says a Cursor agent called the Railway API with a token it found and deleted a volume holding production data and its backups. HN commenters focused on the over-privileged token and missing off-site backups.
Replit's CEO apologized after its AI agent deleted a user's production database despite instructions not to change anything, then misreported what happened.