provenance
Sign in

RODMENA LIMITED · bill of materials as a platform

Every device you own and every component you ship, in one register

provenance is a bill-of-materials system of record. It holds your hardware estate and your software supply chain in one tamper-evident register and turns them into the evidence an ISO 27001 or Cyber Essentials assessor asks for.

The questions it exists to answer

Each of these questions involves both hardware and software. With a tool that covers only one, you finish the job by hand, often in a spreadsheet and often during an incident.

A critical CVE lands in a dependency

Which of our releases contain it, which of those are deployed right now, and which machines run them? provenance answers this in one lookup, because it deduplicates components by purl across the estate and links them to the deployment map.

Someone leaves on Friday

What hardware do they hold, including anything out for repair or recorded lost? Was each device wiped, and were their sessions ended? Offboarding happens on one page instead of in four systems.

An assessor asks what you held in March

The register can be rebuilt from its event log for any past date. You can answer “what did we own, and who had it” without restoring a backup.

Prove this SBOM is the one CI produced

We keep the published bytes with their digest. The document you hand a regulator years later is the artefact your build emitted.

One register, two halves

Most products cover either hardware or software. Asset-management tools handle the hardware and software-composition tools handle the dependencies, and you are left to join the two. That join tells you whether a vulnerability needs fixing tonight or can wait for the next release.

Software bill of materials

CycloneDX ingest per release, components deduplicated by purl, a deployment map naming the environment and the machine, vulnerability findings ranked by real exposure, VEX positions a human approves, and licence policy with recorded verdicts.

Hardware asset register

Every device with its full lifecycle, the custodian who holds it, its disk-encryption evidence and the register as it stood on any past date. Before anything leaves the books, disposal needs a certificate and a human approval.

Built to be checked

A compliance record is only worth what an auditor can verify. We built four things into provenance so that its record can be checked.

  • A hash-chained audit log you can recompute. Every change is appended to the log with who made it, and linked to the previous entry by its digest. The service publishes the canonical payload, so you can verify the chain with your own tools.
  • A scanner that has to prove itself. A broken scanner can return a clean result for an estate that is not clean. provenance only uses scanner results after the scanner has found a set of vulnerabilities we planted, and the dashboard shows a warning until it has.
  • Machines record and propose, and a person approves. No API key can ever hold the scopes for suppressing a critical finding, disposing of an asset or accounting for a break in the audit chain, whoever creates it, an administrator included.
  • Evidence that states its own limits. For every control in an exported pack, provenance states what the register proves and what it does not, so an assessor does not find gaps that the pack failed to mention.

For systems as well as people

Every screen here sits on an HTTP API that CI, a scheduler or an agent can drive directly. Credentials are scoped API keys that must expire within a year. Each key is shown once and stored as a digest. The API is documented for machines at /llms.txt, and a credential can ask what it may do before it tries.

Common questions

What is the difference between a BOM, an SBOM and an HBOM?

A bill of materials lists what something is made of. A software bill of materials (SBOM) lists the libraries, versions and licences inside a release. A hardware bill of materials (HBOM) lists the parts inside a device, the companies that made them and where; vendors supply them to buyers. provenance keeps your SBOMs and your hardware asset register (the laptops, servers and network kit you own, and who holds each one) in one register, because the question that matters in an incident crosses the two. When a library is vulnerable, you need to know which releases ship it and which machines are running those releases now.

Which SBOM formats can I publish?

Today you publish CycloneDX JSON, one document per release. We keep the exact bytes you publish and record their SHA-256 digest. Later, you can prove that the document you download is the one your build produced. SPDX ingest is on the roadmap.

Does it scan for vulnerabilities, or do I bring my own findings?

Yes. provenance scans any release that has a published SBOM against several advisory sources, on demand or on a nightly schedule. Findings are ranked by whether the affected release is deployed.

How is this different from a vulnerability scanner?

A scanner reports what is wrong today. A register records what you had, what you shipped and what you decided, for any past date, in a form an auditor can check. provenance keeps the deployment map, licence positions, disposal certificates and a hash-chained log of every change, so you can answer questions about past events that a scanner cannot.

Can I trust the audit trail if I do not trust you?

Yes. Each entry stores the digest of the previous entry, and the service publishes the exact fields the digest covers along with the whole log in genesis order. You can recompute the chain yourself without relying on us. Breaks are never repaired, only annotated.

What does it cost?

You can try provenance free in a small personal workspace. The pricing page lists its limits and the features it leaves out. Team and Enterprise plans are scoped with our sales team against the estate you run. To start, email sales@rodmena.co.uk with its size.

How does this work for a company?

Enterprise customers get their own workspace, operated by RODMENA and sized to their estate, with membership, roles and invitations managed inside it. Tell us about your estate and we will scope it with you. The security page describes how workspaces are separated today and how that will change.

Start with your own estate

Free for personal and evaluation use. For an enterprise deployment, tell us the size of the estate and what you need to evidence, and we will size it with you.