Softwr

Backup · head to head

Borg Backup vs CapRover

Borg Backup logo

Borg Backup

Backup

Deduplicating archiver with compression and encryption

From
Free
Rated
-
Full reviewWebsite
CapRover logo

CapRover

Cloud

Free self-hosted platform built on Docker Swarm with a dashboard and automatic certificates

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Borg Backup linux, macOS and BSD only; Windows is not a supported platform; CapRover since June 2026 one pseudonymous account wrote 97 of roughly 100 commits and the next human contributor wrote one, so there is no identifiable person or company to contract with, escalate to or hold responsible.
  • They diverge on capability: Borg Backup covers Content-defined chunking, CapRover covers One-click applications.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

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

Attributes where Borg Backup and CapRover differ
AttributeBorg BackupCapRover
Pricing modelfreeOpen source, no licence fee
PlatformsLinux, MacWeb, Linux, Docker, CLI, Self-hosted
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 CapRover

  • One-click applications
  • Automatic certificates
  • Web dashboard
  • Multiple deploy paths
  • Docker Swarm clustering
  • Custom nginx configuration

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 CapRover
  • Encrypted backup to a server you do not fully trust, since the server never sees plaintextnot CapRover
  • Browsing previous versions by mounting an archive over FUSEnot CapRover
  • Scripted server backups with no agent or daemon to runnot CapRover

CapRover

  • Running a personal server or homelab with several applications behind automatic certificatesnot Borg Backup
  • A two person team that wants a dashboard rather than a terminal for deployments on one boxnot Borg Backup
  • Standing up one-click databases and internal tools without writing Compose filesnot Borg Backup
  • Hosting client demos cheaply where downtime is inconvenient rather than expensivenot 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

CapRover

  • Since June 2026 one pseudonymous account wrote 97 of roughly 100 commits and the next human contributor wrote one, so there is no identifiable person or company to contract with, escalate to or hold responsible.
  • Donations over the last twelve months totalled 285 US dollars and there is no commercial tier, so no paid support exists at any price and no maintenance commitment is funded.
  • The LICENSE file is Apache 2.0 with a superseding appendix that bans redistributing a paid version and refers to paid features that do not yet exist, and GitHub cannot classify it, so the terms already anticipate a commercial change of direction.
  • Releases arrive in bursts with an eleven month gap between September 2023 and August 2024 and two further gaps of about six months since, so there is no basis for assuming a security fix will land promptly.
  • The backup feature is documented as experimental, covers only the CapRover configuration directory and explicitly excludes persistent volumes and container images, so every database has to be dumped separately with its container stopped.

Pricing, plan by plan

Borg Backup

Free
  • FreeFree
    • Deduplication
    • Compression
    • Encryption

CapRover

Free
  • CapRoverFree
    • No paid tier and no hosted offering
    • Unlimited applications, servers and users
    • Community support through Slack and GitHub

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.
Borg Backup review

Choose CapRover if

  • You need one-click applications.
  • You want to start without paying.
  • You work on Web, Linux, Docker, CLI, Self-hosted.
  • You also want automatic certificates.
CapRover review

Questions people ask

Is Borg Backup or CapRover better?
Neither clearly leads. Borg Backup starts at Free and CapRover at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Borg Backup or CapRover?
Borg Backup starts at Free and CapRover at Free.
Does Borg Backup or CapRover run on more platforms?
Borg Backup runs on Linux, Mac. CapRover runs on Web, Linux, Docker, CLI, Self-hosted.
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 CapRover is typically brought in for.
What can Borg Backup do that CapRover cannot?
Borg Backup covers Content-defined chunking, Deduplication, Compression, Authenticated encryption. CapRover covers One-click applications, Automatic certificates, Web dashboard, Multiple deploy paths.

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
CapRover: Does CapRover cost anything?

No. There is no paid tier and no hosted version. The only income is donations, which came to 285 US dollars over the last twelve months.

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
CapRover: Is the licence really Apache 2.0?

Not quite. The LICENSE file is Apache 2.0 plus an appendix that supersedes it in case of conflict, forbidding modification of paid features and redistribution of a paid version. GitHub does not recognise the result as a standard licence.

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
CapRover: Does the backup feature protect my databases?

No. It backs up the CapRover configuration directory only and explicitly excludes persistent directories and container images. You have to dump each database yourself with the container stopped.

CapRover: Can I move off Docker Swarm later?

Not without rebuilding. CapRover is architecturally tied to Swarm, so outgrowing it means migrating applications to a different platform rather than switching a scheduler.

Share

Related pages

More on Borg Backup

More on CapRover

Keep looking

Other head to heads