Softwr

Cybersecurity · head to head

Grype vs Hookdeck

Grype logo

Grype

Cybersecurity

Vulnerability scanner for container images and filesystems

From
Free
Free plan
Yes
Full reviewWebsite
Hookdeck logo

Hookdeck

Developer Tools

Event gateway that receives, queues, retries and replays inbound webhooks

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • Each has a real cost: Grype depends on public vulnerability databases, so coverage and false positives vary by ecosystem; Hookdeck pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.
  • They diverge on capability: Grype covers Image and filesystem scanning, Hookdeck covers Ingest and persist.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Grype and Hookdeck actually diverge.

Attributes where Grype and Hookdeck differ
AttributeGrypeHookdeck
Pricing modelOpen source, no licence feePer month by delivered event count
PlatformsLinux, macOS, Windows, DockerWeb, Linux, macOS, Windows
CategoryCybersecurityDeveloper Tools

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

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 Hookdeck

  • Ingest and persist
  • Automatic retries
  • Filters and fan-out
  • Transformations
  • Local development CLI
  • Rate limiting

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

Hookdeck

  • A payments integration where losing a Stripe event during a deploy causes an order to go unfulfillednot Grype
  • Fanning one provider webhook out to several internal services without each subscribing separatelynot Grype
  • Debugging a partner integration by replaying the exact failing payload after shipping a fixnot Grype
  • Receiving production-shaped webhooks on a developer laptop without running a public tunnelnot 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

Hookdeck

  • Pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.
  • Free-tier retention is three days, which is shorter than the time it typically takes to notice a failing integration, so the payloads needed for a replay are often already gone.
  • It becomes a single point of failure in front of every third-party integration, and an outage there means every provider webhook queues or fails at once.
  • The transformation layer runs JavaScript in a constrained environment, so anything that needs a database lookup or an external call has to happen downstream instead.
  • For a team already running Kafka or SQS the value is mostly the console and the replay UI, which is a hard cost to justify against infrastructure they already operate.

Pricing, plan by plan

Grype

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

Hookdeck

Free
  • DeveloperFree
    • Up to ten thousand events per month
    • Three-day retention
    • One user
  • Team$39/month
    • Ten thousand events included
    • Unlimited users
    • Pay as you go metering above the included events
  • Growth$499/month
    • Ten thousand events included plus metered usage
    • Thirty-day retention
    • Uptime and latency SLAs
  • Enterprise$undefined/year
    • Negotiated event volume
    • Custom retention
    • Dedicated support

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

  • You need ingest and persist.
  • You want to start without paying.
  • You work on Web, Linux, macOS, Windows.
  • You also want automatic retries.
Hookdeck review

Questions people ask

Is Grype or Hookdeck better?
Neither clearly leads. Grype starts at Free and Hookdeck at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Grype or Hookdeck?
Grype starts at Free and Hookdeck at Free.
Does Grype or Hookdeck run on more platforms?
Grype runs on Linux, macOS, Windows, Docker. Hookdeck runs on Web, Linux, macOS, Windows.
Can I use Grype for free?
Both have a free tier, so you can try either at no cost before committing.
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 Hookdeck is typically brought in for.
What can Grype do that Hookdeck cannot?
Grype covers Image and filesystem scanning, SBOM-driven, Wide ecosystem coverage, Pipeline friendly. Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations.

Answered from the vendors’ own pages

Grype: Is Grype free?

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

Hookdeck: Is there a free plan?

Yes, ten thousand events a month with three-day retention and one user.

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.

Hookdeck: How is usage counted?

By delivered events, so a single inbound webhook fanned out to three destinations counts as three.

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.

Hookdeck: Can I replay a failed webhook?

Yes, individually or in bulk from the console, with the original payload.

Hookdeck: Does it work for outbound webhooks too?

Yes, the same queueing, retry and observability applies to webhooks you send.

Share

Related pages

More on Grype

More on Hookdeck

Keep looking

Other head to heads