Softwr

Backup · head to head

Borg Backup vs Rook

Borg Backup logo

Borg Backup

Backup

Deduplicating archiver with compression and encryption

From
Free
Rated
-
Rook logo

Rook

Cloud

Kubernetes operator that deploys and manages Ceph storage clusters

From
Free
Rated
-

The short version

  • Each has a real cost: Borg Backup linux, macOS and BSD only; Windows is not a supported platform; Rook rook automates Ceph but does not abstract it, so an incident still demands Ceph expertise, and organisations without it end up hiring consultants at exactly the wrong moment.
  • They diverge on capability: Borg Backup covers Content-defined chunking, Rook covers Ceph operator.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Borg Backup and Rook actually diverge.

Attributes where Borg Backup and Rook differ
AttributeBorg BackupRook
Pricing modelfreeOpen source, no licence fee
PlatformsLinux, MacLinux, Kubernetes
CategoryBackupCloud
Founded2015Unknown

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Borg Backup

  • Content-defined chunking
  • Deduplication
  • Compression
  • Authenticated encryption
  • Pruning
  • Mount archives
  • SSH
  • BorgBase

Only in Rook

  • Ceph operator
  • Block, file and object
  • Erasure coding
  • CSI driver
  • Automated upgrades
  • Multi-cluster mirroring

What people use each for

The jobs each tool is most often brought in to do.

Borg Backup

  • Deduplicated backups where daily full snapshots would otherwise be expensivenot Rook
  • Encrypted backup to a server you do not fully trust, since the server never sees plaintextnot Rook
  • Browsing previous versions by mounting an archive over FUSEnot Rook
  • Scripted server backups with no agent or daemon to runnot Rook

Rook

  • An on-premises Kubernetes platform needing block, shared filesystem and S3 storage without buying three productsnot Borg Backup
  • A team that already runs Ceph and wants its lifecycle managed declaratively inside Kubernetesnot Borg Backup
  • A large cluster where three-way replication overhead is unaffordable and erasure coding is requirednot Borg Backup
  • An organisation building a private cloud that cannot use managed cloud storage services for residency reasonsnot Borg Backup

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Borg Backup

  • Linux, macOS and BSD only; Windows is not a supported platform
  • Command-line only, with no graphical interface in the project itself
  • Version 2.0 is still in beta, so production use means staying on the 1.4 line
  • Restoring requires the Borg tooling, since archives are a deduplicated chunk store rather than plain files

Rook

  • Rook automates Ceph but does not abstract it, so an incident still demands Ceph expertise, and organisations without it end up hiring consultants at exactly the wrong moment.
  • There is no vendor and no SLA; the realistic commercial support routes are IBM Red Hat OpenShift Data Foundation or an independent Ceph consultancy, both of which change the cost picture entirely.
  • Ceph is resource hungry, needing substantial memory and dedicated disks per OSD, so the hardware cost of a properly sized cluster is often underestimated.
  • Recovery and rebalancing after a disk or node failure generates heavy background input and output that can degrade application performance for hours, which surprises teams sizing for steady state.
  • Minimum viable clusters require several nodes with several disks each, so it is impractical at small scale and the entry hardware cost exceeds simpler alternatives.

Pricing, plan by plan

Borg Backup

Free
  • FreeFree
    • Deduplication
    • Compression
    • Encryption

Rook

Free
  • RookFree
    • Apache 2.0 licensed, no licence fee
    • Graduated CNCF project
    • Community support via GitHub and Slack only

Which should you pick?

Choose Borg Backup if

  • You need content-defined chunking.
  • You want to start without paying.
  • You work on Linux, Mac.
  • You also want deduplication.

Choose Rook if

  • You need ceph operator.
  • You want to start without paying.
  • You work on Linux, Kubernetes.
  • You also want block, file and object.

Questions people ask

Is Borg Backup or Rook better?
Neither clearly leads. Borg Backup starts at Free and Rook at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Borg Backup or Rook?
Borg Backup starts at Free and Rook at Free.
Does Borg Backup or Rook run on more platforms?
Borg Backup runs on Linux, Mac. Rook runs on Linux, Kubernetes.
Can I use Borg Backup for free?
Both have a free tier, so you can try either at no cost before committing.
What is Borg Backup best used for?
Borg Backup is most often used for deduplicated backups where daily full snapshots would otherwise be expensive, encrypted backup to a server you do not fully trust, since the server never sees plaintext, browsing previous versions by mounting an archive over fuse, scripted server backups with no agent or daemon to run. Of those, deduplicated backups where daily full snapshots would otherwise be expensive and encrypted backup to a server you do not fully trust, since the server never sees plaintext are not what Rook is typically brought in for.
What can Borg Backup do that Rook cannot?
Borg Backup covers Content-defined chunking, Deduplication, Compression, Authenticated encryption. Rook covers Ceph operator, Block, file and object, Erasure coding, CSI driver.

Answered from the vendors’ own pages

Borg Backup: What is the cost of BorgBackup?

BorgBackup is completely free and open source under the BSD license with no mandatory costs for the core software.

Source
Rook: Who supports it in production?

Nobody by default. IBM sells Red Hat OpenShift Data Foundation, which is supported Rook and Ceph, and independent consultancies sell Ceph support. Decide this before deployment.

Borg Backup: Are there paid services available for BorgBackup?

Yes, optional third-party services are available: BorgBase for specialized Borg repository hosting, Hetzner Storage Box with Borg support, and rsync.net cloud storage integration.

Source
Rook: Does it need Ceph knowledge?

Yes. Rook handles deployment and routine operations, but troubleshooting a degraded cluster is a Ceph skill and there is no way around it.

Borg Backup: How can I support the BorgBackup project?

BorgBackup accepts voluntary contributions through Open Collective, GitHub Sponsors, Liberapay, and PayPal, though donations are optional.

Source
Rook: Can it replace an object storage appliance?

Functionally yes, through the RADOS gateway, but you take on the operations that an appliance vendor would otherwise carry.

Share

Related pages

Other head to heads