Softwr

Cybersecurity · head to head

Syft vs Unit21

Syft logo

Syft

Cybersecurity

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

From
Free
Rated
-
Full reviewWebsite
Unit21 logo

Unit21

Cybersecurity

No-code fraud and AML risk operations platform for fintechs and neobanks

From
On request
Rated
-
Full reviewWebsite

The short version

  • Only Syft has a free tier, so it costs nothing to try first.
  • Each has a real cost: 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.; Unit21 it is built for fintech scale rather than card issuer scale, so organisations reaching very high transaction volumes generally re-evaluate against heavier platforms and face a migration.
  • They diverge on capability: Syft covers Multi-format output, Unit21 covers No-code rule builder.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Syft and Unit21 actually diverge.

Attributes where Syft and Unit21 differ
AttributeSyftUnit21
Starting priceFreeOn request
Pricing modelOpen source, no licence feequote
Free tierYesNo
PlatformsmacOS, Linux, Windows, DockerWeb

Identical on both: user rating (Not yet rated), category (Cybersecurity).

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 Unit21

  • No-code rule builder
  • Case management
  • SAR filing
  • Backtesting
  • Identity and device signals
  • Data ingestion API

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 Unit21
  • Feeding an inventory into a vulnerability scanner rather than scanning images directlynot Unit21
  • Recording what shipped in a build so a future disclosure can be answered quicklynot Unit21
  • Public sector work where an SBOM is a contractual deliverablenot Unit21

Unit21

  • A neobank whose sponsor bank requires a documented monitoring programme before it will keep the BIN sponsorshipnot Syft
  • A crypto exchange needing SAR filing and case management without building an internal compliance engineering teamnot Syft
  • A payments startup where the fraud lead needs to ship a new rule the same day a new attack pattern appearsnot Syft
  • A lender consolidating fraud alerts from three point tools into one investigator queue with a single audit trailnot 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.

Unit21

  • It is built for fintech scale rather than card issuer scale, so organisations reaching very high transaction volumes generally re-evaluate against heavier platforms and face a migration.
  • No-code rule authoring shifts power to the risk team, which is the point, but without governance it produces rule sprawl that nobody can explain to an examiner two years later.
  • Detection quality depends on the signals you feed it, so a thin integration produces thin results and the platform cannot compensate with proprietary consortium data the way larger vendors do.
  • Pricing is quoted by volume with an annual commitment, so a fintech whose growth stalls pays for headroom it did not use.
  • SAR filing coverage is oriented to United States FinCEN reporting, so firms filing in the United Kingdom, European Union or Asia handle those submissions outside the tool.

Pricing, plan by plan

Syft

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

Unit21

On request
  • Unit21 Platform$undefined/year
    • Priced by monitored volume and modules, annual contract
    • Fraud, AML and case management packaged separately
    • Implementation and historical data backfill quoted with the subscription

Which should you pick?

Choose Syft if

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

Choose Unit21 if

  • You need no-code rule builder.
  • You also want case management.
Unit21 review

Questions people ask

Is Syft or Unit21 better?
Neither clearly leads. Syft starts at Free and Unit21 at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Syft or Unit21?
Syft has a free tier; the other does not. Paid plans start at Free for Syft and On request for Unit21.
Does Syft or Unit21 run on more platforms?
Syft runs on macOS, Linux, Windows, Docker. Unit21 runs on Web.
Can I use Syft for free?
Yes. Syft has a free tier, so you can try it without paying. Unit21 starts at On request.
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 Unit21 is typically brought in for.
What can Syft do that Unit21 cannot?
Syft covers Multi-format output, Broad ecosystem coverage, Binary classifiers, In-toto attestations. Unit21 covers No-code rule builder, Case management, SAR filing, Backtesting.

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.

Unit21: Do we need engineers to run it?

Only for the initial data integration. After that the design intent is that risk and compliance staff author and deploy rules themselves.

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.

Unit21: Does it file SARs?

Yes, it generates and electronically files suspicious activity reports to FinCEN. Non-US regimes are not covered to the same depth.

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.

Unit21: Can we test a rule before it goes live?

Yes. Backtesting against historical data to see projected alert volume is one of the more useful parts of the product, because alert volume is the real cost.

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

More on Syft

More on Unit21

Keep looking

Other head to heads