An AI agent wiped our production database in nine seconds. Bringing it back took us sixty hours. The story went further than we expected — across X, LinkedIn, Hacker News, podcast feeds, and the inboxes of just about every founder we know. The reporters who reached out wanted the same thing: a clean cautionary tale about AI gone wrong.
We owe our customers, our partners, and the operators who trust us with their fleets a real answer in our own voice. Not a hot take, not a defensive memo, and not a pretend-it-never-happened press release.
Yes, it happened. Yes, we recovered. And yes, we are still all in on AI for our rental operators. Here is the longer version of why.
What actually happened
We are a small startup. Three founders. There were no engineers paged in, because there are no engineers to page. When the database went down, it was the founder who handles engineering — alone, opening a laptop, working the problem, and personally calling and emailing customers to tell them what was going on.
The first thing we did was reach for our backups. The backups were there. They were also three months out of date. Our backup process had quietly stopped working a quarter earlier and we did not catch it. That is on us. What should have been the easy part of recovery turned out not to be available at all, and the next sixty hours became the hardest of our company's life — rebuilding our platform from every source of truth we could pull from, account by account, until our customers could log in again.
For those sixty hours, operators could not log in. Bookings did not flow normally. Dashboards were dark. Daily briefings did not send. The people who trust us to run their rental businesses sat with their phones in their hands waiting for us to bring the lights back on.
The viral version of the story compressed the timeline. The deletion took nine seconds. The recovery took sixty hours. Both numbers are true, and the second one matters more.
When we did finish, every customer was made whole. No bookings were lost. No accounts were lost. But the fact remains that for two and a half days, our customers could not run their businesses on our software, and a lot of them fell back to spreadsheets and phone calls to keep their fleets moving. We will not forget that, and we will not pretend it didn't happen.
Here is what we have changed. Destructive operations now require human-in-the-loop confirmation before they can run. Our recovery procedures have been completely restructured — an incident like this one is now measured in hours, not days. And our backups are now triple-redundant, fully offsite, and verified daily. The specific failure that bit us cannot bite us the same way again.
Why we are not backing away from AI
The easy move would be to throw the AI under the bus, announce a "return to manual processes," and quietly delete the word "AI" from our marketing. We are not going to do that. It would be dishonest, and it would be bad for our customers.
The AI did not act with malice. It can't — it is a computer. It is a machine. It acted with confidence on permissions it should never have had, against a system that did not have enough friction in the right places. We believe that is an engineering and safety-tooling problem, not an AI problem. And it is one we have now fixed.
Our customers are not asking us to slow down. They are asking us for more. They run operations on thin margins, with porter teams stretched and vehicles scattered across cities. AI is the difference between catching a fuel issue at 6:30 AM and discovering it at 11:00 AM after a guest complains.
Here is what we have built for them.
What we have shipped:
AI Cloud Agents
We call them AI Cloud Agents. They are narrow, scheduled, autonomous workers that run in the background for every organization on our platform. Eighteen of them are in production today. Each one does exactly one job, on a defined schedule, and the operator can pause, configure, or roll back any of them in a single click.
Daily Snapshot
At 6:30 AM, every rental operator on our platform wakes up to a Miles AI Daily Snapshot. Revenue from active rentals. Average revenue per vehicle. Total fleet miles ahead that day. Scheduled deliveries and pickups. Porter coverage needs. Fuel alerts. A clean bookings-by-source breakdown.
A real briefing from our system told a luxury operator one morning that they had three active rentals doing $3,410 in revenue, an impressive $1,137 per vehicle, 300 fleet miles ahead — and two vehicles sitting at 0% fuel that needed immediate attention. That fuel alert was not buried in a dashboard. It was the first thing they saw when they opened their phone.
That is what AI is good at. Not replacing the operator. Pulling the two facts that matter out of a sea of data and putting them in front of the person who can act on them.
At 8:15 AM, our TurboRank SEO customers get the same kind of briefing for their search performance — traffic, keyword movement, reviews, and content alerts.
AI-powered Turo Calendar Sync
Turo does not offer a calendar sync. They have made the deliberate choice not to let third-party software talk to their platform — no API, no calendar feed, no integration path. For an operator who lists on Turo and on their own direct channels, that is a real problem. A booking on Turo can quietly turn into a double-booking everywhere else if it is not caught in time.
What Turo does send is email. Booking confirmations, modifications, cancellations, trip extensions — every change lands in the operator's inbox.
So we built our Turo Calendar Sync around that. Our system understands the booking events flowing through those emails and updates the operator's availability across their other channels automatically. The hundreds of edge cases — partial dates, time zones, modifications layered on modifications, cancellations followed by rebookings — are handled by our AI behind the scenes, so the operator does not have to.
We want to be honest about the limitation. The sync is one-directional. Turo data flows into our platform, but our platform cannot push back into Turo, because Turo does not allow it. That is a constraint of the marketplace, not our software. Within that constraint, we have built the closest thing to a real calendar integration that exists for Turo hosts. For an operator running fifty vehicles across multiple channels, a single avoided double-booking can be worth more in a year than the cost of our entire platform.
Autonomous SEO
For operators on TurboRank SEO, we have built a family of agents that handle the unglamorous work of local search end to end. Reviews get on-brand AI responses. Blog content gets written and published twice a week. Opportunity alerts surface every morning. Behind the scenes, agents sync Google Business Profile reviews every fifteen minutes, Search Console and Analytics every six hours, and keyword rankings every morning at 5 AM.
The piece we are proudest of is the autonomous task loop. Our agents take the alert signals, turn them into queued work, do the work, verify it shipped correctly, and measure the impact the next morning. The operator never has to log into a single Google dashboard.
What comes next
We are going to keep building. We are going to keep telling these stories honestly. And we are going to keep our customers in control — every AI Cloud Agent on our platform can be paused, configured, or rolled back by the operator without picking up the phone.
To our customers: thank you for not flinching. To the operators who emailed us through those sixty hours with patience and even encouragement, you are the reason we get to keep doing this.
Yes, an AI deleted our production database in nine seconds.
Yes, we recovered.
And yes, we are still, unequivocally, all in.