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. The Runner executes all restore tests locally, and only metadata (status, metrics) is sent to the Control Plane.

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. Signatures are verified by the Control Plane for audit trails and compliance.

What network access does the Runner need?

One outbound connection to the Control Plane, plus access to your backup storage. No inbound port to open, no address to expose. A fully disconnected environment is not supported today — write to us if that is your case.

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. This ensures isolation and prevents any potential data leakage between verification runs.

How do I handle secrets for database connections?

Secrets are resolved locally by the Runner: environment variables (env://) or files mounted in the container (file://). RestoreProof stores the secret reference only, never its value, and secrets never travel to the Control Plane.

Free plan, no credit card

Don't trust your backups. Prove them.

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

Start for free View documentation

100%

Local Execution

Ed25519

Signed Reports

Zero

Data Exposure

See It in Action

Sixty seconds: test the restore before the incident, and keep the evidence of every test

restoreproof.io

How It Works

Three simple steps to verify your backups actually restore

Deploy the Runner

Install the RestoreProof Runner on your infrastructure with Docker, or the Helm chart on Kubernetes. It opens an encrypted channel to the Control Plane itself — no inbound port to open on your side.

app.restoreproof.io

RestoreProof deploy-a-runner wizard: the generated docker run command with the runner API key

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 the database (PostgreSQL, MySQL, MongoDB, LDAP), run integrity checks.

app.restoreproof.io

RestoreProof add-a-backup wizard asking what kind of data is backed up

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.

app.restoreproof.io

RestoreProof run detail: a passing proof report with its probe results and its Ed25519 signature

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.

app.restoreproof.io

RestoreProof scheduling wizard: how often to test a backup, with the next run date

Put it on a schedule

Nightly, weekly, monthly or your own cron. The next run is shown before you confirm.

app.restoreproof.io

RestoreProof connect wizard: the webhook URL and the Restic integration snippet

Fire it from your backup tool

Restic, Borg, Veeam, Duplicati, rclone: copy the snippet, paste it after your backup command.

app.restoreproof.io

RestoreProof dashboard: restorability score, active runners and verified backups

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.

Ten Probes Out of the Box

PostgreSQL, MySQL, MongoDB, SQLite, PocketBase, LDAP, X.509 certificate, HTTP health check, archive integrity and filesystem canary.

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.

Several Runners

Deploy one runner per site, environment or customer, label them to find your way around, and pick the one that runs each test.

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 for free

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

What's next

Here is what we are working on. We announce no date, and none of it is sold in today's plans.

Coming soon

Standalone runner binary

Install the runner without a Docker image, on a plain Linux machine or as a systemd service.

Coming soon

Google Cloud Storage and Azure Blob

Read backups straight from GCS and Azure Blob Storage, the way the runner already reads S3, a local or NFS share and an HTTP URL.

Coming soon

Backups from the Windows world

Restore and verify a SQL Server backup, read network shares, and prove the freshness and completeness of the exports business applications produce.

Coming soon

Virtual machine and container backups

Prove a backed-up VM image is usable without booting it: full extraction, healthy filesystems, a coherent system, and the databases it holds brought up in a sandbox.

Frequently Asked Questions

Everything you need to know about RestoreProof

Ready to Verify Your Backups?

Create your account, deploy a runner, get your first signed report.

Start for free