Softwr

Backup · head to head

Borg Backup vs Flux

Borg Backup logo

Borg Backup

Backup

Deduplicating archiver with compression and encryption

From
Free
Rated
-
Flux logo

Flux

Cloud

GitOps continuous delivery for Kubernetes

From
Free
Rated
-

The short version

  • Each has a real cost: Borg Backup linux, macOS and BSD only; Windows is not a supported platform; Flux no user interface of its own: observing what Flux is doing means CLI or a third-party dashboard
  • They diverge on capability: Borg Backup covers Content-defined chunking, Flux covers Git as source of truth.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

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

Attributes where Borg Backup and Flux differ
AttributeBorg BackupFlux
Pricing modelfreeOpen source, no licence fee
PlatformsLinux, MacKubernetes, Linux
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 Flux

  • Git as source of truth
  • Pull-based delivery
  • Helm and Kustomize support
  • Automated image updates

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

Flux

  • Removing cluster credentials from CI systemsnot Borg Backup
  • Keeping many clusters consistent with a single declared statenot Borg Backup
  • Automatically correcting configuration drift rather than discovering it laternot 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

Flux

  • No user interface of its own: observing what Flux is doing means CLI or a third-party dashboard
  • Debugging a stuck reconciliation is harder than reading a pipeline log, because failure is asynchronous
  • Everything must be in Git, which is awkward for secrets and needs a sealed-secrets or external-secrets approach
  • GitOps is a workflow change, not just a tool, and teams used to imperative deploys find the adjustment real

Pricing, plan by plan

Borg Backup

Free
  • FreeFree
    • Deduplication
    • Compression
    • Encryption

Flux

Free
  • FluxFree
    • Full functionality
    • No usage limits
    • Community support

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 Flux if

  • You need git as source of truth.
  • You want to start without paying.
  • You work on Kubernetes, Linux.
  • You also want pull-based delivery.

Questions people ask

Is Borg Backup or Flux better?
Neither clearly leads. Borg Backup starts at Free and Flux at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Borg Backup or Flux?
Borg Backup starts at Free and Flux at Free.
Does Borg Backup or Flux run on more platforms?
Borg Backup runs on Linux, Mac. Flux runs on Kubernetes, Linux.
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 Flux is typically brought in for.
What can Borg Backup do that Flux cannot?
Borg Backup covers Content-defined chunking, Deduplication, Compression, Authenticated encryption. Flux covers Git as source of truth, Pull-based delivery, Helm and Kustomize support, Automated image updates.

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
Flux: Is Flux free?

Yes, open source and CNCF-graduated.

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
Flux: Flux or Argo CD?

Both implement GitOps. Argo CD ships a strong web UI and is often preferred for visibility; Flux is more modular and composes as controllers, which suits platform teams.

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
Flux: Why is pull-based safer?

Because the cluster reaches out to Git rather than CI reaching into the cluster. No external system needs write credentials to production.

Share

Related pages

Other head to heads