Regulation (EU) 2024/1689 · Artificial Intelligence Act ● Annex III: — days

EU AI Act Registration: Who Goes Into the EU Database and When (Article 49)

The EU database is where an AI system becomes a public fact. Which providers must register, which deployers must follow, what the entry actually publishes — and the SME carve-out that removes the step without removing the duties.

Renomira Team · 9 min read

Registration is the Act’s public-facing ledger: a Commission-maintained database (Article 71) where high-risk systems get entries that counterparties and authorities can check. It is also the obligation most often assumed to apply to everyone — and most often skipped by exactly the people it applies to, because the trigger conditions are narrower than “you run AI.”

A fountain pen resting on a contract awaiting signature
Photo: Blogtrepreneur / CC BY 2.0 via Wikimedia Commons

Article 49 sets who registers and when. The rule resolves differently for providers and deployers, carries a genuine SME exemption, and publishes more than most teams expect.

Providers: register before you place

Providers of high-risk AI systems must submit information to the EU database before placing the system on the market or putting it into service — for Annex III systems, via the provider’s own member state. The entry covers the essentials of the Annex IV technical documentation, in structured form: intended purpose, provider identity and contact, the classification and the conformity-assessment route taken, and the underlying characteristics.

Read that timing clause closely: registration is a precondition, not a post-launch chore. A system live in production with no entry is out of order even if everything else in the documentation is perfect.

What is not in scope: Article 6(1) product-safety-component systems register through their product legislation rather than this database; law-enforcement and certain defence-adjacent uses follow the restricted provisions; and Article 50 transparency-only systems (limited risk) are simply not registered — the database is a high-risk ledger, not an AI census.

Deployers: a narrower set

Deployers register too, but the net is much smaller. Article 49 pulls in:

  • deployers that are public bodies, and
  • private entities providing public services, and
  • deployers of the Annex III creditworthiness and life/health insurance high-risk systems.

A 400-person private manufacturer deploying an Annex III 4 screening tool does not register — its deployer duties (Article 26 oversight, logging, worker consultation) still apply in full. A municipal housing-benefits authority running an eligibility model does register.

The SME exemption — and its exact boundary

Article 49 exempts SMEs, including start-ups, from the registration obligation. This is one of the three explicit small-business concessions in the Act, and it is easy to over-read: what an SME skips is the database entry. The classification decision, the technical documentation an entry would summarise, conformity assessment where triggered — none of that moves. When an enterprise buyer asks for your classification evidence, “SME exempt” answers the registration question and nothing else.

What an entry publishes

More than teams budget for. Expect the entry to surface: provider and authorised-representative identity, system intended purpose, the high-risk classification with its Annex III area, conformity-assessment details, and the substantive characteristics of the system. This is public transparency aimed at exactly the thing enterprise procurement checks — a buyer can verify your claim instead of trusting your PDF.

Two consequences follow. First, your public documentation and your database entry must agree; inconsistencies are findable by anyone. Second, the entry is a version artefact: a system re-classified or materially updated needs its record to move with it.

Registration in the procurement conversation

Auditors and buyers treat the entry as a checkable control. The passing pattern in questionnaires:

  1. Provider — registration entry reference plus the classification reasoning behind it.
  2. Deployer, in the narrow Article 49 set — your own entry, or the article that puts you outside it.
  3. Deployer, outside the set — a one-line note: Article 49 deployer registration not applicable (private, non-public-services deployer); Article 26 duties apply and are documented. Naming the article that excludes you reads better than silence.

That third answer converts an apparent gap into evidence of a completed analysis.

The sequence that keeps entries true

Registration is the visible tip; keep the machinery underneath in one order:

  • Classify (Article 6 record) → document (Annex IV file) → register (database entry) → operate with oversight and logging (Article 26, for deployers) → re-verify on change — model version, intended purpose, classification move.

Every re-classification event ends with one question: does the entry still say what the system now is? If the answer is no, the entry updates before the system change rolls, not after the next audit finds it.

How to check your own position in four minutes

The free exposure scan asks twelve questions about your AI usage and governance and returns an exposure score, your ranked exposures with the exact article that fired, and your first three moves — mapped to the dates that apply. Confirm your email and the full report unlocks.

Frequently asked questions

Do I have to register my AI system in the EU database?

Providers of high-risk AI systems must register before placing the system on the market or putting it into service (Article 49). Deployers must register only in the narrower cases: public bodies, private entities providing public services, and deployers of the Annex III creditworthiness and life/health-insurance systems. SMEs, including start-ups, are exempt from the registration step. Limited-risk systems subject only to Article 50 duties are not registered at all.

Is AI Act registration the same as conformity assessment?

No. Conformity assessment is the verification that the system meets the Act — self-assessment or notified-body route depending on the system. Registration is the publication of the outcome and key facts into the EU database. Assessment first, then registration: the entry reports the route you completed, so an entry without a completed assessment misstates your position.

Are SMEs exempt from EU AI database registration?

Yes — Article 49 exempts SMEs, including start-ups, from the registration obligation. The exemption covers the entry itself: classification reasoning, technical documentation and any triggered conformity assessment remain fully required. Enterprise buyers asking for evidence will not accept the exemption as an answer to those.

What information appears in the EU AI database entry?

Provider identity and contact, intended purpose, the high-risk classification including the applicable Annex III area, conformity-assessment details, and the system’s substantive characteristics as drawn from the Annex IV documentation. The purpose is public verifiability — counterparties can confirm your claim rather than rely on a document you authored.

When does a deployer need its own registration entry?

When the deployer is a public body or a private entity providing public services, or when it deploys an Annex III creditworthiness or life/health-insurance system. Everyone else with Annex III systems owes Article 26 deployer duties — oversight, logging, consultation — without an entry. Record the exclusion reasoning; a documented “not applicable” passes reviews where an absence does not.

Next step

Put this guide to work on your own estate.

Run the free exposure scan to see which of these articles actually apply to your company — 12 questions, four minutes, no card. Confirm your email and the full report unlocks.

  • Free forever plan
  • No credit card
  • EU-hosted · GDPR-native
Run a free scan Sign up free

Build a live AI register in minutes — upgrade only when you need the audit pack.

EU AI Act registration requirementsArticle 49 EU database AIAI Act EU database register high-riskdo deployers have to register AI systemsAI Act registration SME exemptionwhen to register AI system EUEU database AI transparency

Keep reading