Softwr

Cybersecurity · head to head

Grype vs Signicat

Grype logo

Grype

Cybersecurity

Vulnerability scanner for container images and filesystems

From
Free
Rated
-
Full reviewWebsite
Signicat logo

Signicat

Cybersecurity

European digital identity hub connecting national eID schemes

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; Signicat national eID scheme fees are passed through on top of Signicat's own charge, so a single-country business almost always pays less by integrating with the scheme directly.
  • They diverge on capability: Grype covers Image and filesystem scanning, Signicat covers eID scheme brokering.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Grype and Signicat actually diverge.

Attributes where Grype and Signicat differ
AttributeGrypeSignicat
Starting priceFreeOn request
Pricing modelOpen source, no licence feequote
Free tierYesNo
PlatformsLinux, macOS, Windows, DockerWeb, iOS, Android

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 Signicat

  • eID scheme brokering
  • Qualified electronic signatures
  • Document verification
  • AML screening
  • Authentication
  • Digital onboarding flows
  • eIDAS compliance

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 Signicat
  • Failing CI when a build introduces a known vulnerabilitynot Signicat
  • Auditing what is actually installed inside a third-party imagenot Signicat

Signicat

  • A lender expanding from Norway into Sweden, Denmark and the Netherlands without four separate eID integrationsnot Grype
  • An insurer needing eIDAS qualified signatures on policy documents that will hold up in a European courtnot Grype
  • A bank that wants customers to onboard with their existing national bank ID rather than photographing a passportnot Grype
  • A public sector body needing cross-border recognition of notified eID schemes under eIDASnot 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

Signicat

  • National eID scheme fees are passed through on top of Signicat's own charge, so a single-country business almost always pays less by integrating with the scheme directly.
  • Value is concentrated in Northern and Western Europe, and coverage in Southern and Eastern Europe is thinner, so a pan-European rollout still hits gaps requiring document fallback.
  • Pricing is per transaction and quoted, and because scheme rates vary by country the cost per onboarded customer differs materially between markets in ways that complicate unit economics.
  • Each eID scheme connection typically carries its own setup fee and approval process, so adding a country is a project with a lead time rather than a configuration change.
  • Availability is tied to the national schemes, meaning an outage at BankID or MitID stops your onboarding entirely and there is no vendor-side mitigation for it.

Pricing, plan by plan

Grype

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

Signicat

On request
  • Signicat Platform$undefined/year
    • Priced per transaction with national scheme fees passed through
    • Signature and verification products licensed separately
    • Setup fee per eID scheme connected

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 Signicat if

  • You need eid scheme brokering.
  • You work on Web, iOS, Android.
  • You also want qualified electronic signatures.
Signicat review

Questions people ask

Is Grype or Signicat better?
Neither clearly leads. Grype starts at Free and Signicat at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Grype or Signicat?
Grype has a free tier; the other does not. Paid plans start at Free for Grype and On request for Signicat.
Does Grype or Signicat run on more platforms?
Grype runs on Linux, macOS, Windows, Docker. Signicat runs on Web, iOS, Android.
Can I use Grype for free?
Yes. Grype has a free tier, so you can try it without paying. Signicat 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 Signicat is typically brought in for.
What can Grype do that Signicat cannot?
Grype covers Image and filesystem scanning, SBOM-driven, Wide ecosystem coverage, Pipeline friendly. Signicat covers eID scheme brokering, Qualified electronic signatures, Document verification, AML screening.

Answered from the vendors’ own pages

Grype: Is Grype free?

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

Signicat: Is this an alternative to a document verification vendor?

Only where national eID exists. In markets with a mature bank ID scheme it is better; elsewhere you fall back to document checks, which Signicat also provides.

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.

Signicat: Do we still pay the eID schemes?

Yes. Scheme fees are passed through in addition to Signicat charges. Ask for the split when comparing to a direct integration.

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.

Signicat: Are signatures legally qualified?

Signicat supports eIDAS qualified electronic signatures, which carry the highest legal standing in the EU, as well as advanced signatures.

Share

Related pages

More on Grype

More on Signicat

Keep looking

Other head to heads