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.

RestoreProof supports PostgreSQL, MySQL, HTTP health checks, archive integrity verification, and filesystem canary checks. The probe system is extensible, so you can add custom verification logic for any system.

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.

Yes. The Runner can operate in partially connected or air-gapped environments. Reports can be exported and verified offline. Contact us for enterprise deployments with specific network constraints.

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 using your existing secret management: environment variables (env://), files (file://), HashiCorp Vault (vault://), or SOPS (sops://). Secrets never travel to the Control Plane.