Softwr

Cybersecurity · head to head

Syft vs UrBackup

Syft logo

Syft

Cybersecurity

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

From
Free
Free plan
Yes
UrBackup logo

UrBackup

Backup

Open source client server backup doing both file and whole disk image backups of Windows machines

From
Free
Free plan
Yes

The short version

  • Both are free.
  • Only Syft lists multi-format output; only UrBackup lists windows image backups.
  • Prices and features on this page were last checked on 31 August 2026.

Where they differ

Only the attributes on which Syft and UrBackup actually diverge.

Attributes where Syft and UrBackup differ
AttributeSyftUrBackup
PlatformsmacOS, Linux, Windows, Self-hostedLinux, Windows, macOS
CategoryCybersecurityBackup

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes).

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 Syft

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

Only in UrBackup

  • Windows image backups
  • File backups
  • Web interface
  • Client discovery
  • Internet mode
  • Filesystem deduplication

What people use each for

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

Syft

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

UrBackup

  • A small office with Windows workstations that needs bare metal restore without per seat licensingnot Syft
  • Schools and labs where machines are re-imaged often and a known good image must be recoverablenot Syft
  • Backing up a mixed fleet to one server on premises with a web interface non specialists can usenot Syft
  • Replacing an expiring commercial endpoint backup licence where the budget is the constraintnot Syft

Where each one falls short

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

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

UrBackup

  • Backups are stored on the server without encryption at rest by default, so the backup server holds a readable copy of every machine it protects and becomes the highest value target on the network
  • Deduplication relies on filesystem features such as hard links, btrfs or ZFS, so a server built on the wrong filesystem silently consumes far more space and the fix is a rebuild rather than a setting
  • There is no native object storage target, so offsite copies mean replicating the server storage with another tool rather than backing up to a bucket directly
  • Restoring a full Windows image requires booting a restore environment, which is a manual, on site procedure that needs to be rehearsed before the day it is needed
  • A single server holds everything and there is no built in clustering, so its own failure removes every recovery point at once unless you have separately solved replication

Pricing, plan by plan

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

UrBackup

Free
  • UrBackupFree
    • Full functionality, unlimited clients
    • File and image backups
    • Web administration interface

Which should you pick?

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.

Choose UrBackup if

  • You need windows image backups.
  • You want to start without paying.
  • You work on Linux, Windows, macOS.
  • You also want file backups.

Questions people ask

Is Syft or UrBackup better?
Neither clearly leads. Syft starts at Free and UrBackup at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Syft or UrBackup?
Syft starts at Free and UrBackup at Free.
Does Syft or UrBackup run on more platforms?
Syft runs on macOS, Linux, Windows, Self-hosted. UrBackup runs on Linux, Windows, macOS.
Can I use Syft for free?
Both have a free tier, so you can try either at no cost before committing.
What is Syft best used for?
Syft is most often used for producing a bill of materials for a customer or regulator that requires one, feeding an inventory into a vulnerability scanner rather than scanning images directly, recording what shipped in a build so a future disclosure can be answered quickly, public sector work where an sbom is a contractual deliverable. Of those, producing a bill of materials for a customer or regulator that requires one and feeding an inventory into a vulnerability scanner rather than scanning images directly are not what UrBackup is typically brought in for.
What can Syft do that UrBackup cannot?
Syft covers Multi-format output, Broad ecosystem coverage, Binary classifiers, In-toto attestations. UrBackup covers Windows image backups, File backups, Web interface, Client discovery.

Answered from the vendors’ own pages

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.

UrBackup: Does it back up Linux servers as well?

File backups yes, image backups no. The image path is Windows only through volume shadow copy.

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.

UrBackup: Is the data encrypted?

Transport can be encrypted, and there is optional client side file encryption, but the default server storage is not encrypted at rest. Use full disk encryption on the server.

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.

UrBackup: Can I back up to Amazon S3?

Not directly. The server writes to local or mounted storage, so cloud copies are made by replicating that storage separately.

Syft: What does Anchore Enterprise cost?

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

UrBackup: How many clients can one server handle?

Dozens is routine on decent hardware. The limit is usually storage input and output during overlapping backup windows rather than client count.

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