EU AI Act compliance, built into your engineering workflow
Classify your AI systems, map the obligations to your architecture and keep requirements, documentation and evidence close to the work.
components/ChatWidget.tsx- Applies to
- Providers and deployers of AI systems placed on the EU market, including non-EU companies.
- Key dates
- In force since 1 August 2024. Annex III high-risk obligations from 2 December 2027.
- What's involved
- Inventory your AI use cases, classify each system by risk and map the obligations that apply.
- High-risk providers
- Risk management, data governance, technical documentation, logging, human oversight and more.
- Keldyn's role
- Keeps requirements, technical documentation and evidence close to engineering work.
On this page
Who it affects
The EU AI Act affects providers and deployers of AI systems placed on the EU market, including non-EU companies. UK companies can be in scope if they place AI systems on the EU market or their output is used in the EU.
EU AI Act application dates
- Entered into force
- Prohibited practices apply
- General-purpose AI model obligations
- High-risk standalone systems (Annex III)
- High-risk AI in regulated products (Annex I)
Dates reflect the AI Act as amended by the Digital Omnibus, as of November 2026. Not legal advice.
First, classify your AI systems by risk
Start with an inventory of your AI use cases. Classify each AI system by risk, then map the obligations that apply to its architecture and use.
What high-risk providers need
- Risk management
- Data governance
- Technical documentation
- Logging
- Human oversight
- Accuracy and cybersecurity
- Registration
The timeline, as of November 2026
- 1 August 2024: the AI Act entered into force.
- 2 February 2025: prohibited practices began to apply.
- 2 August 2025: general-purpose AI model obligations began to apply.
- 2 December 2027: high-risk obligations for standalone systems (Annex III).
- 2 August 2028: high-risk obligations for AI embedded in regulated products (Annex I).
The Digital Omnibus on AI received final approval in June 2026. Transparency duties are phasing in.
Dates reflect the AI Act as amended by the Digital Omnibus, as of November 2026. This page is not legal advice.
How Keldyn helps
Map obligations to the build
Keldyn inventories and classifies AI use cases, maps obligations to your architecture and gives requirements to coding agents through Keldyn MCP.
Secure design →Check changes before merge
The compliance gate checks every change before it merges against your security and compliance requirements.
Compliance gate →Evidence ready for review
Technical documentation and evidence from your tools and your checks, ready for your auditor, alongside ISO 42001, GDPR, NIS2 and DORA.
Evidence and audit →Keldyn helps you keep requirements in the engineering workflow and technical documentation and evidence current as your AI systems change.
Frequently asked questions
Does the delay mean we can wait?
Prohibitions and general-purpose AI model rules already apply, and preparation takes time.
Does it apply to UK companies?
Yes, if you place AI systems on the EU market or their output is used in the EU.
Is ISO 42001 enough?
ISO 42001 supports EU AI Act readiness, but it is not a substitute for compliance with the Act.
“You should be building to compliance rather than fixing to it.”
Tim BrownCo-Founder, Kyance




