LandingRed keeps one record of every AI system you build or use. From that record it derives the obligations, the documentation and the evidence each regulation asks for.
Four steps, in the order most teams actually work through them.
List every AI system you develop, buy or use. Record its purpose, its owner, its data, and your role: provider, deployer, importer or distributor.
A guided questionnaire places each system in its risk class under Article 6 and Annex III. It records the reasoning behind every answer.
Technical documentation, impact assessments, conformity records, logs and incident reports attach to the system they belong to, not to a folder somewhere.
Export an audit-ready pack for a customer, a notified body or a market surveillance authority. Every change is traceable to a person and a date.
Every item below is live in the product now. Work that is planned or under way sits on the roadmap instead.
The single record every other module reads. It holds purpose, owner, lifecycle stage, data sources, your role and the regulations that apply.
A questionnaire mapped to all eight Annex III areas and the Article 6(3) exception, with the reasoning documented per system.
Article 11 documentation generated from the inventory: versioned, exportable, and available in four languages.
The Article 27 assessment for deployers of high-risk AI, linked to the data protection impact assessments you already hold.
Map a control once. See its equivalents under the AI Act, GDPR, NIS2, the Cyber Resilience Act, DORA, the Data Act and ISO 42001.
Every classification, document and decision is logged and versioned. Records cannot be edited or deleted after the fact.
Each regulation has its own page with the obligations, the deadlines, and what the platform does about them.
Five minutes, no account needed. You get a readiness report with your risk level and the obligations that apply to you.