lastresort · in private beta
A dated log of restores that actually completed
In brief
Replaces “the backups are fine” with a dated record that they restored. Restores run on a schedule in a sealed container, and the log is evidence that can go straight to an auditor, a customer or an insurer.
Evidence that your backups restore, produced on a schedule. A backup is fetched, restored into an isolated container with no route out, and checked against the questions you declared it should answer. The dated record is kept either way.
What it does
- The scratch container has no external egress, so a restored copy full of live credentials cannot call anything
- A failed check exits non-zero, which means cron and CI can act on it without a human reading a report
- The dated record is an evidence pack an auditor, a customer or an insurer can be handed
A closer look
Select any screenshot to enlarge it.
The lastresort.run landing page
The Lastresort demo overview, signed in as its read-only viewer
The run log in the Lastresort demo
The whitepaper behind it
The problem it measures, the method behind it, and what it deliberately does not do.