Your backups run.But can you actually restore?
DrillProof is backup and disaster recovery for Kubernetes and AWS — immutable, cost-tiered, and proven with automated recovery drills. Runs in your own cloud account.
- Runs in your account
- Your data never leaves your region
- Immutable (S3 Object Lock)
- Certified-Kubernetes compatible
| RESOURCE | BACKUP | RESTORE |
|---|---|---|
| payments-db (RDS) | ok | untested |
| orders-pv (EKS/EBS) | ok | verified |
| etcd (prod-cluster) | none | failed |
Recoverability Score: 61/100 (3 critical gaps)
- etcd for prod-cluster has NO backup
- 4 restore points never test-restored ("backed up" != "recoverable")
Most backups are never tested.
Many fail when it matters.
Snapshots complete. Jobs go green. The dashboard says protected, so everyone assumes recovery works — until ransomware, a bad deploy, or a dropped table forces the first real restore of the year. That is when teams discover the volume was never consistent, the database dump was truncated, or nobody captured cluster state at all.
“Backed up” is not “recoverable.” The only way to know the difference is to perform the restore — before you need it.
Three steps, then it runs itself
Connect once. DrillProof backs up, tiers, and re-tests on the schedule you set.
- 01
Connect your cloud, keep your data
You create a scoped cross-account IAM role with an external ID. DrillProof orchestrates through it; nothing is copied out. Revoke it at any time and the connection ends.
- 02
Back up immutably, tier automatically
Cluster state via Velero, EBS volumes and RDS databases as consistent restore points. Written under S3 Object Lock, then aged down the storage classes by policy.
- 03
Drill on a schedule, get proof
A real restore runs in isolation, gets verified, and tears itself down. What remains is a dated record and a Recoverability Score you can show anyone.
What you get
Six things that hold up under a skeptical read.
Tested recovery
Scheduled drills restore your latest backup in an isolated environment, verify it, and record the result. Recoverability becomes a number you can watch.
Immutable by default
Backups land in S3 Object Lock storage under WORM retention. Ransomware and a bad credential cannot rewrite or delete what is already locked.
In your own account
Bring-your-own-cloud is the default: snapshots, volumes and restores stay in your account and your region, and the control plane holds metadata only. A hosted option exists if you would rather not run storage.
Cost-tiered storage
Retention policies move older restore points down the storage classes automatically, so long retention stops being an argument with finance.
For Kubernetes and AWS
Cluster state and manifests through Velero, persistent volumes on EBS, and managed databases on RDS — captured as one consistent restore point.
Evidence built in
Every drill leaves a dated record of what was restored and what was checked. Export it when an auditor asks how you know recovery works.
At launch: Amazon EKS · Amazon EBS · Amazon RDS on AWS.
Coming: Amazon EFS · DynamoDB · S3 · SaaS sources.
The drill
A restore that actually happened, four times a month
A drill is not a checksum or a dry run. DrillProof recovers the real restore point into a throwaway environment, proves it works, and removes it.
- 01
Restore
The latest restore point is recovered into an isolated, throwaway environment in your account. Production is never touched.
- 02
Verify
Volumes mount, the database accepts a connection, and workloads reach ready. Checks are asserted, not assumed.
- 03
Tear down
The isolated environment is destroyed, so a drill costs the runtime of the drill and nothing after it.
- 04
Evidence
A dated record of what was restored, what was checked, and how long it took — retained for auditors.
Start free from your terminal
See if you are actually recoverable before you talk to anyone. The scan is read-only and reports on the backups you already have.
$ drillproof audit scan --region ap-southeast-1
RESOURCE TYPE BACKUP AGE IMMUTABLE RESTORE
payments-db (RDS) database ok 6h no untested
orders-pv (EKS/EBS) volume ok 3h yes verified
etcd (prod-cluster) k8s-state none - - failed
Recoverability Score: 61/100 (3 critical gaps)
x etcd for prod-cluster has NO backup
! 4 restore points never test-restored ("backed up" != "recoverable")
Fix free: https://drillproof.com/auditPick a recovery objective, not a package
Two dials: a flat platform fee per protected workload, plus per-TB retained. Your recovery tier multiplies the first one. No surprise bills.
Backup & Restore
RTO hoursRestore when you need it.
Pilot Light
RTO tens of minutesCore services stay warm.
Warm Standby
RTO minutesScaled-down copy, always running.
Find out if you are actually recoverable — free.
We connect read-only, test-restore your latest backups, and send you a report. No commitment.