Backup and recovery designed around one question: how do we prove we can restore. Everything else follows from that.
A backup that has never been restored is a belief, not a control. We design the strategy — full, incremental and point-in-time — automate it, store it in a way that survives the failure it is meant to protect against, and then schedule regular restore tests with documented evidence.
This is deliberately positioned for organisations that do not need, and should not pay for, an enterprise backup suite. The engineering matters more than the product badge.
Who it’s for
Every organisation running a database or a file server. This is the most universal service we offer.
- Institutions with regulatory data-retention obligations
- Organisations whose current backup is a scheduled job nobody has tested
- Businesses that need reliable recovery without enterprise backup software licensing
- Teams that can back up but have no documented, timed restore procedure
What we deliver
A backup regime with tested restores and evidence you can hand to an auditor.
Recovery objectives
Agreed recovery point and recovery time targets per system, set against business impact rather than technical convenience.
Strategy design
Full, incremental and differential schedules, retention periods and point-in-time recovery capability matched to those objectives.
File system backup
Servers, workstations and virtual machines, with incremental scheduling to control storage growth.
Database backup
Engine-native backup with point-in-time recovery, consistent with your replication topology.
Storage design
On-site, off-site and offline or air-gapped copies, kept within your jurisdiction and your control.
Encryption
Backups encrypted at rest and in transit, with key management you own.
Automation and monitoring
Scheduled, monitored jobs where a failed backup raises an alert the same night, not at the next audit.
Restore testing
Scheduled restore drills, timed and documented, so recovery time is a measured number.
What we protect
- PostgreSQL
- MySQL / MariaDB
- Microsoft SQL Server
- Linux file systems
- Windows file servers
- Virtual machine images
On-premises versus cloud
Every criterion below is one your auditors will ask about. This is why we deploy inside your network by default.
| Criterion | On-premises, on your infrastructure | Public cloud / SaaS |
|---|---|---|
| Security | You control the firewall, the encryption keys, the access policy and the audit trail. | Shared infrastructure and a provider-defined security boundary. |
| Privacy | Data never leaves your network perimeter. | Data is stored and processed on third-party systems under their terms. |
| Autonomy | Full customisation, your upgrade schedule, no vendor lock-in. | Provider-driven roadmap and forced upgrade windows. |
| Integrity | You define backup, retention and recovery, and you test them. | You inherit the provider’s backup policy and their definition of acceptable loss. |
| Continuity | Service survives loss of internet connectivity; it runs on your intranet. | An outage or a commercial dispute at the provider becomes your outage. |
| Cost | Capital cost plus support; no per-seat escalation as headcount grows. | Per-user subscription that grows with your organisation. |
Backups are the last line. Where they are held, under whose jurisdiction, and who can technically access or delete them are questions worth being certain about.
How it connects to the rest of your stack
Nothing we deploy is meant to stand alone. These are the joins we build as part of the same engagement.
- Monitoring — Backup job success and failure are monitored checks with alerting — a silent failed backup is the most dangerous single condition in an estate.
- Disaster recovery — Backup is the foundation the recovery plan stands on; we design them together.
- Asset management — Backup coverage can be tracked against the asset register, which is how gaps get found.
Engagement summary
Questions we’re usually asked
We already have backups. Why would we need this?
The question is not whether backups run, it is whether a restore has been performed, timed and documented recently. In our experience that is where most estates fall short — and it only becomes visible at the worst possible moment.
Do we need to buy backup software?
Usually not. Engine-native tooling and well-engineered automation cover the large majority of requirements. We will tell you plainly if your case genuinely warrants a commercial product.