R1Soft and JetBackup solve overlapping problems with very different architectures. R1Soft is a block-level continuous data protection (CDP) system with its own kernel module; JetBackup is an account-level backup tool that talks to cPanel's API. The honest answer for most hosting companies is that neither one wins outright — they cover different failure modes, and many serious operators run both.
This article compares them on the dimensions that actually decide procurement: backup granularity, storage efficiency, restore experience, self-service in cPanel, off-site destinations, and licensing.
At a glance
| Dimension | R1Soft | JetBackup |
|---|---|---|
| Backup level | Block-level via hcpdriver kernel module | File and account-level via cPanel API |
| Storage engine | Proprietary disk safes with block-delta dedupe | Standard files (tar/incremental); dedupe optional |
| Storage efficiency | Wins on large servers (10:1+ on similar accounts) | Loses on similar accounts; comparable on diverse |
| Restore granularity | File, folder, full disk, bare metal | Account, mailbox, database, file |
| End-user self-service | Via cPanel plugin (clunky UI) | Native cPanel plugin (clean) |
| Off-site destinations | SBM-to-SBM replication only | S3, Wasabi, B2, SFTP, Google Drive, more |
| Restore from off-site | Replicate-back required | Direct from remote bucket |
| Performance impact | Low (block reads at the device layer) | Higher (reads through cPanel API + filesystem) |
| Licensing | Per protected machine on SBM | Per server (cPanel/Direct editions) |
| Operational complexity | High — central SBM, kernel module per host | Low — installs on each cPanel server, no central |
Backup architecture
R1Soft installs a kernel module on each protected machine. The module captures block-level changes at the device layer and streams them to the central SBM. The agent does not care about cPanel, filesystem layout, or account boundaries — it sees blocks. This is fast and storage-efficient, but it means a "restore one customer's email" operation requires mounting the disk safe and copying files out manually (or using the cPanel plugin).
JetBackup runs on the cPanel server itself and uses the cPanel API to enumerate accounts, then tars or rsyncs each one. It understands the cPanel object model natively, so "restore the bob@example.com mailbox to last Tuesday at 14:00" is one click.
The architectural difference cascades into everything else.
Storage efficiency
On a server with 200 similar WordPress accounts, R1Soft's block-level dedupe is dramatic — most accounts share OS-level files, common plugin code, and the WordPress core. R1Soft sees these as duplicate blocks and stores them once. We have seen 10:1 ratios sustained over months.
JetBackup stores per-account tarballs. Dedupe is available via the Wasabi or B2 backends but is filename-level — much weaker than block-level. On the same 200-account server, expect 2:1 to 3:1.
The gap closes when accounts are diverse — a server with 50 different CMSes, custom apps, and varying PHP versions has fewer duplicate blocks, so R1Soft's advantage shrinks.
Restore granularity
JetBackup wins on day-to-day restores. The flows are tuned for the most common request — "I deleted a file", "the database is corrupted", "I need yesterday's mailbox" — and end users do them through the cPanel plugin without a ticket.
R1Soft wins on disaster scenarios. Bare-metal restore to a different machine, full-disk recovery after a ransomware event, or restoring a server with a corrupted filesystem all work cleanly. JetBackup can do bare-metal but it is not its strong suit.
End-user self-service
Both expose backups in cPanel. JetBackup's plugin is native, fast, and matches cPanel's visual language. R1Soft's plugin works but feels bolted on — it is the same UI as the SBM, embedded in an iframe. End users can do single-file restores but the UX is enough worse that most hosts hide the R1Soft plugin and route restore requests through support.
If end-user self-service is a feature you charge for, JetBackup is the right pick.
Off-site destinations
JetBackup ships with native S3, Wasabi, Backblaze B2, SFTP, Google Drive, and more. Configuration is per-server. This is excellent for small-to-mid fleets that want backups in a separate provider for free.
R1Soft only replicates SBM-to-SBM. There is no S3 backend. The closest analogue is running a second SBM with cheap storage (a hetzner SX64 with 4x18TB drives is a popular pattern) and replicating to it. See Disk Safe replication setup for the configuration.
The "no S3" answer surprises people. R1Soft's view is that S3 latency and bandwidth costs make block-level CDP replication impractical, and they would rather you run a second SBM.
Performance impact
R1Soft reads at the block layer, below the filesystem. It is invisible to applications and does not contend with cPanel's process limits. The kernel module adds a tiny per-write overhead (single-digit percent on a busy MySQL server).
JetBackup reads through the cPanel API and the filesystem. On a server with 500+ accounts a full backup pass can take hours and noticeably load the disk during peak hours. Most operators schedule JetBackup overnight.
Licensing and cost
R1Soft licenses per protected machine on the SBM. You buy a pool (e.g. 50 machines), assign as you grow. The R1Soft license page has current pricing.
JetBackup licenses per server, with cPanel and Direct (Linux-only, no panel) editions. JetBackup 5 is current. The JetBackup license page has current pricing.
For a 20-server cPanel fleet, the per-month cost is broadly comparable — JetBackup tends to be slightly cheaper per server, R1Soft tends to be cheaper at higher per-server account density.
When to pick which
Pick R1Soft if:
- Your fleet is large (50+ servers) and storage efficiency matters
- You need bare-metal restore for DR drills or PCI/ISO audits
- Your customers do not self-restore (managed hosting, agency clients)
- You can run dedicated SBMs in two regions
Pick JetBackup if:
- You sell end-user self-service as a feature
- Your fleet is small-to-medium (under 50 servers)
- You want native S3 / Wasabi / B2 destinations
- Per-account, per-mailbox restores are your most common ticket type
Run both if:
- You take backup seriously enough to want defence in depth
- R1Soft for full DR and storage efficiency, JetBackup for end-user self-service and per-account restore
- The combined cost is justified by your account density
For the broader backup strategy question — including when cPanel's built-in is enough — see the 2026 cPanel backup strategy guide and the JetBackup vs cPanel built-in comparison.
Next steps
- Pick a stack: backup strategy for cPanel hosts in 2026.
- Buy R1Soft: R1Soft license.
- Buy JetBackup: JetBackup license.