Deduplication that pays for itself
Content-defined chunking with BLAKE3 content addressing, so an unchanged block is referenced rather than re-uploaded — across every backup and every asset in the repository. FastCDC, BLAKE3, zstd.
Data protection
RemoteBackups
One control plane for servers, databases, hypervisors, cloud VMs and SaaS — backing up to storage you own. Copies are deduplicated, compressed and encrypted before they leave your network, and every restore is verified chunk by chunk against its content address.
43
Platforms in the catalogue
12
Storage backends supported
9
Hypervisor & cloud VM platforms
100%
Of your data, on your own storage
Backups you can actually restore — proven, not promised
What RemoteBackups is
Most backup failures are discovered during the restore. A green dashboard is not evidence: archives silently truncate, credentials rotate, retention quietly deletes the copy you needed, and ransomware encrypts the repository along with production. RemoteBackups is built so each of those fails visibly and early, in a way you can act on.
Snapshot orchestration is used where the platform does it best — hypervisors and cloud VMs — and full copies into your own storage everywhere else. Both paths share one repository format, one retention model and one restore path.
Capabilities
Everything RemoteBackups does
Encrypted before it leaves
AES-256-GCM with per-chunk authentication, keyed from your organisation's master key. The storage provider holds ciphertext and cannot see your file names or content hashes.
Immutable by physics, not policy
Copies are written under S3 Object Lock, so the storage backend itself refuses deletion until retention expires. Stolen credentials cannot erase what the bucket will not delete. Governance and compliance modes both supported.
Granular restore with undo
Browse a recovery point and restore a single file or a single database row, preview the diff before applying it, and roll the change back if it was wrong. Four-eyes approval on the sources that warrant it.
Point-in-time recovery
Replay the transaction log forward from a recovery point to a chosen moment, so the answer to “restore to just before 14:32” is a real answer rather than the previous nightly.
One line to protect a server
Paste a single command into a root shell; the agent picks the right build, verifies it, installs the service and enrols itself. It reports what it can protect — including every cPanel/WHM account on the box — and you tick what a policy should cover.
Built for distant storage
Chunks are hashed, compressed, encrypted and uploaded in parallel, so throughput follows your bandwidth rather than your round-trip time. Uploads resume part by part; a dropped connection costs one 16 MiB retry, not the whole run.
DR orchestration
Recovery plans are a boot-order DAG rather than a wiki page. Run them non-disruptively as a rehearsal or for real as a failover, and get measured RTO and RPO against your targets.
Under the hood
A platform that runs deep
The parts you would usually pay three separate vendors for — built in, and switched on from one console.
Ransomware detection
A backup whose data suddenly stops compressing is a backup of encrypted files. Reduction ratio, entropy, churn and mass-deletion signals are scored together by a model that learns from your analysts' verdicts.
IoC threat hunting
Sweep every recovery point for known-bad hashes, ransom notes and filename patterns, including feeds you subscribe to, and get a timeline showing the last clean point to restore from.
Answers grounded in your data
Ask when the last clean backup of a given database was, and get an answer assembled from the catalogue with the recovery points it used shown alongside.
Verified on restore
Every chunk is re-hashed on the way back and a size mismatch is an error, so a corrupted or tampered backup fails loudly instead of quietly handing back bad data.
No vendor lock-in
Your buckets, your keys, and the whole stack is self-hostable end to end — an air-gapped copy stays your decision rather than a vendor's.
Guided connectors
Every one of the 43 connectors ships with a setup wizard and a live connection test, so you find out it works before you schedule anything.
Who it is for
Built for teams like these
MSPs & hosting providers
One repository format across every client platform, with per-client isolation and restores you can demonstrate.
Regulated teams
Immutable retention under Object Lock, four-eyes restore approval and measured RTO/RPO against your stated targets.
Self-hosters
Run the whole stack yourself, into your own buckets, with your own keys — nothing about recovery depends on us.
Common questions
RemoteBackups, answered
Still weighing it up? Tell us your stack and we will tell you honestly whether this fits.
Request pricingWhat stops ransomware from destroying the backups too?
Copies are written under S3 Object Lock, so the storage backend refuses deletion until retention expires — stolen credentials cannot erase what the bucket will not delete. The backup stream is also analysed for ransomware signals, because a backup whose data suddenly stops compressing is a backup of encrypted files.
How do we know a backup will actually restore?
Every chunk is re-hashed against its content address on restore and a size mismatch is treated as an error, so a corrupted or tampered backup fails loudly rather than quietly returning bad data. Recovery plans can also be rehearsed non-disruptively.
Can we host it ourselves?
Yes. The whole stack is self-hostable, the data goes to storage you own, and you hold the encryption keys. The free tier is permanent and needs no card.
What can it protect?
43 platforms across nine databases, eight applications and SaaS tenants, six hypervisors, six clouds, five hosting panels, four storage backends, three server types and two container platforms.
More products
All 10 products