Cybersecurity · head to head
Syft vs Velero

Syft
Cybersecurity
Generates a software bill of materials from images, filesystems and archives
- From
- Free
- Free plan
- Yes

Velero
Backup
Open source backup and migration for Kubernetes cluster resources
- From
- Free
- Free plan
- Yes
The short version
- Both are free.
- Only Syft lists multi-format output; only Velero lists cluster resource backup.
- Prices and features on this page were last checked on 1 September 2026.
Where they differ
Only the attributes on which Syft and Velero actually diverge.
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 Velero
- Cluster resource backup
- Volume snapshots
- File-level backup
- Cross-cluster restore
- Backup hooks
- Scheduled backups
- Object storage targets
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 Velero
- Feeding an inventory into a vulnerability scanner rather than scanning images directlynot Velero
- Recording what shipped in a build so a future disclosure can be answered quicklynot Velero
- Public sector work where an SBOM is a contractual deliverablenot Velero
Velero
- A platform team needing namespace-level restore after an accidental deletion, with no budget for a backup productnot Syft
- Migrating workloads between Kubernetes clusters or between cloud providers using backup and restorenot Syft
- Capturing cluster configuration before a risky upgrade so the previous state can be reinstatednot Syft
- An organisation proving a Kubernetes recovery capability to an auditor before deciding whether to buy a commercial productnot 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
Velero
- There is no vendor support contract from the project itself, so a failed restore during an outage is resolved by your team reading source code and GitHub issues
- Application consistency depends on backup hooks you write and maintain, and a database backed up without a correct hook restores to a state that may not be usable
- Restore ordering across dependent resources such as custom resource definitions and operators needs manual attention, and complex applications frequently need a documented runbook rather than a single restore command
- Corporate engineering investment became uncertain after Broadcom acquired VMware, which is a real consideration for anyone building a long retention policy on the project
- Object storage egress charges apply on restore and are billed by your cloud provider, so a full cluster recovery from another region carries a cost discovered during the incident rather than during planning
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
Velero
Free- VeleroFree
- Apache 2.0 licensed
- No cluster or capacity limits
- Community support via Kubernetes Slack and GitHub
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 Velero if
- You need cluster resource backup.
- You want to start without paying.
- You work on Linux.
- You also want volume snapshots.
Questions people ask
- Is Syft or Velero better?
- Neither clearly leads. Syft starts at Free and Velero at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Syft or Velero?
- Syft starts at Free and Velero at Free.
- Does Syft or Velero run on more platforms?
- Syft runs on macOS, Linux, Windows, Self-hosted. Velero runs on Linux.
- 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 Velero is typically brought in for.
- What can Syft do that Velero cannot?
- Syft covers Multi-format output, Broad ecosystem coverage, Binary classifiers, In-toto attestations. Velero covers Cluster resource backup, Volume snapshots, File-level backup, Cross-cluster restore.
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.
Velero: Can we buy support for Velero?
Not from the project. Several commercial Kubernetes backup products package or extend it and sell support, which is the practical route to an accountable vendor.
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.
Velero: Does it back up persistent volume data?
Yes, through cloud or Container Storage Interface snapshots, or through file-level upload where snapshots are not available.
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.
Velero: What does it cost?
Nothing to licence. You pay for object storage capacity and for egress on restore, both billed by your cloud provider.
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.
Related pages
Other head to heads
- Syft vs Cosign
- Syft vs Sigstore
- Syft vs Trivy
- Syft vs Chainguard
- Syft vs Metasploit
- Syft vs Wireshark
- Syft vs Semgrep
- Syft vs Legit Security
- Syft vs OWASP ZAP
- Syft vs HashiCorp Vault
- Syft vs Bitwarden
- Syft vs Infisical
- Syft vs Teleport
- Syft vs Tenable Nessus
- Syft vs Transmit Security
- Syft vs TrustArc
- Syft vs Varonis Data Security Platform
- Syft vs VMware Carbon Black
- Syft vs Portworx Backup
- Syft vs Trilio
- Syft vs Restic
- Syft vs HYCU
- Syft vs UrBackup
- Syft vs Acronis Cyber Protect
- Syft vs BDRShield
- Syft vs Kopia
- Syft vs Veeam Kasten for Kubernetes
- Syft vs Amanda Enterprise
- Syft vs Bacula Enterprise
- Syft vs Borg Backup
- Syft vs OwnBackup
- Syft vs AOMEI Backupper
- Syft vs Apple Time Machine
- Syft vs Arcserve UDP
- Syft vs AvePoint Cloud Backup
- Syft vs Axcient x360Recover
- Velero vs Cosign
- Velero vs Sigstore
- Velero vs Trivy
- Velero vs Chainguard
- Velero vs Metasploit
- Velero vs Wireshark
- Velero vs Semgrep
- Velero vs Legit Security
- Velero vs OWASP ZAP
- Velero vs HashiCorp Vault
- Velero vs Bitwarden
- Velero vs Infisical
- Velero vs Teleport
- Velero vs Tenable Nessus
- Velero vs Transmit Security
- Velero vs TrustArc
- Velero vs Varonis Data Security Platform
- Velero vs VMware Carbon Black
- Velero vs Portworx Backup
- Velero vs Trilio
- Velero vs Restic
- Velero vs HYCU
- Velero vs UrBackup
- Velero vs Acronis Cyber Protect
- Velero vs BDRShield
- Velero vs Kopia
- Velero vs Veeam Kasten for Kubernetes
- Velero vs Amanda Enterprise
- Velero vs Bacula Enterprise
- Velero vs Borg Backup
- Velero vs OwnBackup
- Velero vs AOMEI Backupper
- Velero vs Apple Time Machine
- Velero vs Arcserve UDP
- Velero vs AvePoint Cloud Backup
- Velero vs Axcient x360Recover
