CRA files for connected hardware, built from a parts list.

Upload the parts list your chip or module supplier sent you. Readymark turns it into the component list (SBOM), technical file and EU declaration the CRA asks for, ready for your review and signature. When a component is actively exploited, you get drafts of your Art. 14 reports to ENISA.

Reg. (EU) 2024/2847EU Cyber Resilience Act, in force since 10 December 2024

Three questions, no sign-up. Your answers stay in your browser.

Example drillArt. 14(2)(a)
Sample product LSP-2 smart plug: a flaw in its local API is actively exploited.
Time left for the early warning
23:59:59
  1. 24 hEarly warning to CSIRT and ENISA14(2)(a)

This clock restarts at 24 hours each time the page loads. In your workspace it runs from the moment you record that you became aware of the exploit.

The file you hand to the authority

An excerpt from the technical file Readymark drafts for its built-in example product. Gaps stay marked until you fill them in.

DocumentTechnical documentation · Lumo Smart Plug LSP-2
Doc. no.TF-LSP2-001
Revision1 · fw 2.4.1
Date27 Oct 2026
Annex VII (3)Art. 13(2)–(4)Annex I Part I

3. Cybersecurity risk assessment

Known or foreseeable risk circumstances: use on an open Wi-Fi network; exposing the local control port to the internet through port forwarding; reusing the default pairing code.

RefRequirementStatusHow the product meets it
Part I (1)Appropriate level of cybersecurity based on the risksIn progressThreat model drafted for cloud, app and local interfaces.
Part I (2)(a)No known exploitable vulnerabilities when placed on the marketOpen[to complete: how the product meets this]
Part I (2)(b)Secure by default configuration, with a reset to the original stateEvidence attachedUnique pairing code per device; local port closed until paired; factory reset by 10-second button press.
Part I (2)(c)Security updates, automatic by default, with an opt-outEvidence attachedSigned OTA updates, automatic by default, user can postpone for 7 days.
Example Devices Ltd · TallinnSection 3 of 8 · prepared under Art. 31 and Annex VII

See a full sample technical fileDeclaration, user information and disclosure policy included.

Two minutes, parts list to report

The workspace walked through on the built-in example product: scope, components, scan, the known-exploited finding, the 24-hour clock and the drafted report. Captions, no sound.

Reporting applies since11 Sep 2026

Report exploited vulnerabilities within 24 hours, including for products already on the market.

Full application from11 Dec 2027

Connected products placed on the EU market from this date need a CRA technical file, declaration and CE marking.

Maximum fine€15M or 2.5%

The higher of the two, counted on worldwide annual turnover (Art. 64(2)).

From parts list to a file ready to sign, in four steps

The workspace prints the article or annex next to each field you fill in.

  1. Art. 2, 7, 8

    Scope check

    Three questions settle whether the CRA applies. Match your product against the Annex III and IV lists and the workspace names your conformity route.

  2. Annex I Part II (1)

    Components

    Import a CSV parts list or an existing SBOM. Download the component list as CycloneDX 1.5 or SPDX 2.3.

  3. Annex II, V, VII

    Technical file

    Each missing detail shows as a marked gap in the draft. Fill it in, then download the technical file, declaration and user information.

  4. Art. 14

    Watch and report

    The scan matches components against OSV.dev and CISA's Known Exploited Vulnerabilities catalogue. For an exploited finding, the reporting step drafts all three Art. 14 reports. On the Desk plan, Readymark re-checks your components every day and alerts you.

What goes in your file

Keep these for market surveillance authorities for ten years after placing on the market, or for the support period if longer (Art. 13(13)).

Technical documentation

Product description, architecture, risk assessment against all 14 essential requirements, support period, standards, test reports.

Annex VII · Art. 31

EU declaration of conformity

Full declaration plus the simplified text to ship with the product.

Annex V · Annex VI

Security information for users

Contact point, support end date, secure setup, updates and data removal.

Annex II · Art. 13(18)

Vulnerability disclosure policy

A published policy and a security.txt file for your website.

Annex I Part II (5)(6)

Software bill of materials

CycloneDX or SPDX file. Re-import the parts list with each firmware release to keep it current.

Annex I Part II (1)

Built for two kinds of seller

Readymark assumes a parts list and no in-house security team.

EU makers

Small hardware brands

You design smart home devices, sensors, wearables or e-bike electronics with 5 to 100 people. Your firmware comes from a chip vendor's SDK.

  • Works from a parts list; no code repository needed
  • One price per product, with no per-developer seats
Non-EU sellers

Marketplace sellers

You sell connected products on Amazon EU or other marketplaces from China, the UK, the US or Turkey. You already pay a GPSR representative.

  • Documents drafted in English. You provide the declaration and user information in the languages each Member State where you sell requires (Art. 13(18), 28(2)).
  • Report text for each of the three Art. 14 stages
  • A partner plan for representative firms that serve many sellers

