Softwr

Cybersecurity · head to head

Grype vs ThetaRay

Grype logo

Grype

Cybersecurity

Vulnerability scanner for container images and filesystems

From
Free
Rated
-
Full reviewWebsite
ThetaRay logo

ThetaRay

Cybersecurity

Unsupervised AI transaction monitoring for cross-border and correspondent banking

From
On request
Rated
-
Full reviewWebsite

The short version

  • Only Grype has a free tier, so it costs nothing to try first.
  • Each has a real cost: Grype depends on public vulnerability databases, so coverage and false positives vary by ecosystem; ThetaRay unsupervised models are harder to justify to an examiner than explicit rules, and some regulators still expect documented threshold logic, which can force you to run both systems.
  • They diverge on capability: Grype covers Image and filesystem scanning, ThetaRay covers Unsupervised detection.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Grype and ThetaRay actually diverge.

Attributes where Grype and ThetaRay differ
AttributeGrypeThetaRay
Starting priceFreeOn request
Pricing modelOpen source, no licence feequote
Free tierYesNo
PlatformsLinux, macOS, 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 Grype

  • Image and filesystem scanning
  • SBOM-driven
  • Wide ecosystem coverage
  • Pipeline friendly

Only in ThetaRay

  • Unsupervised detection
  • Cross-border focus
  • Sanctions screening
  • Alert triage
  • Customer risk scoring
  • Cloud native

What people use each for

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

Grype

  • Re-scanning stored SBOMs as new CVEs are published, without rebuilding imagesnot ThetaRay
  • Failing CI when a build introduces a known vulnerabilitynot ThetaRay
  • Auditing what is actually installed inside a third-party imagenot ThetaRay

ThetaRay

  • A correspondent bank that cannot see the ultimate originator and needs behavioural signals rather than counterparty listsnot Grype
  • A cross-border payments fintech whose rules engine produces more alerts than its compliance team can clearnot Grype
  • A bank under a regulatory consent order needing demonstrable improvement in detection within a fixed periodnot Grype
  • A payment institution entering a high-risk corridor where existing thresholds were calibrated on domestic trafficnot Grype

Where each one falls short

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

Grype

  • Depends on public vulnerability databases, so coverage and false positives vary by ecosystem
  • No triage, exception tracking or reporting UI — that is Anchore’s commercial product
  • Overlaps heavily with Trivy, and most teams pick one rather than running both

ThetaRay

  • Unsupervised models are harder to justify to an examiner than explicit rules, and some regulators still expect documented threshold logic, which can force you to run both systems.
  • The alert reduction claim depends heavily on your data, so a parallel run is essential and adds months and cost before you can decommission the incumbent.
  • Coverage is strongest in cross-border and correspondent flows; institutions whose risk is domestic retail fraud will find the fit weaker than a general-purpose monitoring platform.
  • It is a smaller vendor than the incumbents, so integration connectors into legacy core banking systems are often bespoke work rather than a supported adapter.
  • Model retraining and tuning are vendor-led, which means changing detection behaviour is a support conversation rather than something your own analysts can do that afternoon.

Pricing, plan by plan

Grype

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

ThetaRay

On request
  • ThetaRay Sonar$undefined/year
    • Priced by monitored transaction volume and number of monitored entities
    • SaaS on Azure with regional data residency options
    • Parallel run and model tuning included in onboarding

Which should you pick?

Choose Grype if

  • You need image and filesystem scanning.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Docker.
  • You also want sbom-driven.
Grype review

Choose ThetaRay if

  • You need unsupervised detection.
  • You also want cross-border focus.
ThetaRay review

Questions people ask

Is Grype or ThetaRay better?
Neither clearly leads. Grype starts at Free and ThetaRay at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Grype or ThetaRay?
Grype has a free tier; the other does not. Paid plans start at Free for Grype and On request for ThetaRay.
Does Grype or ThetaRay run on more platforms?
Grype runs on Linux, macOS, Windows, Docker. ThetaRay runs on Web.
Can I use Grype for free?
Yes. Grype has a free tier, so you can try it without paying. ThetaRay starts at On request.
What is Grype best used for?
Grype is most often used for re-scanning stored sboms as new cves are published, without rebuilding images, failing ci when a build introduces a known vulnerability, auditing what is actually installed inside a third-party image. Of those, re-scanning stored sboms as new cves are published, without rebuilding images and failing ci when a build introduces a known vulnerability are not what ThetaRay is typically brought in for.
What can Grype do that ThetaRay cannot?
Grype covers Image and filesystem scanning, SBOM-driven, Wide ecosystem coverage, Pipeline friendly. ThetaRay covers Unsupervised detection, Cross-border focus, Sanctions screening, Alert triage.

Answered from the vendors’ own pages

Grype: Is Grype free?

Yes, open source from Anchore. Anchore Enterprise is the paid platform around it.

ThetaRay: Does it replace a rules engine entirely?

Rarely on day one. Most institutions run it alongside existing rules during a parallel period, and some keep specific regulator-mandated rules permanently.

Grype: What is the difference between Grype and Syft?

Syft generates the software bill of materials; Grype matches that inventory against vulnerability data. They are designed to be used together.

ThetaRay: Where is the data processed?

SaaS runs on Microsoft Azure with regional deployment options, which is the mechanism for meeting data residency conditions in regulated markets.

Grype: Grype or Trivy?

They cover similar ground. Trivy is broader out of the box, including misconfiguration and secret scanning; Grype pairs more cleanly with an SBOM-first workflow.

ThetaRay: Is sanctions screening included?

Screening is available on the same platform but licensed as part of the commercial package rather than bundled by default. Confirm it is in your quote.

Share

Related pages

More on Grype

More on ThetaRay

Keep looking

Other head to heads