Skip to content

Provider vs. Deployer: Who Must Do What Under the EU AI Act?

The EU AI Act clearly distinguishes between providers and deployers. Both have different obligations – but shared responsibility. This guide clarifies the roles.

Updated: February 20269 min read

The Two Main Roles in the EU AI Act

Regulation (EU) 2024/1689 defines two central actors in the AI value chain:

  • Provider – Anyone who develops or commissions the development of an AI system and places it on the market under their own name (Art. 3(3))
  • Deployer – Anyone who uses an AI system under their own authority (Art. 3(4))

Who Is a Provider?

Art. 3(3) EU AI Act: A natural or legal person that develops or commissions the development of an AI system and places it on the market or puts it into service under its own name or trademark.

Typical providers:

  • Software companies that develop AI products
  • Tech startups with AI-based SaaS solutions
  • Companies that train an AI model and offer it as an API
  • Companies that substantially modify an existing AI system (Art. 25) – thereby becoming a provider

Who Is a Deployer?

Art. 3(4) EU AI Act: A natural or legal person that uses an AI system under its own authority – except in the course of a personal, non-professional activity.

Typical deployers:

  • A bank using a third-party credit scoring system
  • An HR department using an AI tool for candidate screening
  • A hospital deploying an AI diagnostic solution
  • A public authority using an AI system for social welfare decisions

Obligations Compared

ObligationProvider (Art. 16)Deployer (Art. 26)
Risk management system (Art. 9)Yes – establish and maintainNo
Data governance (Art. 10)YesNo
Technical documentation (Art. 11)Yes – create and updateNo (but may request access)
Record-keeping (Art. 12)Yes – enable system logsYes – retain logs
Transparency (Art. 13)Yes – instructions for useYes – duty to inform affected persons
Human oversight (Art. 14)Yes – enableYes – carry out
FRIA (Art. 27)NoYes (for public bodies, credit scoring, HR)
Conformity assessment (Art. 43)YesNo
CE marking (Art. 48)YesNo
EU database registration (Art. 49)YesYes
Incident reporting (Art. 62)YesYes

When Does a Deployer Become a Provider?

Art. 25 EU AI Act defines important cases:

  1. Substantial modification – The deployer substantially modifies a high-risk AI system
  2. Own name/trademark – The deployer places the system on the market under its own name
  3. Change of intended purpose – The system is used for a high-risk purpose not intended by the provider

In these cases, the deployer assumes all provider obligations – including technical documentation and conformity assessment.

Decision Guide: Are You a Provider or Deployer?

  1. Did you develop the AI system yourself or commission its development? → Provider
  2. Are you placing it on the market under your own name/trademark? → Provider
  3. Have you substantially modified an existing system? → Provider (Art. 25)
  4. Are you using a third-party system without substantial modification? → Deployer

Correctly Assigning Obligations with AIvunera

When using our document generator, you select your role (provider/deployer). Our AI tailors the generated drafts accordingly:

  • As a provider, you receive: Technical documentation (Annex IV), transparency notice (Art. 13), and a FRIA if needed
  • As a deployer, you receive: FRIA (Art. 27), transparency notice (Art. 26), and guidance on collaborating with the provider

Generate role-specific drafts now – from €149 net →

Compliance drafts

FRIA, Technical Documentation and Transparency Notice – AI-generated for your system. From €149.

Generate drafts

Ready for your EU AI Act Compliance?

Review-ready document drafts – AI-generated, tailored to your system. From €149.

Provider vs. Deployer: Obligations Under the EU AI Act | AIvunera