The four ways in
- Connect your server. Your tech person pastes one line. Our helper makes, encrypts and sends us a copy each week. We need no key from you. Coming first, in version one.
- Connect your hosting. Type your cPanel or Plesk login once, and your host sends us a full backup each week. Later.
- Connect your storage. Sign in once to Dropbox, Google Drive or the S3 bucket where your backups already land, and we fetch the copy each week. Later.
- Connect your platform. Shopify, Google Workspace, Microsoft 365 or Xero: we pull the weekly export and prove it opens and holds the right counts. Later.
None of the four is open to customers yet. Each one appears here as available on the day it is built and tested. Today our own system is rehearsed every week.
Your first rehearsal is the proof
Your kind of system does not need to be on a list. Your first rehearsal is the proof, and it is free. If it fails, the plain report of what broke is free too.
If your first rehearsal needs fixing, you choose how to pay for the fix:
- A one-off setup fee, then monthly from your first PASS. Cancel any time.
- No setup fee, with a twelve-month minimum on the base package.
Billing and the Monday emails start on your first PASS, not before.
For your tech person: the readiness check
Before a first rehearsal, the readiness check gives a quick read of how ready a server is. It is one command, read-only, with no network:
docker run --rm --network none \ -v /var/run/docker.sock:/var/run/docker.sock:ro \ -v /srv/ops:/stack:ro \ proven-restorable/check --compose /stack/docker-compose.yml --manifest /stack/stack.yaml
--network none: the container has no network, so it cannot send anything.- The Docker socket and your stack directory are mounted read-only. The check lists containers, volumes, host services, cron and the last backup run. It reads names, sizes and times, never contents, and it never starts, stops or changes anything.
- It lists what a fresh server would not have: data in no backup, services outside what is declared, a credential baked into an image, and the questions only a person can answer.
The check is not the proof. It reads; it does not restore anything. Only a rehearsal, where your backup is rebuilt on a fresh server and checked, shows that you can be restored. The check image is not published yet; it will be when the code opens in December.