Launching soon — not yet accepting new client matters.
Interactive · EU AI Act

Does the EU AI Act apply to you?

Most AI-native SaaS is not a "high-risk system" — but founders either panic that it is, or assume the Act is a Europe problem that doesn't reach a US startup. Both are wrong often enough to matter. Answer a few questions and land in the bucket that actually fits your product, with the obligations and 2026 dates for each.

In effect
Prohibited practices + AI-literacy duty (since 2 Feb 2025)
In effect
GPAI model obligations + governance (since 2 Aug 2025)
2 Aug 2026
High-risk (Annex III) + transparency (Art. 50) + EU enforcement
2 Aug 2027+
High-risk embedded in regulated products

The one distinction that trips everyone up

Are you a provider or a deployer? If you build and put an AI system (or a general-purpose model) on the market, you're a provider and you carry the heavier obligations. If you use someone else's model — say you call the OpenAI API inside your app — you're mostly a deployer, with lighter duties (use it as intended, keep humans in the loop where required, pass through transparency notices). Most "we're an AI startup" companies are deployers of a third-party model plus providers of their own thin layer, and the obligations attach differently to each. Getting that split right is usually the difference between a weekend of disclosures and a genuine compliance program.

This decision tree is a general educational guide, not legal advice, and using it does not create an attorney-client relationship. The Act's classifications turn on specific facts about your system and how it's used; a result here is a starting orientation, not a determination. Have an actual classification confirmed before you rely on it.

Get your AI Act classification confirmed →