Devani keeps your site recoverable at three layers, all automatic. Knowing which layer to reach for saves time when something's wrong.
1. Per-edit snapshots — "undo my last few edits"
Every write to content — an editor save, an MCP/AI change, a header or stylesheet update — first snapshots the previous version of the affected files. The newest few snapshots per file group are kept and older ones pruned, so this layer is for quick undo, not deep history.
Restore: via the admin, or ask your connected AI to list snapshots (optionally filtered to one file, like the header) and restore one. Restores take a fresh safety snapshot of the current state first — so a rollback is itself reversible.
2. Scheduled content snapshots — point in time
The whole content tree is snapshotted on a schedule — daily by default (weekly or off if you prefer), with a configurable retention window (30 days by default). Find and restore them in the admin under System. This is the layer for "it was fine last Tuesday."
3. Hourly storage backups — settings and records
Devani's internal storage (settings, users, orders, media records) is backed up hourly, separately from content. You'll rarely touch this layer, but it means even non-content data has history.
What's deliberately excluded
- Media files live on the Tonta CDN independently — content restores never touch them, and removing an image from a page never deletes the file.
- Integration API keys are excluded from content snapshot archives by design, so a snapshot tarball never leaks credentials.
The practical map
- Bad edit just now → per-edit snapshot.
- Broken for days → scheduled snapshot from before the break.
- Settings/order weirdness → storage backups.
- Server died entirely → your host's own machine backups (worth enabling; Devani's layers live on the same disk).