Where Readymark fits

Options a small maker weighs for a first connected product. Costs outside Readymark come from public price lists and one published estimate.

OptionYou needTypical costAfter the file
Consultancy projectWeeks of workshops€30,000 to €60,000 for a first product (Porta Regulus estimate)Ends at delivery
Developer security toolsA code repository and an engineer to run themFrom $25 per developer per month (Snyk Team); enterprise tools on requestFindings, no filing
Enterprise firmware platformsA sales processNot publishedManaged, per product per year
ReadymarkYour supplier's parts listFree for drafts and up to 10 components · from €79 per product per monthScans on demand, and an automatic daily check on the Desk plan
Source text

How we check the law

Readymark holds the CRA as structured data, and every requirement, deadline and list in it carries its article or annex reference. You can check each one against the official text on EUR-Lex, CELEX 32024R2847.

The workspace paraphrases the law in plain English. Where the wording differs, the official text applies.

One price per product

Prices exclude VAT. Cancel at the end of any month and keep every document you generated.

Free

€0

Scope check, SBOM, full previews of every document, scans up to 10 components. Your workspace is stored in your browser.

Start free

Starter

€79 per product / month

One-off setup €490

  • Everything in Free
  • Download, print and copy the technical file, EU declaration and user information
  • Vulnerability scans of any size, whenever you run them
  • Encrypted cloud backup, open in any browser
Subscribe to Starter

Desk Daily check

€199 per product / month

One-off setup €490

  • Everything in Starter
  • Automatic re-check of your components every day against OSV.dev and the CISA known-exploited catalogue
  • Browser notification when a component becomes known-exploited or a new critical vulnerability appears, even with the workspace closed
  • Art. 14 report drafts prefilled from the alert
Subscribe to Desk

Partner

€490 per month

One-off setup €490

  • For EU representatives and seller agencies
  • One workspace for all client products
  • 10 client products included, €39 each after
  • Daily check and notifications for every client product
  • Complete files to hand over to each client
Subscribe as a partner

Founding customers (first 20): no setup fee and 50% off the first three months. Stripe applies the discount at checkout.

Ask a question first

Payment through Stripe. Invoices are issued by SIA "DDA Projects". Change the number of products in the workspace menu, and cancel from your billing page, at any time.

Readymark is software, not a law firm, and does not give legal advice. Your company signs the documents and stays responsible under the CRA.

Questions

Readymark prepares documents and reports. Your company signs them and stays responsible under the CRA.

Does the CRA apply to my product?

It applies to products with software or firmware that can connect to a device or network, directly or through an app. Medical devices, vehicles, aviation and marine equipment have their own rules and are excluded. The scope check in the workspace walks through Art. 2 and gives you the answer with the article it rests on.

My radio product already meets the RED cybersecurity rules. Is that enough?

No. The RED rules cover some security properties of radio equipment. They do not include the 24-hour reporting under Art. 14, a software bill of materials, a disclosure policy or a stated support period, and from 11 December 2027 the CRA is the rule for connected products. Your RED work still counts as evidence in the CRA file.

We are a small company. Do we still have to report?

Yes. Micro and small enterprises cannot be fined for missing the 24-hour early warning deadline (Art. 64(10)(a)), but the reporting duty itself applies to them.

Who submits the reports to ENISA?

Your company does, through the single reporting platform with an EU Login account. At launch the platform has no API, so no tool can submit for you. Readymark prepares each stage so the person on duty can paste and submit it in minutes.

Do you replace a notified body?

No. Most connected products are in the default category and can use self-assessment. Class I products can self-assess only if they apply a harmonised standard, common specification or certification scheme in full; until CRA standards are published, that usually means a notified body. Class II and critical products need a notified body or a certification. Readymark prepares the file you hand to them.

There are no harmonised CRA standards yet. How can the file be complete?

Annex VII lets you describe the solutions you adopted where no standard is applied. The workspace asks for that description for each requirement, and suggests established references such as ETSI EN 303 645 for consumer IoT.

In which language are the documents?

Readymark drafts them in English. The declaration of conformity and the information for users must be in the languages each Member State where you sell requires (Art. 28(2), Art. 13(18)), so plan a translation for each market.

How does the partner plan work?

Representative firms and seller agencies run one workspace for many client products. Each product's documents carry the client's name as manufacturer, and each client gets a complete file to keep. Ten client products are included; each further product costs €39 per month and can be added from the workspace menu.

Write to us

Ask about scope, the partner plan or a product line with many models. Replies come by email within two working days.

The details are used only to answer you. See the privacy policy.

Check your product against Art. 2 before your next shipment.

Start the scope check