Blog · GEO

EU AI Act, explained

Own the definitional queries compliance teams ask before they trust an AI system to the EU market.

What does VendorVet include at a glance?

Regulation
(EU) 2024/1689
Ruleset pinned
eu-ai-act-deployer@2026-10-21
Risk tiers
Prohibited · High · Limited · Minimal
Annex III high-risk duties
Apply from 2 Dec 2027
Published guides
2
Output type
Decision support, not a certificate

Which deep-dive guides should you read first?

Long-form, cited explainers. Each carries primary-source references and a decision-support disclaimer.

What do people ask about VendorVet?

What is the EU AI Act risk taxonomy?

The Act classifies systems as prohibited, high-risk, limited-risk (transparency), or minimal risk. Official text: Regulation (EU) 2024/1689.

Does VendorVet issue a certificate?

No. It is decision-support documentation aid. Legal conformity assessment remains with you and qualified counsel.

Which obligations does it track?

Risk classification, technical documentation outlines, and phased deadline awareness mapped to publicly published timelines.

Is live AI required?

Demo mode works without a key. Live narrative needs a configured platform or enterprise BYOK key under fair use.

Who is it for?

Product and compliance teams shipping AI features to the EU who need an obligation checklist, not a law firm substitute.

Where are primary sources?

EUR-Lex Regulation (EU) 2024/1689 and European Commission AI Act guidance pages.

Which countries and regions can I use VendorVet in?

Reachable worldwide as a cloud app; Waffo Pancake payment availability may vary by region.

Is VendorVet GDPR and privacy compliant?

Inputs generate your output only and are never sold. See Privacy; Enterprise can include a DPA/NDA.

What languages does VendorVet support?

The UI supports ten locales. Generated narratives follow the selected UI language when live AI is configured.

How to map an AI system to its EU AI Act obligations

  1. Describe the AI system. Write one or two sentences on what the system does in production — for example, screening job applicants or scoring credit. The description drives the Annex III use-case match.
  2. State the intended users. Name who operates the system and who is affected (HR teams, public authorities, consumers). Intended use is what determines the applicable risk tier, not the vendor marketing label.
  3. Pick the deployment context. Choose the context you actually deploy in — public sector, workplace / HR, healthcare, finance, or general consumer. Context plus intended users is what separates limited-risk transparency duties from Annex III high-risk duties.
  4. Read the obligation output as a checklist. VendorVet returns a risk tier with rationale, the obligations that tier triggers, the phased deadlines, and an action checklist. Treat it as decision support and review it with qualified counsel before relying on it for a conformity assessment.

Scope: VendorVet produces decision-support documentation. It is not legal advice and does not issue a conformity certificate. Verify against EUR-Lex Regulation (EU) 2024/1689 and current Commission guidance.

Was this result helpful?Feedback