Simple, Transparent Pricing

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.

Ten probes are available: PostgreSQL, MySQL, MongoDB, SQLite, PocketBase, LDAP, X.509 certificate, HTTP health check, archive integrity and filesystem canary. Backups are fetched from Amazon S3 or compatible storage, a local or NFS share, or an HTTP URL.

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.

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.

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.

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.