Our AI agents propose a class for every product and map the essential requirements. They keep the SBOM and the reporting process current. Product, security and legal teams make the decisions.
Example data
Tick what you can prove today. Your result stays in your browser and is never sent.
The foundation is missing
Book a demoStructure there, evidence not yet
See a gap auditReady for the conformity assessment
Book a demoPure SaaS that does not support a product's function is outside the CRA. Cloud services such as SaaS fall under the NIS2 Directive, depending on company size. Check NIS2 for your company. Explore NIS2 →
Medical devices, in vitro diagnostics and type-approved vehicles are outside the CRA.
You can assess conformity yourself through internal control.
If you apply a harmonised standard, common specifications or a suitable certification scheme in full, internal control stays possible.
You need a notified body, through EU-type examination or full quality assurance.
You need a notified body or a certification scheme at assurance level "substantial".
The Commission can require a European certification scheme. Until then the class II route applies.
Since 11 September 2026 you have had to report actively exploited vulnerabilities and severe incidents, within 24 hours, within 72 hours and with a final report. This applies to products already on the market too.
The class follows the core functionality of the product. We check with you whether harmonised standards for your product category are already in the Official Journal. Open-source software in Annex III categories can use internal control if its technical documentation is public. This helper is not legal advice.
Since 11 September 2026 manufacturers have had to report actively exploited vulnerabilities and severe incidents. From 11 December 2027 the CRA applies in full. Whatever goes on the market then needs technical documentation, a conformity assessment and CE marking.
Art. 14 applies to every product, including those placed on the market before December 2027. The early warning is due within 24 hours.
You can only self-assess an important class I product if you apply a harmonised standard, common specifications or a certification scheme in full. Otherwise you need a notified body. The same goes for class II, unless you use a European certification scheme.
It is usually at least five years. Each security update stays available for at least ten years, or until the support period ends if that is later. Set it without engineering and you promise work nobody planned.
You need an SBOM in a commonly used, machine-readable format. When you find a vulnerability in a component, you report it to that component's maintainer.
Our AI agents propose classes and map the requirements. They keep track of every release. Product and security teams make the decisions.
GetTeddy builds the product inventory and proposes a class per product, with reasons from Annex III or IV. Your product team and Legal confirm it.
GetTeddy checks every product against Annex I. Controls from your ISO 27001 programme, such as secure development and incident handling, count where they apply.
The Evidence Agent collects SBOMs from connected repositories and watches vulnerabilities in the components you ship.
The Policy Agent drafts the Art. 14 process with roles, criteria and templates. Everyone knows who decides and who reports through the single reporting platform.
Risk assessment, Annex I mapping, SBOM and support period together form the technical documentation for your conformity assessment. Gap audits run every week, so it stays right with every release.
Product management, the firmware team and sales ask the same questions in their own words. GetTeddy answers from the inventory, SBOMs and evidence. New questions reach the right person with a draft.
Ask GetTeddyIs our gateway class I? Which support period did we promise? Every answer links to its source.
Agents do the groundworkThey propose classes and map Annex I. They also collect SBOMs and keep the reporting templates ready.
Our team backs you upA compliance engineer helps you prepare for the conformity assessment.
Read next CRA · NIS2 · ISO 27001 · SaaS · Automotive suppliers and TISAX®
The Art. 14 reporting duty has applied to them since 11 September 2026. The other product rules apply to products placed on the market before 11 December 2027 only after a substantial modification.
Actively exploited vulnerabilities and severe incidents. The early warning is due in 24 hours, the notification in 72 hours. The final report follows 14 days after a fix is available, or one month after the notification for incidents. Reports go through the single reporting platform to the coordinating CSIRT and ENISA.
It depends on the class. You assess default products yourself. Class I only if you apply a harmonised standard, common specifications or a certification scheme in full. Otherwise you need a notified body. Class II needs a notified body or a certification scheme.
Remote data processing without which the product cannot perform a function is part of the product. Pure SaaS that does not support a product's function is outside the CRA. Cloud services such as SaaS fall under the NIS2 Directive, depending on company size. GetTeddy keeps device, app and backend in the same product inventory.
For breaches of Annex I, Art. 13 or Art. 14, up to €15 million or 2.5% of worldwide annual turnover, whichever is higher. Micro and small enterprises are not fined for missing the 24-hour early warning.
In the region you choose: EU, Germany or the US. Your data is kept separate from other customers and encrypted. GetTeddy uses read-only access by default and never trains AI models on your data.
| Typical | With GetTeddy | |
|---|---|---|
| Classification | Legal review per product | Proposal with reasons, confirmed by your team |
| Requirements | Generic checklists | Mapped to your controls per product |
| SBOMs | Collected by hand | Per release from your repositories |
| Reporting | Ownership settled during the emergency | Process and templates with named roles |
| Ongoing | Yearly review | Gap audits every week |
In 30 minutes we show you how it works on one of your products.