available
Industry template: Manufacturers
- Cyber Resilience Act per product up to CE marking
- Radio Equipment Directive with EN 18031
- Vulnerability management with SBOM
from €427 per month plus VAT in the Start package, size S, annual payment
Who it’s for
You develop software, firmware, apps or connected devices and sell them in the EU. Since 11 September 2026 you have to report actively exploited vulnerabilities and severe incidents under the Cyber Resilience Act, and from 11 December 2027 all requirements for your products apply. Complass guides you per product from classification to CE marking and through the support period.

For an actively exploited vulnerability you have 24 hours until the early warning, even for products that have been on the market for a long time. This only works with a well-rehearsed process.
Libraries, open source and supplier components: without an up-to-date software bill of materials you cannot tell which product is affected by a new vulnerability.
The Radio Equipment Directive, the CRA, the Data Act and, where relevant, the AI Act interlock, each with its own deadlines and transitions.
The Cyber Resilience Act applies to products with digital elements that can connect to a device or network, which covers most software and almost all connected devices. Exceptions include medical devices and vehicles with their own type approval.
Frameworks: CRA · Radio Equipment Directive · IEC 62443 for manufacturers · Data Act · AI Act
Not sure which frameworks apply to you? Start the applicability check
Costs, effort and time: consultant only, consultant with Complass or in-house with Complass? Open the compliance cost calculator
AI in the product. If your product contains an AI system, check its classification under the AI Act. If the AI is a safety component of a product that needs a third-party conformity assessment under EU law, it may be high-risk. Transparency obligations, for example for chatbots, have applied since 2 August 2026. Art. 6 AI ActArticle 6 AI Act Classification rules for high-risk AI systems1. Irrespective of whether an AI system is placed on the market or put into service independently of the products referred to in points (a) and (b), that AI system shall be considered to be high-risk where both of the following conditions are fulfilled: - (a) the AI system is intended to be used as a safety component of a product, or the AI system is itself a product, covered by the Union harmonisation legislation …Open original (EUR-Lex – consolidated version of 27.07.2026) ↗ Art. 50 AI ActArticle 50 AI Act Transparency obligations for providers and deployers of certain AI systems1. Providers shall ensure that AI systems intended to interact directly with natural persons are designed and developed in such a way that the natural persons concerned are informed that they are interacting with an AI system, unless this is obvious from the point of view of a natural person who is reasonably well-informed, observant and circumspect, taking into account the circumstances and the context of use. This …Open original (EUR-Lex – consolidated version of 27.07.2026) ↗
General information, not legal advice. This page summarises the legal position in simplified form and does not replace an assessment of your individual case. The wording of the laws and standards is authoritative.
Standard software, apps and firmware: software bill of materials, updates and notifications throughout the support period.
Smart home, IoT and industrial devices with radio: the Radio Equipment Directive today, the CRA from December 2027.
Controllers, gateways and network components; routers and other network components partly count as important products with a stricter conformity procedure. IEC 62443-4-1 and 4-2 are a widely used framework.
Products with embedded AI: classification under the AI Act in addition to the CRA.
Classification, risk assessment, Annex I requirements, technical documentation and declaration of conformity, guided in phases.
More about this featureImport software bills of materials (CycloneDX, SPDX), match vulnerabilities and vendor advisories (CSAF) and export SBOM and VEX for customers and authorities.
More about this featureActively exploited vulnerability or severe incident: Complass shows the three reporting stages with deadline and the required details.
More about this featureA framework of its own for manufacturers with templates for the development process, the threat model and the PSIRT process, linked with the CRA.

The Manufacturers industry template preselects the CRA, the Radio Equipment Directive and vulnerability management with SBOM. You add the AI Act if you need it.
available
from €427 per month plus VAT in the Start package, size S, annual payment
available
from €79 per month plus VAT in the Practice package, size S, annual payment
All prices are for businesses, not for consumers. They are net plus VAT with annual payment; monthly payment carries a surcharge of 15 %. As of 16 October 2026. Enterprise and groups of companies on request.
Yes. Software sold on its own is also a product with digital elements. Pure cloud services without a product link usually fall under NIS2 rather than the CRA. Remote data processing without which a product cannot perform its function, however, is part of the product.
You have to report actively exploited vulnerabilities and severe security incidents via the single reporting platform, with an early warning within 24 hours. This also applies to products you placed on the market before this date.
The series of standards is not mandatory but is often required for industrial components. IEC 62443-4-1 describes requirements for a secure development process, IEC 62443-4-2 technical security requirements for components. Complass links both with the CRA requirements.
Set up your trial yourself, with a sample project per framework if you like. If you would rather see Complass first, request a demo.