For manufacturers selling connected products in the EU

Know what’s inside everything you ship. Prove it.

Upload the software bill of materials (SBOM) of your product. Venlark checks every component against public vulnerability databases and gives you a clear report for the EU Cyber Resilience Act. Your product files never leave your computer.

  • Only the SBOM is uploaded
  • CycloneDX and SPDX (JSON)
  • Checked by Grype, Trivy and OSV-Scanner

11 Sept 2026 In force

Reporting applies. Actively exploited vulnerabilities must be reported to the authorities.

11 Dec 2027

Every requirement applies, including documented software components for each product.

—

days until
full application

§ 01The problem

A list of components is not evidence.

Customers, auditors and market surveillance authorities will ask how you know what is in a product. The answer has to hold up for every version you have shipped.

  1. 01

    Hand-made lists go stale

    A spreadsheet of components drifts away from the build the moment a supplier updates a library.

  2. 02

    Scanners quietly guess

    One tool misses what another finds, and versions it cannot read are often filled in rather than flagged.

  3. 03

    Nobody can show their work

    When a customer asks why a vulnerability does or does not apply, there is no trail to point at.

§ 02What you upload

One file. Only the SBOM.

CycloneDX JSON

Versions 1.4 to 1.6 are also checked against the official schema. Up to 64 MB.

SPDX JSON

Versions 2.2 and 2.3 are also checked against the official schema. Up to 64 MB.

No SBOM yet?

We are building desktop apps for Mac and Windows that make the SBOM for you, on your own computer.

Coming soon

Apps

How we handle your address: Privacy notice

Firmware images, app packages, archives and source code are refused before they are stored. CycloneDX XML and SPDX tag-value are not supported yet.

§ 03How it works

From an SBOM to a clear answer.

  1. Step 01

    Make an SBOM on your computer

    Most build tools can write one, for example Syft, Trivy or cdxgen. Our desktop apps for Mac and Windows will make it for you; they are coming soon.

  2. Step 02

    Upload only the SBOM

    CycloneDX JSON or SPDX JSON. Anything else is refused before it is stored, so your firmware, apps and source code never reach us.

  3. Step 03

    Match known vulnerabilities

    Grype, Trivy and OSV-Scanner check every component against public vulnerability databases. The database date is recorded with every result.

  4. Step 04

    Get a clear report

    A one-page summary with a red, amber or green status, the full list of findings, and machine-readable files. It is produced automatically and says so.

  5. Step 05

    Hear about new problems

    When new vulnerabilities are published, your SBOMs are checked again and you get an alert, without uploading anything new.

§ 04Evidence

Every line can be defended.

Finding · sample

openssl 1.1.1k

CVE-2023-0286 · High
Listed in SBOM
pkg:generic/openssl@1.1.1k
Matched by
GrypeTrivyOSV-Scanner
Confidence
High · package URL and version in the SBOM, 3 of 3 matchers agree
Review
Not reviewed · automatic report
Data
Vulnerability databases of 10 Nov 2026
Fix
Upgrade to 1.1.1t or later
Unknown, explained

libvendor unknown

The SBOM gives no version. Reported as unknown, with the reason, instead of a guessed version that would produce false matches.

One status for the whole product

  • Red. A vulnerability on the CISA list of actively exploited vulnerabilities. Check it first.
  • Amber. A vulnerability rated critical or high, or a part of the check that could not run.
  • Green. Neither. Lower-rated findings may still be listed.

One status language

Read any result at a glance, in colour or in black and white.

Every status has a mark, a word and a colour. The same scale is used in the app, the report and the export.

Severity

  • Critical
  • High
  • Medium
  • Low

Confidence

  • High
  • Medium
  • Low
  • Unknown

Review

  • Awaiting review
  • Reviewed
  • Disputed

§ 05The report

Written for the people who decide.

Business owners get a plain-language report: what needs action, what to ask suppliers, and what is fine. Engineers get the machine-readable findings for the same SBOM.

  • Clearly labelled: automatic, not reviewed by a person
  • Every finding links to its source record
  • Mark findings that do not apply, and the status updates

§ 06Pricing

Start free. Pay per product.

Example prices, not final. Plans and prices will be confirmed before launch.

  • Free check

    Example

    See where a product stands.

    €0one SBOM

    • Upload one CycloneDX or SPDX SBOM
    • One-page report with a red, amber or green status
    • The most urgent vulnerabilities named
    Get started
  • Full report

    Example

    Everything you need for one release.

    €49per product version

    • Everything in the free check
    • Full report: top issues, every finding, every component
    • CycloneDX VEX and CSV exports
    • Mark findings that do not apply
    Get started
  • Monitoring

    Example

    Stay informed after you ship.

    €19per product, per month

    • Everything in the full report
    • Re-checks when new vulnerabilities are published
    • Alerts in the app
    • Compare product versions
    • CRA paperwork drafts, exported as PDF or DOCX
    Get started

The desktop apps for Mac and Windows, which make the SBOM for you, are coming soon. Reports are produced automatically and are not legal advice.

§ 07Privacy and security

Your product files never leave your computer.

SBOM only

Anything that is not a CycloneDX or SPDX file is refused before it is stored.

Isolated checks

The workers that read your SBOM cannot reach the internet.

Pinned tools

Exact versions and SHA-256 checksums, checked at build and every time a worker starts.

Full audit log

Every sign-in and change is recorded, so you can show who did what and when.

Vulnerability matching by open tools, pinned to exact versions

  • Grype 0.121.3
  • Trivy 0.76.2
  • OSV-Scanner 2.7.1

§ 08Questions

Before you ask.

No. You upload only the software bill of materials (SBOM), a list of the software components in your product. Every other file is refused before it is stored, so firmware, apps and source code never reach us.

Ship with proof.