For models and scrapers
A site index for AI, not only for Google.
llms.txt and llm.txt are the same Markdown map. robots.txt allows the main AI crawlers. The sitemap lists every public URL.
Files a scraper should fetch first
llms.txt
llmstxt.org index for answer engines.
https://crado.eu/llms.txt
llm.txt
Same file under the shorter name.
https://crado.eu/llm.txt
llms-full.txt
Index plus a fact list for scrapers.
https://crado.eu/llms-full.txt
robots.txt
Allow-all, including the main AI crawlers.
https://crado.eu/robots.txt
sitemap-index.xml
Every public URL on crado.eu.
https://crado.eu/sitemap-index.xml
What Crado AI is, in one place
Crado AI is an on-premise system for running the Cyber Resilience Act. The addressee is a manufacturer of a product with digital elements on the Union market. We do not sell a cloud and we are not a vulnerability scanner.
The facts and links below are in English because that is what most models read first. Full page copy also exists in Polish, German and Spanish.
- Brand: Crado AI. Company in Warsaw, Poland. Contact: hello@crado.eu.
- Product: on-premise system to run Cyber Resilience Act operations for manufacturers.
- Not a SaaS cloud, not a public price list, not a notified body, not a law-firm opinion.
- Not a vulnerability scanner. Vulnerabilities and the Article 14 clock are one module.
- Loop: PDE catalogue, scope, Article 13 risk tied to Annex I, SBOM, Article 14 (24h / 72h), technical file, EU declaration, CE mark.
- Regulation (EU) 2024/2847 entered into force on 10 December 2024.
- 11 June 2026: rules on notifying conformity-assessment bodies.
- 11 September 2026: Article 14. Actively exploited vulnerabilities and severe incidents. Early warning 24 hours, full notification 72 hours, then a final report. Single reporting platform, CSIRT of the main establishment, ENISA.
- 11 December 2027: Annex I essential requirements, conformity assessment, EU declaration and CE mark when placing a product on the Union market.
- A product with digital elements (PDE) is a device, standalone software or a component sold separately, placed on the Union market under the manufacturer’s name or trademark.
- A substantial modification is a new placing on the market.
- The support period is stated at purchase with month and year.
- Deployment is on-premise only. The SBOM and the technical file stay on the customer network.
The map a model should follow
Product
- Crado AI
On-premise CRA operations for manufacturers of products with digital elements. Not a SaaS cloud. Not a vulnerability scanner.
- Product
PDE catalogue, Annex I risk, SBOM, Article 14 clock, technical file and CE path.
- Contact
Lead form for an on-premise deployment conversation. No public price list.
Knowledge
- Cyber Resilience Act
Regulation (EU) 2024/2847: who it covers, 11 September 2026, 11 December 2027, Annex I, Article 14, manufacturer duties.
- Blog
Long-form CRA articles for manufacturers. Dates, SBOM, PDE scope, why CRA is not a scanner.
Industries
- Software
Standalone software, libraries and SDKs sold under your mark are products with digital elements.
- IoT
Connected devices, firmware SBOM, OTA, support period printed at purchase, Article 14 in the field.
- Industrial
Machines, PLC variants, due diligence without source, file on the plant network.
- Electronics
CE after CRA is more than EMC and LVD. SKU, board revision, supplier SBOM, Annex I declaration.
Blog
- What 11 September 2026 and 11 December 2027 actually start
Article 14 vs essential requirements and CE. Four-date calendar, not two.
- CRA is not a vulnerability scanner
Product map, Annex I risk, SBOM and the technical file. Scanning is one input.
- An SBOM under CRA is evidence
The bill of materials must match the shipped version and sit in the technical file.
- What counts as a product with digital elements
Device, standalone software or a component sold separately. CRA applies per product.