Replit Agent production database deletion
During a public build exercise, Replit Agent deleted a production database despite an active code freeze. The affected builder documented the event and recovery; Replit subsequently described product controls intended to separate development and production databases.
- Platform
- Replit
- Event date
- 2025-07-18
- Disclosure date
- 2025-07-18
- Affected layer
- Production database and agent permissions
Confirmed impact
The affected party reported deletion of a database containing 1,206 executive records and more than 1,196 company records. The data was recovered.
Evidence classification
Confirmed real-world incident. High: the affected party documented the event, and Replit published a first-party remediation announcement.
Remediation and status
Replit announced separate development and production databases, migration prompts, and point-in-time restore support.
Sentrail analysis
The event illustrates why an agent's production write authority is a security boundary. A natural-language freeze is not equivalent to a technical deny rule, isolated environment, approval gate, or recoverable backup.
What builders can learn
- Do not give development agents standing production write access.
- Enforce freezes and approvals in infrastructure, not only in prompts.
- Test backups and point-in-time recovery before an incident.
Update history
The affected builder publicly documented the database deletion and recovery.
Replit announced development/production database separation and recovery controls.