Don't trust your backups. Prove them.
Automated restoration verification. Local execution. Cryptographically signed reports. Your backup data never leaves your infrastructure.
See It in Action
Register a runner, configure storage, and create your first restore plan
How It Works
Three simple steps to verify your backups actually restore
Deploy the Runner
Install the RestoreProof Runner on your infrastructure via Docker — Kubernetes and standalone binary support coming soon. It connects securely to the Control Plane.
The app writes the docker run command for you, API key included.
Define Restore Plans
Create restore plans with steps: fetch backup, unpack archive, start sandbox container, restore database (PostgreSQL, MySQL), run integrity checks.
Tell it what the backup holds and where it lives. No credentials leave your infrastructure.
Run Probes & Get Reports
Execute verification probes in isolated containers. Get PASS/WARN/FAIL results with metrics. Reports are signed with Ed25519 for tamper-proof evidence.
Every run ends in a signed report — evidence you can hand to an auditor.
Set it once, then forget it
Put the checks on a schedule, fire them from your backup tool, and keep one number to watch.
Put it on a schedule
Nightly, weekly, monthly or your own cron. The next run is shown before you confirm.
Fire it from your backup tool
Restic, Borg, Veeam, Duplicati, rclone: copy the snippet, paste it after your backup command.
One number to watch
Restorability score, runner fleet and verified backups — the whole state on one screen.
Built for DevOps Teams
Enterprise-grade backup verification without compromising security
Data Never Leaves Your Infra
Backup data and secrets stay local. The Runner executes everything on your infrastructure. Only metadata reaches the Control Plane.
Isolated Probe Containers
Each probe runs in a stateless, ephemeral OCI container. Destroyed immediately after execution. No data persistence, no cross-contamination.
Multi-Database Support
PostgreSQL, MySQL, HTTP health checks, archive integrity, and filesystem canary. Extensible architecture.
Scheduled Runs
Automate verification with cron-like scheduling. Run daily, weekly, or after each backup. Never wonder if your backups work.
Ed25519 Signed Reports
Every report is cryptographically signed. Tamper-proof verification evidence for compliance and audit trails.
Multi-Runner Support
Deploy multiple runners with labels for targeting specific environments. Route plans to the right runner automatically.
Architecture
Strict separation between Control Plane and Data Plane
Control Plane (SaaS)
Data Plane (Runner)
Why RestoreProof?
An untested backup doesn't exist. You might have terabytes of backup data, but without verification, you're hoping, not knowing.
Hope is Not a Strategy
Most teams discover their backups are broken during a real disaster. By then, it's too late.
Proof, Not Hope
Ed25519 signed reports provide cryptographic proof that your backups actually restore. Evidence you can audit.
Automate the Boring Stuff
Scheduled runs mean you verify automatically. No more "we should probably test backups this quarter."
{
"status": "PASS",
"probe": "postgres",
"duration_ms": 1247,
"metrics": {
"tables_verified": 42,
"rows_sampled": 10000,
"checksum_valid": true
},
"signature": "ed25519:...",
"timestamp": "2024-01-15T10:30:00Z"
}Frequently Asked Questions
Everything you need to know about RestoreProof
Ready to Verify Your Backups?
Join the waitlist and be the first to know when RestoreProof launches
Join Waitlist