Softwr

Backup · head to head

Borg Backup vs Syft

Borg Backup logo

Borg Backup

Backup

Deduplicating archiver with compression and encryption

From
Free
Free plan
Yes
Syft logo

Syft

Cybersecurity

Generates a software bill of materials from images, filesystems and archives

From
Free
Free plan
Yes

The short version

  • Borg Backup is a deduplicating backup program.
  • Both are free.
  • Only Borg Backup lists content-defined chunking; only Syft lists multi-format output.
  • Where Borg Backup falls short: linux, macOS and BSD only; Windows is not a supported platform.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

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

Attributes where Borg Backup and Syft differ
AttributeBorg BackupSyft
Pricing modelFreeOpen source, no licence fee
PlatformsLinux, macOSmacOS, Linux, Windows, Self-hosted
CategoryBackupCybersecurity

Identical on both: starting price (Free), free tier (Yes).

Not yet recorded: founded for Syft.

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 Syft

  • Multi-format output
  • Broad ecosystem coverage
  • Binary classifiers
  • In-toto attestations
  • Library and CLI
  • Pairs with Grype

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

Syft

  • Producing a bill of materials for a customer or regulator that requires onenot Borg Backup
  • Feeding an inventory into a vulnerability scanner rather than scanning images directlynot Borg Backup
  • Recording what shipped in a build so a future disclosure can be answered quicklynot Borg Backup
  • Public sector work where an SBOM is a contractual deliverablenot 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

Syft

  • Lockfile parsing can drop packages silently. An open issue filed in August 2026 reports the yarn v1 cataloguer returning 118 of 745 packages with no error raised, which means a complete bill of materials and an 84 percent incomplete one look identical to the caller
  • Fidelity varies sharply by ecosystem. Conan for C and C++, Haskell and Terraform get cataloguer support with no licence data, no dependency relationships and no file ownership, so a C and C++ shop gets the least from it
  • Binary classification yields no licence or dependency metadata, and vendored or statically linked code is exactly where supply chain risk hides, so the blind spot and the risk overlap
  • Incorrect CPE values and CPE collisions are recorded as open issues, and since Grype matches on CPE and PURL, an inventory error becomes a false negative in the security report downstream
  • An inventory is not a risk assessment. Even a perfect bill of materials says a vulnerable version is present, never that the vulnerable function is called, and the triage burden lands entirely on the reader

Pricing, plan by plan

Borg Backup

Free
  • FreeFree
    • Deduplication
    • Compression
    • Encryption

Syft

Free
  • SyftFree
    • Apache-2.0
    • No usage limits
    • Community support
  • Anchore EnterpriseOn request
    • Policy enforcement and reporting
    • Federal and commercial tiers
    • Pricing not published, quoted on request

Which should you pick?

Choose Borg Backup if

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

Choose Syft if

  • You need multi-format output.
  • You want to start without paying.
  • You work on macOS, Linux, Windows, Self-hosted.
  • You also want broad ecosystem coverage.

Questions people ask

Is Borg Backup or Syft better?
Neither clearly leads. Borg Backup starts at Free and Syft at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Borg Backup or Syft?
Borg Backup starts at Free and Syft at Free.
Does Borg Backup or Syft run on more platforms?
Borg Backup runs on Linux, macOS. Syft runs on macOS, Linux, Windows, 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 Syft is typically brought in for.
What can Borg Backup do that Syft cannot?
Borg Backup covers Content-defined chunking, Deduplication, Compression, Authenticated encryption. Syft covers Multi-format output, Broad ecosystem coverage, Binary classifiers, In-toto attestations.

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
Syft: Does Syft find vulnerabilities?

No. It produces an inventory. Grype, from the same company, matches that inventory against vulnerability feeds. They are separate tools and the distinction is frequently lost.

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
Syft: Does anything in the Anchore stack do reachability analysis?

No. Neither Syft, Grype nor the commercial Anchore platform performs call graph or reachability analysis, so none of them tells you whether a vulnerable code path is actually invoked.

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
Syft: Is it a CNCF or OpenSSF project?

No. It is single-vendor open source owned by Anchore, with no foundation governance. That is a different licence risk profile from Sigstore.

Syft: What does Anchore Enterprise cost?

Not published. The pricing page is contact-sales only, with named but unpriced commercial and federal tiers.

Syft: How do I know my SBOM is complete?

You largely cannot, which is the honest answer. Silent partial parsing is a known open defect, so a bill of materials used for compliance should be spot-checked against a known dependency list.

Share

Related pages

Other head to heads