A daily backup loses 24 hours of orders.
If something goes wrong at 3pm, the most recent backup is from 2am. Every order, comment, form submission and edit since then, gone. With snapshots every hour, your worst case is 1 hour, not a full day.
Reading mode
Backups every hour.
Restore in one click.
Most hosts back up your site once a day, in production, and hope nothing goes wrong. We snapshot at the storage layer every hour, replicate off-site, and let you roll back any file or table in under a minute, with zero impact on your live site.
Hourly
Snapshot frequency
720 restore points / month
14 days
Retention window
Roll back to any point
Off-site
Replicated geo-redundantly
Different region, different provider
< 60 s
Median restore time
Files or full site
Why high-frequency
Most backup plans are designed for the host, not for you.
Once-a-day, taken at peak traffic, stored on the same disk, with a restore that requires a support ticket. We did the opposite of all four.
Backups should never slow your site down.
We snapshot at the storage layer (ZFS), not the application. Your CPU, RAM and database aren't touched. Visitors don't notice; you don't get a 'site is sluggish' ticket from a customer mid-backup.
Off-site or it doesn't count.
Backups stored on the same machine as the site help you recover from a bad plugin, not from a hardware failure. We replicate every snapshot to a different region on a different provider, so the worst day still has an undo button.
How it works
From snapshot to restore, in under a minute.
A pipeline designed so the only thing you ever have to do is pick a point in time.
01
Snapshot every hour
ZFS storage takes a copy-on-write snapshot of your site's filesystem and database. The operation is atomic and finishes in milliseconds, your site keeps serving traffic without a hiccup.
02
Stored on a separate volume
Snapshots live on dedicated backup storage, not on your site's NVMe drive. A bad disk on the live server doesn't take your history with it.
03
Replicated off-site, every hour
Every snapshot is replicated to a second region within minutes. The copies are encrypted at rest with per-customer keys.
04
14 days of restore points
You always have 720 restore points (24 × 30) to choose from. Pick a moment, preview, restore, files only, database only, or the whole site.
One-click restore
The point of a backup is the restore.
Plenty of hosts will sell you a backup. Far fewer will let you actually use it without opening a ticket and waiting four hours. We obsessed over the restore flow, because that's the part that matters.
See it in actionStep 01
Pick a restore point
Browse 14 days of 4-hour snapshots. Filter by date, search by event (we tag deploys, plugin updates and core upgrades).
Step 02
Choose what to restore
Full site, files only, database only, or a single file/table. Useful when a plugin update broke one page but you don't want to roll back yesterday's orders.
Step 03
Preview before committing
Spin up a temporary clone of the snapshot on a staging URL. Verify, then promote, or discard and try a different point in time.
Step 04
Restore in one click
Median restore in under a minute for sites under 5 GB. Your live site stays online during the restore, we cut over atomically when the new copy is ready.
Vs. the usual suspects
Daily backups are the floor. Not the standard.
| Capability | WP Tango | Kinsta | WP Engine | Generic shared |
|---|---|---|---|---|
| Backup frequency | Hourly | Daily | Daily | Daily |
| Retention window | 14 days | 14 days | 60 days | 7 days |
| Storage-layer snapshots (no CPU hit) | ||||
| Off-site replication (different region) | ||||
| Restore individual files / tables | ||||
| Preview restore on staging first | ||||
| One-click self-serve restore |
Where it matters
The day you actually need a backup.
Real situations our team handles every week, and the difference between 4-hour snapshots and daily is the whole story.
A plugin update broke checkout at 4pm.
With daily backups, you'd lose the morning's orders rolling back to 2am. With 4-hour snapshots + per-table restore, we roll back just the plugin's database tables to noon, and every order taken in between is preserved.
Someone deleted the wrong page.
Browse to the most recent snapshot, restore that single file/post, and you're done. No full-site rollback. No lost work elsewhere.
Your site was injected with a redirect.
We pinpoint the exact snapshot before the injection, restore the affected files, rotate the keys, and have you clean again, usually in under 10 minutes.
Backups, plainly explained.
Everything teams ask before trusting us with their site's history.
Didn't find what you were looking for? Our friendly support team is just a message away and happy to help.
Chat with us