Devani keeps your site recoverable at three layers. You'll mostly use the first one.
1. Per-edit snapshots (quick undo)
Every write — a page save in the editor, or any change Claude makes — first saves a snapshot of the previous version of the affected files. Think of it as "undo my last few edits": the most recent snapshots per file are kept, older ones are pruned automatically.
To roll back, just ask Claude: "list the snapshots for the pricing page and restore the one from before my last change." Restores are themselves snapshotted first, so even a rollback can be rolled back.
2. Scheduled content snapshots (point in time)
On top of per-edit snapshots, the site takes scheduled snapshots of your whole content tree — daily by default, with a configurable retention window (30 days by default). These are for "the site was fine last Tuesday" situations, and you'll find them in the admin under System.
2½. What snapshots don't cover
Media files live on the Devani CDN, which stores them independently — deleting an image from a page never deletes the file. Integration keys and settings are stored separately from content and aren't affected by content restores.
3. Platform backups (ours)
Underneath all of that, Devani Hosting backs up the servers your sites run on. You never interact with this layer directly — it exists so that even infrastructure-level problems don't cost you your site.
The practical advice
- Made a bad edit just now? Per-edit snapshot — ask Claude to restore, or check the admin.
- Something's been wrong for days? Scheduled snapshot from before it broke.
- Worried in general? Don't be — every layer runs automatically. There is no backup plugin to install, configure, or forget about.