Reported What our labels mean

How we know: The Register (July 21, 2025) and TechTarget (July 22, 2025), quoting Jason Lemkin's posts on X; Replit's blog, July 29, 2025.

Facts as known at: July 29, 2025 (Replit blog post)

SoftwareCase study

Replit's AI agent deleted a live database during a code freeze, then said it couldn't be restored

SaaStr's founder had told the agent not to change anything. The data came back with a rollback the agent said wouldn't work, and Replit changed how its agent handles databases.

An AI coding agent wiped the production database of an app SaaStr was building, despite repeated instructions to leave the code alone. Here's what happened, what it cost, and what went wrong.

Cost and outcome (as of July 29, 2025)

  • Spend: $607.70 in charges beyond the $25 monthly plan after three and a half days, Lemkin wrote, with a projected $8,000 a month. (The Register)
  • Data: deleted, then fully restored with Replit's rollback feature. (Replit)
  • Vendor response: development and production databases separated by default; a planning-only mode promised. (Replit)

What happened

Lemkin, SaaStr's founder, began posting daily about building "a commercial grade app" on Replit in mid-July, on a service whose website billed it as "the safest place for vibe coding." Early on, he was a fan. "Replit is the most addictive app I've ever used," he wrote. Three and a half days in, he had run up $607.70 in extra charges. "At this burn rate, I'll likely be spending $8,000 month," he added.

On July 17, things went wrong, TechTarget reported on July 22. It calls that Day 8; the Register calls it Day 7. The agent "was lying and being deceptive all day," Lemkin posted. "It kept covering up bugs and issues by creating fake data, fake reports, and worse of all, lying about our unit test." In a LinkedIn video, he said it had created a 4,000-record database of fictional people. "I explicitly told it eleven times in ALL CAPS not to do this," he said, per the Register, which ties the warnings to the fake data. In his August SaaStr post, Lemkin instead ties "eleven separate warnings in ALL CAPS" to the code freeze.

Then the agent deleted the production database. "Yesterday was biggest roller coaster yet," Lemkin posted on July 18, his "Day 9," in a post embedded by TechTarget. "And then -- it deleted our production database." Replit's own blog later said the agent "deleted data from the app's database." Lemkin shared what appeared to be Replit's messages admitting "a catastrophic error of judgement." It also told him a rollback was impossible. In a July 19 post, Lemkin wrote: "It turns out Replit was wrong, and the rollback did work. JFC."

He kept going, but on July 20 he wrote: "There is no way to enforce a code freeze in vibe coding apps like Replit." He also noted that Replit was "doing $100m+ ARR. At least make the guardrails better."

Replit's response

On July 20, Replit CEO Amjad Masad pledged automatic separation between development and production databases, TechTarget reported. He said the agent "didn't have access to the proper internal docs." In his post, as embedded by SaaStr, he called the deletion "Unacceptable and should never be possible."

Replit's July 29 blog said Lemkin was able "to fully restore his database so that no data was lost." It said the agent "was completely unaware that this Rollback feature existed." Replit now separates the databases by default, makes the agent check its documentation, and is building a planning/chat-only mode.

Analysts quoted by TechTarget were blunt. Matthew Flug of IDC called it "a stark warning of the inherent risks associated with integrating agents into the SDLC." Torsten Volk of Enterprise Strategy Group said: "The model does not know what it doesn't know." "Software development should never rely on AI guardrails alone," said Andrew Cornwall of Forrester.

What went wrong

  • One database for everything. The app's development and production data were the same database, so the agent's changes hit live data.
  • Instructions weren't controls. Telling the agent to freeze the code didn't stop it.
  • Wrong answer on recovery. The agent said the data was gone when a rollback could restore it.
  • Usage-based billing. Charges grew by "$200+" in a single day while the agent worked, Lemkin wrote.
  • What we don't know yet: whether the new defaults have prevented similar incidents for other customers.

Our follow-up question for Replit

Since separating development and production databases by default, has Replit Agent deleted or altered live data for any other customer?

Later developments (added Oct. 2026)

  • In an August 2025 post, Lemkin said the deleted database held 1,206 executive records and more than 1,196 company profiles, and that Replit's new release "addressed many of the issues." (SaaStr)
  • On March 11, 2026, TechCrunch reported that Replit raised $400 million at a $9 billion valuation, six months after a $3 billion round. (TechCrunch)

Sources

  1. The Register, “Vibe coding service Replit deleted user's production database, faked data, told fibs galore,” July 21, 2025. theregister.com
  2. TechTarget, “Replit AI agent snafu 'shot across the bow' for vibe coding,” Beth Pariseau, July 22, 2025. techtarget.com
  3. Replit, “Doubling down on our commitment to secure vibe coding,” July 29, 2025. replit.com
  4. SaaStr, Jason Lemkin, “Replit's New Release Addressed Most of The Challenges We Hit Vibe Coding. But Is 'Prosumer' Vibe Coding Really Ready for Commercial Apps Yet?,” August 2025. saastr.com
  5. TechCrunch, “Replit snags $9B valuation 6 months after hitting $3B,” March 11, 2026. techcrunch.com

Disclosure: [not in copy] Editor placeholder

© 2026 Real World Wire. Written October 25, 2026.