Backups that actually restore
We design backups around how much data you can afford to lose and how fast you need to be back — then prove it with regular restore tests.
- Dedicated support from real engineers
Outcomes that matter to your business
Clear recovery targets
Agreed RPO and RTO for every system.
Copies in more than one place
Following the 3-2-1 rule, encrypted.
Tested, not hoped
Scheduled restore drills with a written result.
What we deliver
Everything below is included unless we agree otherwise in writing. You own the code, the designs and the data.
Technology we use for this
- pg_dump
- WAL archiving
- Restic
- Object storage
- Snapshots
- Encryption at rest
Backup design
What, how often, where and for how long.
Database-consistent backups
Proper dumps or point-in-time recovery, not just disk snapshots.
Off-site encrypted copies
Stored away from the production server.
Restore drills
Regular tests with a report you can show auditors.
A clear process, no surprises
- 01
Assess
What you have and what you can afford to lose.
- 02
Design
RPO, RTO and a retention policy.
- 03
Implement
Automated, encrypted, monitored backups.
- 04
Test
Restore drills on a schedule.
Questions we hear about this service
Aren’t server snapshots enough?
Snapshots help, but they live next to the server and can capture a database mid-write. We add database-consistent backups stored off the server.
How often do you test restores?
At least quarterly on Managed plans, and after major changes. You get a short report each time.
Where are backups stored?
In a different location from the server, in a region you choose — for example, keeping Australian data in Australia.
Your problem is our problem.
Tell us what you need. A senior engineer will reply within one business day — with questions, not a sales script.