PDE catalogue
Product identity, batches, markets, importers, support end date.
Product
CRA operations, not a slide deck.
Crado AI is where a manufacturer keeps evidence: what you make, what it is made of, which gaps you close, and how you notify an actively exploited vulnerability.
How work looks in the system
- 01
Register products
A PDE catalogue with version, market and the date you made it available.
- 02
Pin the requirements
Risk assessment and Annex I on each product, not in a side spreadsheet.
- 03
Build the SBOM
Own and third-party components, with due diligence on suppliers.
- 04
Keep the support period
Vulnerabilities, updates and Article 14 notifications on a 24h / 72h clock.
- 05
Close the file and CE
Documentation, EU declaration, mark. Then post-market surveillance.
Modules
In-scope check
The regulation applied per product, not once for the whole company.
Annex I
Product properties and vulnerability handling, tied to risk.
SBOM
Components, versions, source, links to CVE.
Article 14
Early warning, full notification, final report.
Technical file and CE
What an authority can demand before the product is placed on the market.
The Article 14 clock
-
24h
Early warning from the moment you know of an actively exploited vulnerability or a severe incident.
-
72h
Full notification. One channel (SRP), to the CSIRT of the main establishment, and to ENISA.
-
14 days / 1 month
Final report: 14 days after a fix for a vulnerability, one month after the 72h notice for an incident.
Deployed at your site
Installed on the customer infrastructure. Backups, identity and network stay in your standard. There is no SaaS plan.
- App and database on your infrastructure (VM or Kubernetes).
- Identity against your IdP (OIDC / SAML).
- Backups and network stay in your standard.
- No tenant in our cloud and no SaaS plan.
Talk through your PDE catalogue
Twenty minutes. No public price list. A quote after the call, for an on-premise deployment.
Book a call