9 seconds.One agent action.
Production data gone.
Founder Jer Crane reported that a coding agent deleted the production database and volume-level backups in one action.
Independent backup for an agent-powered world
We’re building an independent way back, outside the permissions granted to your agents. Know what happened. Choose what comes back.
Join the waitlistSee how recovery worksGoogle Workspace is built. Airgap isn’t live yet. Get the first word when we’re ready.
PocketOS. Replit. OpenClaw.Publicly reported incidents
Good intentions. Real consequences.
Reporting context: Railway and Replit reported restoring the affected data. Permanent data loss is not established for OpenClaw. Nine seconds is the PocketOS founder’s reported timing. These are independent reports, not Airgap customers or evidence that Airgap would have prevented the incidents.
Illustrative scenario · sample data
Client handovers, decisions, conversations
Launch plans, research, working documents
Meeting notes, briefs, business records
The same access can put your backup at risk, too.
Saved before the example incident.
Outside the agent’s granted permissions.
Example ready. Play the mistake to see which copies are affected.
An explanation of the intended recovery boundary, using fictional records. Recovery depends on a successful saved copy, supported scope and available recovery options.
The recovery approach keeps a copy outside the permissions you have already granted to your agents.
Review recorded actions and available actor information. Unknown stays unknown.
Review supported saved items and the recovery options that fit the incident.
The intended recovery experience requires a successful saved copy. Coverage and attribution depend on the source.
The setup we’re building
Review permissions and connect an eligible account when Airgap launches.
Understand the supported services, what gets saved and where the limits are.
A completed saved copy is the milestone that matters. Joining the waitlist does not start a backup.
Three intended stages. Provider consent or administrator approval can add steps. We’ll share launch details when the service is ready.
Be there for launchYes. Google provides native recovery capabilities for Drive and Gmail, with defined conditions and time limits. An independent backup is a separate question: what copy remains available, who can delete it and how will you restore the work you need? Google's recovery documentation
Link to this answerIt can if the effective permissions it holds allow both operations. The relevant distinction is authority: keeping a copy in another folder does not by itself prove that the agent cannot reach or remove it.
Link to this answerThe intended recovery experience lets you choose supported saved items and versions instead of assuming everything must be rolled back together. Check the integration’s supported objects, destinations and limitations.
Link to this answerAfter the relevant data has been captured successfully. Payment and account connection are setup milestones, not proof of a completed backup. Check the captured scope, completion result and freshness; a partial capture needs attention to the missing items.
Link to this answerPre-launch. Get the first word.
Google Workspace is built. Airgap isn’t live yet. Join for launch updates and tell us which integrations you want next.
Your work is moving forward.
We’re building the way back.