What a CRA technical file costs to produce

Three routes to the same two documents. The honest answer is that all three involve the same seventeen items that only you can answer — what differs is who structures the work, who writes the prose, and what it costs.

1

A consultant engagement

Estimate: commonly quoted in the thousands of euros per product (estimate; no specific provider surveyed). You get someone who has read the Regulation, who can challenge your risk assessment, and who will write the prose. You also get a document that is current on the day it is delivered and starts drifting on your next release, unless the engagement is renewed.

2

Doing it yourself

Free. The regulation text is free and public on EUR-Lex, and ceproof's own citation data is derived from it. This is a genuinely viable route. The cost is the reading — Annex VII, Annex V, Articles 13, 28 and 31 at minimum — plus building the structure yourself, tracking which consolidated text and which corrigenda you worked from, and keeping the whole thing current across releases. For one product and a patient engineer, that is a real option.

3

ceproof

$99, one-time ($299 for agency use across client projects). The structure, the citations, the provenance block, and the regeneration are done for you. Two of the thirteen Annex VII items are derived from your repository, one partially. The other seventeen items across both annexes are still yours to answer — the tool will not write them, and says so in the output. Scanning and the gap checklist are free; the $99 unlocks the export.

What none of the three buys you

None of them makes you compliant. Conformity is a legal process involving your own assessment and, for some product classes, a notified body. A consultant can advise on it; a document generator cannot, and this one does not claim to.

Where ceproof is the wrong answer

If your product is C or C++ firmware, ceproof cannot read it today — it needs a repository with an npm or Python manifest, and it refuses to run rather than producing a document off no evidence. Importing an SBOM you already have is FDA-profile only (ceproof scan --profile fda --sbom firmware.cdx.json); the CRA profile takes no SBOM as input, and a component list pasted by hand is accepted on neither profile. Routes 1 and 2 above still work for you.

If your difficulty is the risk assessment itself rather than the paperwork around it, a consultant is a better use of the money. ceproof structures and cites; it does not assess.

What you actually get for $99

  • The Annex VII technical documentation pack and the Annex V declaration of conformity draft, as HTML and as print-rendered PDF.
  • Every one of the 21 items in the regulation's own order, each with its full citation to the consolidated text and the corrigenda it was checked against.
  • A provenance block on each document: the release it was generated against, the tool version, the timestamp, and the CRA data version.
  • An explicit open-items list, so nothing is quietly missing.
  • One year of CRA reference-data updates. The tool itself never stops working.
  • A full refund within 14 days if it does not do what the site says.

See what $99 produces, in full → · The 21 items →

Draft yours from your own repository

ceproof lays out all 21 items in the regulation's order, cites each one, derives what your repository can evidence, and lists what is still open. Free to scan and to see the gap checklist. $99, one-time to export the Annex VII pack and the Annex V DoC draft.

Needs a repository with an npm or Python manifest. C or C++ firmware is not supported today.