Connect once. Stay recoverable.
Five minutes of setup. After that, Backup Safe backs up, verifies and restore-tests on its own, and tells you the moment anything needs your attention.
Start your free trial
Create an account and pick a plan. The first 7 days are free with every feature on (up to 2 databases and 5 GB during the trial).
Connect your database
Allow Backup Safe's IP address on your database, then paste a PostgreSQL connection string; a read-only user is enough for backups. Backup Safe tests the connection, detects the server version and encrypts the connection string straight away. It's never shown again.
Choose schedule and encryption
Daily at the hour you choose, or hourly on Pro. Keep standard encryption, or switch on own-key mode so only your passphrase can unlock your backups, and save your recovery kit.
Every backup: encrypted, uploaded, verified
The dump is made with the PostgreSQL version matching your server, encrypted as it streams and uploaded. Then the stored copy is downloaded again, checksummed, fully decrypted and read end to end. Only then is it marked Integrity verified
Every day: a real restore test
Once a day, the newest verified backup of each database is restored into an isolated sandbox with no network access and no privileges, compared object by object with the original, and deleted. Backups over 5 GB are integrity-verified but not restore-tested, and the dashboard shows exactly which backup was tested and when.
You're told when something needs you
Each database has one health state based on its latest backup. Failed backups, failed checks and storage warnings arrive by email in plain language, with the technical detail one click away.
Restore in one click, or anywhere
Restore into the original or a staging database. The backup is authenticated first and restored in a single transaction: it completes fully or changes nothing. You can also download a standard PostgreSQL dump, or decrypt own-key backups offline with your recovery kit.
Encrypted before it leaves the server.
In transit
From your database over its own connection settings (TLS supported), straight into the encryptor.
At rest
Only encrypted files are stored, each with its own key.
During tests
Restored into a throwaway sandbox database that is deleted right after.
The next restore you run shouldn't be your first.
Connect a PostgreSQL database in two minutes, then watch its first backup get encrypted, verified and restore-tested.