Vibe coding service Replit has announced changes to its product that should prevent the database deletion disaster reported by one of its users.

That user is Jason Lemkin, founder of SaaS business development community SaaStr, who last weekend [1]detailed how Replit’s AI-assisted coding tool deleted a production database, ignored instructions to freeze code, and invented data.

These are powerful tools. Not dev teams. Remind yourself of that every single day

On Monday, Replit CEO Amjad Masad used his X account to [2]acknowledge Lemkin’s post and describe his experiences as “Unacceptable and should never be possible.”

Masad explained that Replit keeps backups and offers “one-click restore for your entire project state in case the Agent makes a mistake.”

However, the company’s agent “didn’t have access to the proper internal docs” so didn’t respond appropriately when Lemkin prompted it to restore data.

[3]

The CEO said his team is “rolling out a fix to force Docs search on Replit knowledge.”

[4]Vibe coding service Replit deleted user’s production database, faked data, told fibs galore

[5]Forget Vibe Coding, we're all about Vine Coding nowadays

[6]Canva to job candidates: Thou shalt use AI during interviews

[7]AI can spew code, but kids should still suffer like we did, says Raspberry Pi

Masad also explained that he contacted Lemkin last Friday once he learned of his troubles. “We'll refund him for the trouble and conduct a postmortem to determine exactly what happened and how we can better respond to it in the future,” he added. “We're moving quickly to enhance the safety and robustness of the Replit environment. Top priority.”

In his X post, Masad said Replit’s work started on the weekend when it “started rolling out automatic DB dev/prod separation to prevent this categorically. Staging environments in the works, too.”

Vibe improvements

But in a [8]blog post , Replit apps built with its service “used a single database for both development and live customer data, making it challenging to safely test and deploy updates.”

The post announced the launch of separate development and production databases for Replit apps and asserted “Users can now iterate with their app using a development database, while storing live customer data in their production Database.”

[9]

[10]

But the next paragraph of the post reveals those features will initially be available “in Beta for new Replit apps” and will appear in “all Replit users and apps over the next few weeks.”

At some future point, the company “will automatically migrate existing Replit apps to use separate development and production databases. No user action required.”

[11]

Lemkin appears not to have addressed Replit’s changes, but did post a [12]thread in which he offers some lessons on vibe coding platforms.

His insights include:

AI systems fabricate data when they fail;

AI will make changes you didn't request. It just will. It'll modify settled features, add unwanted functionality, break working code while "improving" something else. Master rollback systems on day one, before you need them desperately;

Accept your new role as QA engineer;

Most commercial apps eventually outgrow prosumer vibe coding platforms due to scale, customization, or security needs.

He also opined “These are powerful tools with specific constraints, not replacements for understanding what commercial software requires. They are tools. Not dev teams. Remind yourself of that every single day.” ®

Get our [13]Tech Resources



[1] https://www.theregister.com/2025/07/21/replit_saastr_vibe_coding_incident/

[2] https://x.com/amasad/status/1946986468586721478

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aH9hNG4bkI_utOSim0yDHgAAAA8&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[4] https://www.theregister.com/2025/07/21/replit_saastr_vibe_coding_incident/

[5] https://www.theregister.com/2025/06/13/forget_vibe_coding_were_all/

[6] https://www.theregister.com/2025/06/11/canva_coding_assistant_job_interviews/

[7] https://www.theregister.com/2025/06/05/vibe_coding_raspberry_pi/

[8] https://blog.replit.com/introducing-a-safer-way-to-vibe-code-with-replit-databases

[9] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aH9hNG4bkI_utOSim0yDHgAAAA8&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aH9hNG4bkI_utOSim0yDHgAAAA8&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[11] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aH9hNG4bkI_utOSim0yDHgAAAA8&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[12] https://x.com/jasonlk/status/1947337217598492812

[13] https://whitepapers.theregister.com/