DrillProof

DrillProof is a backup and disaster recovery platform. Its premise is a single distinction most backup tooling glosses over: "backed up" is not "recoverable."

The Problem

Backup jobs complete. Dashboards go green. The workload is marked protected, and everyone moves on. None of that is evidence, because the only thing that proves a backup works is restoring it — and most teams first attempt that during an actual outage, which is when they discover the volume was captured mid-write, the database dump is truncated, or the surrounding state needed to make any of it run was never captured at all.

The gap is not backup coverage. It is the absence of proof.

What It Does

DrillProof runs the restore for you, on a schedule, into an isolated environment, and writes down what happened. Each drill produces a dated record of what was restored, whether it came back intact, and how long it took — a recoverability score with a report behind it, rather than a job status.

That artifact does double duty: it is the operational signal that recovery still works after three months of schema changes, and it is the evidence an auditor asks for.

Coverage

The platform protects the whole estate rather than one layer of it: managed and self-hosted databases, block volumes, object storage, file systems, and container cluster state. Kubernetes is covered, but it is one workload type among many — the failures that actually hurt tend to be the stateful pieces sitting underneath a cluster, not the cluster itself.

Coverage spans AWS and Azure, so an estate split across two providers produces one recoverability picture instead of one console per cloud and a spreadsheet reconciling them.

Immutability and Data Residency

Recovery points are written with WORM object lock and immutable retention, which means a compromised credential cannot quietly delete or rewrite the one backup it would most want gone.

The platform is bring-your-own-cloud. Backup data is written into the customer's own account and region and stays there; only metadata crosses into the DrillProof control plane. Retention policies tier older recovery points into cheaper storage classes automatically, so a long retention window does not price itself out.

Pricing by Recovery Objective

Plans are chosen by the recovery time the business actually needs, not by a feature matrix:

Billing is a flat platform fee per protected workload plus per-TB of retained storage, which keeps the cost tied to what is being protected rather than to which features are switched on.