Immutable document custody
Your technical file is held in an AES256/512 encrypted, immutable vault outside your own infrastructure, so ransomware, a corrupted migration, or an accidental deletion on your side leaves the deposit untouched.
Every product with digital elements you place on the EU market needs an Annex VII technical file, kept available to market surveillance authorities for at least ten years. Codekeeper’s Technical File Custody holds versioned files in an independent, encrypted vault.
A technical file you cannot produce breaches your manufacturer obligations under Article 13. Fines run up to €15 million or 2.5% of worldwide annual turnover. No manufacturer can afford a migration or a breach erasing evidence they stay liable to produce.
Your technical file is held in an AES256/512 encrypted, immutable vault outside your own infrastructure, so ransomware, a corrupted migration, or an accidental deletion on your side leaves the deposit untouched.
When you update the technical file, Codekeeper pulls the new version from your connected storage and development tools, so the deposit matches the file you keep current under Article 31(2).
Every deposit is stored as its own dated version with a timestamped audit trail, and you set how many versions to retain. A request about a product you shipped six years ago draws the file exactly as it stood then.
Custody runs ten years from the date each product is placed on the market, or your declared support period where that is longer — so no file leaves custody while you are still liable to produce it.
Your signed EU declaration of conformity is deposited alongside the technical file version it certifies, so the two never drift apart and the pairing an authority asks for still holds years later.
Verification checks each deposit against the elements Annex VII requires, so gaps are identified and corrected early instead of surfacing during an audit.
You hand over the technical file as it stands today, including the product description, the cybersecurity risk assessment, test reports, and your signed EU declaration of conformity.
Codekeeper syncs changes from your systems, stores each as a dated version, and checks it against Annex VII.
When a market surveillance authority or notified body asks, you retrieve the exact version they need, with its Software Resilience Certificate.
Setup is live in 24 hours, and custody starts with the technical file you have today. How your team authors and stores that file stays exactly as is.
Book a demoJordan Adler
Ross Kilshaw
Thiago Mendes
We’ll email the sample custody report to you.
The CRA technical file is the technical documentation set out in Annex VII. It covers the product description and intended purpose, the information and instructions for users, the design, development and vulnerability-handling processes including the software bill of materials, the cybersecurity risk assessment, the information used to set your support period, the harmonized standards applied, test reports, and a copy of your EU declaration of conformity.
CRA technical documentation must be kept for at least ten years after the product is placed on the market, or for the support period where that runs longer, under Article 13(13). The same duty covers your EU declaration of conformity. Article 31 separately requires the technical file drawn up before the product is placed on the market and kept updated across the support period.
If you cannot produce your CRA technical file, Article 58 treats technical documentation that is unavailable or incomplete as formal non-compliance, and the market surveillance authority requires you to bring that non-compliance to an end. Where it continues, the Member State restricts or prohibits the product, or has the product recalled or withdrawn from the market.
The CRA technical documentation duty applies to manufacturers first, and it reaches further down the supply chain. Article 18(3) requires an EU authorized representative to keep the technical documentation and EU declaration of conformity at the disposal of market surveillance authorities for ten years after the product is placed on the market, or the support period where that is longer, and Article 19 places a corresponding obligation on importers.
Technical File Custody is different from your own platform or cloud storage because the technical file is held by an independent third party, outside the systems that could lose it. Your own tooling can be migrated, retired, or reached by ransomware, and version history usually breaks in the move. Custody keeps each dated version intact and retrievable for the full retention period.
A technical file held in custody stays reachable through both. Custody continues independently of your company’s status, so an acquirer or successor inherits the file with its full version history rather than a partial copy. Article 13(23) separately requires a manufacturer that stops trading to inform market surveillance authorities before the cessation takes effect, and to inform users by any means available.
Technical File Custody supports the CRA most directly, covering the Annex VII technical documentation under Article 31 and the ten-year retention duty under Article 13(13). The same deposit serves the EU AI Act’s ten-year documentation keeping under Article 18, the records protection control in ISO 27001 Annex A 5.33, the six-year documentation retention HIPAA places on business associates, and the vital records expectations in the FFIEC IT Handbook.