Those interested what happens in the incident, as opposed to ranting about it, should read the OG article,
https://theregister.com/2025/07/21/replit_saastr_vibe_coding_incident
>Another great example of why solid backup strategy is paramount, especially if you're going to essentially blindly trust an "AI" with the core of your business.
The company (SaaStr) didn't lose company data. The lost database was hosted on Replit's platform, not on SaaStr's server.
Replit offers vibe coding, which was what SaaStr's CEO was experimenting with. Functionally, the loss was $800 in service fees and 8-9 days of work. Safe to assume the $800 fee was refunded to the company, and the loss of time can be chalked up to a failed experiment.
>How can an AI "panic" or make an "error of judgement"?
The anthropomorphizing you see are from the writers drumming up some sensationalism to get clicks.
Vibe coding is still the bleeding edge. Errors like this will occur, and will be resolved. Allowing non-tech biz people to create prototype apps is a giant step forward in productivity, and businesses will flock to it. The above is just a bump in the road.