EU software supply-chain evidence
The supply-chain evidence for your product, current and sealed.
Sovra keeps your product's supply-chain evidence for the Cyber Resilience Act current and signed, and adds the packs regulated buyers ask for: NIS2, DORA, the AI Act and data-transfer exposure. For makers in the EU and anyone selling into it.
The video is in English.
How it works
- 1
Scan
You give Sovra the address of your GitHub or GitLab repository. The Sovra server fetches your dependency manifests and reads them.
- 2
Add intelligence
The service adds jurisdiction and provenance for each component. Every scan you run re-signs the SBOM snapshot and shows what changed since the last one.
- 3
Seal
Packs are generated when you export them. Every pack is signed with Sovra's key, and the public key travels in every pack, so tampering can be detected.
What it covers
| Regulation | What Sovra produces | Included in |
|---|---|---|
| Cyber Resilience Act | SBOM, CRA documentation pack, Procurement-response pack | Attest |
| NIS2 | Supply-chain assessment | Regulated |
| DORA | Register-of-information feed | Regulated |
| EU AI Act | Technical-documentation pack | AI Inventory, Regulated |
| GDPR transfers and US CLOUD Act | Cross-border transfer map, CLOUD Act and FISA 702 exposure pack | Data Exposure |
Sovra produces evidence; you stay responsible for your declarations and filings.
Who is behind it
Sovra is built by Informatologia, Portugal. The hosted service runs in the EU.
What the CRA asks
The manufacturer documents its components. That includes an SBOM covering at least the top-level dependencies, in a machine-readable format.
Art 13 + Annex I Part II(1)The SBOM is part of the technical documentation and is kept for 10 years or the support period, whichever is longer. It goes to market surveillance authorities on a reasoned request and does not have to be public.
Art 13(13), Recital 77The main obligations apply from 11 December 2027. Reporting obligations started in September 2026.
The manufacturer stays responsible. Sovra produces and maintains the evidence.
How an engagement runs
Three steps, from the first conversation to evidence that stays current.
- 1
A call
We talk through the product you ship and who is asking for its evidence.
- 2
Onboarding
We connect your repositories, agree the policy, install the Sovra CLI in your CI and hand over your first signed pack with a readout.
- 3
Subscription
Attest keeps the evidence current: every scan you run re-signs the SBOM snapshot, with a diff against the last one, and you export signed packs when you need them.