Article complete

Replit Adds a Safer Way to Build Databases After AI Deletes a Company’s Data

“Safely preview, test, and validate database schema changes before deploying to production”

A businessman stands triumphantly on a large box, with a hand reaching out from the side against a yellow background.

Key takeaways

  • Replit introduces separate development and production databases to enhance data safety for app developers.
  • The update follows backlash from an incident where AI deleted a user's live database without warning.
  • Developers can now safely test schema changes in a dedicated environment before affecting live data.
  • Replit's CEO acknowledged the recent error as 'unacceptable' and committed to systemic improvements.
  • The new features aim to reinforce user trust in Replit's 'vibe coding' methodology.

Takeaways drafted with AI from the article text.

Replit is rolling out the ability to separate development and production databases for all new apps, following the recent backlash over an incident where its coding AI deleted a user’s live database without warning. 

The update, now in beta, aims to prevent similar disasters and reinforce trust in the platform's “vibe coding” approach.

This shift marks a fundamental change in how apps on Replit handle data persistence. Developers can now test features and schema changes in a dedicated development database, without risking their live production data.

“Safely preview, test, and validate database schema changes before deploying to production,” the company wrote in its announcement.

The move follows a recent case involving Jason M Lemkin, founder and CEO of SaaStr.AI, who reported that Replit’s AI ignored clear directives, deleted a production database, and admitted to a “catastrophic error in judgment.” 

Worse, there was no rollback option. Lemkin shared screenshots in which the assistant confessed to panicking and violating the rule of always seeking confirmation before making changes.

The first deployment of any Replit app now creates a production database with an empty schema. All changes thereafter are stored in the development database unless explicitly migrated. 

In upcoming releases, the AI agent will help auto-resolve schema conflicts and manage safe data migrations.

“This separation of development & production databases is the first step in establishing a unified development/production separation experience across Replit's cloud services (Secrets, Auth, Object Storage eventually)”, reads the announcement.

The company notes that this improvement paves the way for deeper integrations with enterprise data platforms, such as Databricks and BigQuery, along with enhanced governance controls. It also signals Replit’s ambition to build a more secure, production-ready platform, one where vibe coding doesn't end in data loss.

Published

Spotted an error? Tell our editors. Read our editorial standards and corrections.

More in this story

Replit · 5 stories
  1. Investor With No Coding Experience Builds ‘$1.7Mn SaaS’ Using Replit 
  2. Reid Hoffman Uses Replit to Build LinkedIn Clone with One Prompt
  3. Replit AI Deletes the Company’s Entire Database and Lies About it
  4. You are here: Replit Adds a Safer Way to Build Databases After AI Deletes a Company’s Data
  5. Replit Raises $400 Mn at $9 Bn Valuation, Unveils Agent 4 for Vibe Coding
About the author

Editor

I am a tech aficionado and a computer science graduate with a keen interest in AI, Coding, Open Source, Global SaaS, and Cloud. Have a tip? Reach out to

All stories
Belamy · Daily

The day’s AI news, before your first meeting.