Skip to content

Where does your AI land under the EU AI Act?

Six questions about one AI use case. Out comes the risk class, the obligations that apply to your role, and the deadlines. Plain language instead of legalese, results in English or German.

1 · Your role
2 · Does the system do any of these?

The banned list. Leave everything unchecked if none apply.

3 · Where does it make or shape decisions?

The high-risk areas. Leave everything unchecked if none apply.

5 · Does it talk, generate, or read people?

The transparency triggers. Leave everything unchecked if none apply.

One use case per check. Nothing stored. Orientation, not legal advice.

What this answers

The risk class

Prohibited, high-risk, transparency, or minimal: the four levels of Regulation (EU) 2024/1689, decided by what the system does and where it decides.

Your obligations, not all obligations

Providers and deployers carry different duties. You get the checklist for your role, with article references and deadlines.

The timeline

What has applied since 2025, what still lands on 2 August 2026, and what the omnibus agreement moves to 2027 and 2028.

Classified. Now build it compliant.

We build AI systems with the EU AI Act in the architecture: logging, human oversight, transparency, and documentation from day one.

Contact

What eats your team's time?

Two or three sentences are enough. Philipp reads every message himself and usually replies within two business days.

Philipp Kant

Philipp Kant
Software & AI Architect, Krefeld

What is it about?

Opens your email app with the message to philipp@kant.dev, ready to send. You see everything before it goes out. Privacy policy

  • No sales call unless you ask for one.
  • No newsletter, no automated follow-ups.
  • Your message goes to one inbox: philipp@kant.dev.

Rather talk? Pick a 30-minute slot

Or write directly: philipp@kant.dev