About
Why RestoreProof exists.
RestoreProof exists because of the sentence every engineer dreads: 'our backups hadn't run in 6 months and nobody noticed.' Everyone backs up. Almost nobody tests restores. RDS snapshots exist — and verify nothing.
We do the one job nobody else does standalone: every week, restore your Postgres/MySQL backup into an isolated sandbox and run integrity checks. Green badge in Slack. Red alert on a Tuesday morning — while there's still time to fix it.
We speak in check results, not adjectives. 'Verified Tuesday 03:14 UTC. 14/14 checks green.' That's the whole pitch — proof, not promises.
What we won't do
- The simulated driver verifies manifest-based artifacts; real pg_restore/mysql restores are a per-customer setup step (the scaffold raises an honest error until configured).
- RestoreProof verifies backups; it does not take them — bring your pg_dump, WAL archives, or snapshots.
- Alert delivery in v1 is an operator-pulled queue; connect your own notifier for Slack/email.
- We never claim guaranteed recovery or zero data loss. Verification logs hold metadata only — never row data.