How does RestoreProof ensure my backup data stays secure?

RestoreProof uses a strict separation between Control Plane (SaaS) and Data Plane (Runner). Your backup data and secrets never leave your infrastructure.

What databases and systems are supported?

RestoreProof supports PostgreSQL, MySQL, HTTP health checks, archive integrity verification, and filesystem canary checks. The probe system is extensible.

How do cryptographically signed reports work?

Each verification report is signed using Ed25519 digital signatures. This creates tamper-proof evidence that the verification actually occurred and the results have not been modified.

Can I run RestoreProof in air-gapped environments?

Yes. The Runner can operate in partially connected or air-gapped environments. Reports can be exported and verified offline.

What happens to probe containers after execution?

All probe containers are ephemeral and stateless. They are destroyed immediately after execution completes. No data persists between runs.

How do I handle secrets for database connections?

Secrets are resolved locally by the Runner using your existing secret management: environment variables, files, HashiCorp Vault, or SOPS. Secrets never travel to the Control Plane.

Now accepting early access signups

Don't trust your backups. Prove them.

Automated restoration verification. Local execution. Cryptographically signed reports. Your backup data never leaves your infrastructure.

Join Waitlist View Documentation

100%

Local Execution

Ed25519

Signed Reports

Zero

Data Exposure

See It in Action

restoreproof.io

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, or standalone binary. It connects securely to the Control Plane.

Define Restore Plans

Create restore plans with steps: fetch backup, unpack archive, start sandbox container, restore database (PostgreSQL, MySQL), run integrity checks.

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.

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)

Plan definitions

Scheduling & orchestration

Report aggregation

Signature verification

Data Plane (Runner)

Your infrastructure

Backup data access

Secret resolution

Probe execution

No backup data transmitted

No secrets transmitted

TLS encrypted metadata only

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."

Start Verifying Today

result.json

{
  "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