Agentic compliance for connected product makers

Connected products that meet the Cyber Resilience Act, release after release

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.

  • Class and conformity route per product
  • Art. 14 reporting process with named owners
  • Hosting in the EU, Germany or the US

Example data

Obligations check

How ready your products are for the CRA

Tick what you can prove today. Your result stays in your browser and is never sent.

Products and classes
Development and vulnerabilities
Reporting
Conformity
Your progress0%

The foundation is missing

Book a demo
Which class and conformity route apply to your product
Do you place the product on the EU market, and can it connect to a device or network?

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.

What connected product makers deal with

Reporting applies today, CE marking is coming

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.

01Reporting covers products in the field

Art. 14 applies to every product, including those placed on the market before December 2027. The early warning is due within 24 hours.

02The class sets the conformity route

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.

03The support period is a promise

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.

04Third-party components are your responsibility

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.

How it works

Products you can place on the market

Our AI agents propose classes and map the requirements. They keep track of every release. Product and security teams make the decisions.

01 Gap Audit Agent

Classify every product with reasons

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.

Key factsAnnex III and IV
Class I includes operating systems, routers, modems and switches
Class II includes firewalls, hypervisors and container runtimes
Critical includes smart meter gateways and smartcards
02 Gap Audit Agent

Check the essential requirements per product

GetTeddy checks every product against Annex I. Controls from your ISO 27001 programme, such as secure development and incident handling, count where they apply.

Key factsArt. 13, Annex I
Cybersecurity risk assessment per product
Annex I Part I for the product, Part II for vulnerability handling
03 Evidence Agent

SBOM and vulnerabilities from your repositories

The Evidence Agent collects SBOMs from connected repositories and watches vulnerabilities in the components you ship.

Key factsAnnex I Part II
SBOM at least for top-level dependencies
Security updates free of charge during the support period
Report component vulnerabilities to their maintainer
04 Policy Agent

A reporting process with owners

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.

Key factsArt. 14
Early warning in 24 hours, notification in 72 hours
Final report 14 days after a fix is available, for incidents one month after the notification
Affected users are informed
05 Certification Agent

Technical documentation from your evidence

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.

Key factsConformity
Technical documentation per Annex VII
EU declaration of conformity and CE marking
Deadlines

The dates that drive your product roadmap

10 Dec 2024CRA in forceRegulation (EU) 2024/2847 enters into force.
1 Aug 2025Radio equipmentCybersecurity requirements for radio equipment under the Radio Equipment Directive apply.
11 Jun 2026Notified bodiesThe rules for conformity assessment bodies apply.
11 Sep 2026Reporting appliesArt. 14, also for products already on the market.
11 Dec 2027Full applicationEssential requirements, conformity assessment and CE marking.
Per productSupport periodUsually at least five years.
Per updateAvailabilityEach security update for at least ten years or until the support period ends.
Never alone

Product, security and sales ask, and GetTeddy answers with a source

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.

1

Ask GetTeddyIs our gateway class I? Which support period did we promise? Every answer links to its source.

2

Agents do the groundworkThey propose classes and map Annex I. They also collect SBOMs and keep the reporting templates ready.

3

Our team backs you upA compliance engineer helps you prepare for the conformity assessment.

TeddyYour company · Example data
A customer asks for our support period for our gateway.
The gateway has a support period of 5 years from its market date.
  • Support period5 years
  • Security updates available10 years
  • Approved byProduct
Shall I send the answer to Sales?
Send to SalesAsk our team
CEYour compliance engineer helps you prepare for the conformity assessment.
Why GetTeddy

One programme for your products and your organisation

  • AI agents that support your CRA work
  • CRA, ISO 27001 and NIS2 on one control set
  • Compliance engineer included
  • A human approves every decision
  • Hosting in the EU, Germany or the US

Read next CRA · NIS2 · ISO 27001 · SaaS · Automotive suppliers and TISAX®

FAQ

Questions from connected product makers

Does the CRA apply to products we already sell?

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.

What do we report, and when?

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.

Do we need a notified body?

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.

Are the app and the cloud part of the product?

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.

What fines apply?

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.

Where is our data hosted?

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.

Before and after

What changes with GetTeddy

TypicalThe CRA as a 2027 project
With GetTeddyDuties run with every release
TypicalWith GetTeddy
ClassificationLegal review per productProposal with reasons, confirmed by your team
RequirementsGeneric checklistsMapped to your controls per product
SBOMsCollected by handPer release from your repositories
ReportingOwnership settled during the emergencyProcess and templates with named roles
OngoingYearly reviewGap audits every week

Your products ready for the CRA, built on the controls you already run

In 30 minutes we show you how it works on one of your products.

  • Backed by Antler
  • Hosting in the EU, Germany or the US
  • Compliance engineer included