The scariest moment in webcare is the restore that doesn’t work. So we don’t promise your data is safe — we prove it, on a schedule, and we audited our own pipeline to make sure.
Most “backups” are never tested until the day you need them. That’s the worst possible day to discover they don’t restore.
After every backup, we don't just check that a file exists — we check that the bytes match. Binary and database columns are captured exactly, so a restore brings back precisely what you had: no truncated émojis, no mangled serialized data, no silently dropped rows.
Every week we take a real backup and restore it into an isolated scratch database, then scan the recovered data for corruption. If a backup can't restore cleanly, we find out on our schedule — not on the day your client's site is down.
An empty or truncated dump is rejected, not uploaded. A backup that passes our checks is one we've proven is complete. The worst backup is the one you think you have but don't — so we refuse to pretend.
Most backup bugs never announce themselves — the dump looks valid, the file uploads, and the data is wrong. We ran a full data-fidelity audit of our own backup and restore path and found six ways WordPress data can silently corrupt. Then we fixed every one and added the checks that catch the next one.
The agent on your site talks to us over a per-site secret with HMAC-signed requests, a timestamp window, and single-use nonces. Nothing can impersonate your site or replay an old request.
Commands we send to your site are cryptographically signed and verified by the agent before they run. Even if the network between us were tampered with, a forged command is rejected.
Backups are encrypted and stored offsite in a private Cloudflare R2 bucket. Downloads happen through short-lived, scoped links — never a public URL.
We ran a full security audit of the platform — injection, remote code execution, SSRF, secrets, dependencies and infrastructure — and fix what we find. Your maintenance tool shouldn't be your biggest risk.
Send us your URL. We’ll dig through it and come back with what’s at risk, whether your current backups would actually restore, and what we’d fix in week one. No pitch. Free.