Documentation
You install SafeGrd on a host that can reach your database. It encrypts each backup on that host, writes it to a locked bucket, and restores it on a schedule to test it. Your data never passes through SafeGrd's server. If you set a surface to drill on SafeGrd, it is restored on a machine started for that drill and destroyed when it ends.
Quickstart
You can try it without an account. Once it is installed, safegrd try postgres://…
backs up one database and restores it as a check. Run safegrd signup to keep the
backup (Try it before you sign up).
Three commands get you a tested backup. The first prints a sign-in link you can open on any device, so it works over SSH too.
safegrd init and a first backup, recorded in a terminal.With a customer-managed key, keep a copy of ~/.safegrd/keys/daemon.key.
It is the key that opens your backups. With a SafeGrd-managed key, SafeGrd keeps it sealed for you.
If you have no account, or the host cannot reach SafeGrd, run safegrd init
instead. It sets up a host that backs up, restores and verifies on its own.
What the console shows
The other tabs are covered under Fire Drills and Account.
Where to go next
Install the CLI, enroll a host and choose how its key is managed.
02 Command referenceEvery command, flag and environment variable.
03 SurfacesWhat each database, file tree and mailbox backup captures.
04 Storage and retentionUse your own bucket or ours, with Object Lock and retention.
05 Threat ShieldGet an alert when tables or rows vanish. The last good snapshot is kept.
06 DaemonSchedules, the service and how it retries.
07 Restore and Fire DrillsRestore a backup, or test a restore away from production.
08 The attestation recordThe signed record of every drill, checkable offline.
09 Security and key custodyWhat SafeGrd holds and what it never receives.
10 Organizations and billingProjects, members, tokens and billing.
11 AI agents (MCP)Let a coding agent check, take and test backups. It cannot delete one.
12 TroubleshootingCommon errors and their fixes.