Skip to main content
Praxikon
Determine your role under the AI Act

Provider vs deployer

Are you the provider or the deployer of an AI system?

Your role determines which AI Act obligations apply to you. The answer is usually quick, but your own brand, a substantial modification or a new purpose can still make you the provider.

Art. 3
role definitions
Art. 25
when you become provider
Art. 26
deployer obligations
~10 min readLast updated: October 2026

Are you a provider or a deployer?

If you use someone else's AI system under your own authority, you are a deployer (Article 3(4)). If you develop the system or have it developed and place it on the market or put it into service under your own name, even internally only, you are a provider (Article 3(3)). Your own name or trademark, a substantial modification or a new intended purpose can still turn a deployer into a provider (Article 25(1)).

Interactive Tool

Determine Your Role in 3 Steps

Answer a few questions about your AI system and see whether you are a provider, deployer, or another operator, including the obligations associated with that role.

Takes less than 1 minute

Official definitions

What does the law say exactly?

The AI Act makes a fundamental distinction between providers and deployers. The provider develops an AI system or has it developed and places it on the market or puts it into service under its own name or trademark, whether for payment or free of charge (Article 3(3)). The deployer uses an AI system under its authority, except for personal non-professional use (Article 3(4)). This distinction determines which obligations apply to you.

Provider (Article 3(3))

Develops the AI system or has it developed and places it on the market or puts it into service under its own name or trademark

Deployer (Article 3(4))

Uses an AI system under its authority, other than for personal non-professional use

Both roles possible

An organisation can have a different role per system, and both roles for one system

Role determines obligations

Providers of high-risk AI have the Article 16 obligations, deployers those of Article 26

Related articles

The value chain: from provider to deployer

Who does what for a high-risk AI system?

The AI Act spreads the obligations for high-risk AI systems across the whole chain, from development to use. The provider carries the heaviest obligations (Article 16). If it is established outside the EU, it appoints an authorised representative in the EU by written mandate before making the system available (Article 22). The importer places the system of a non-EU provider on the European market and first verifies the conformity assessment, the technical documentation, the CE marking, the EU declaration of conformity with instructions for use and the authorised representative (Article 23). The distributor makes the system available further and verifies the CE marking, the declaration of conformity and the instructions for use (Article 24). Importers and distributors only place a non-conforming system on the market once it has been brought into conformity. The deployer uses the system and has the obligations of Article 26. An importer, distributor or deployer can itself become the provider under Article 25(1).

Provider (Article 16)

Risk management, technical documentation, conformity assessment, CE marking, registration and post-market monitoring

Importer (Article 23)

Verifies before placing on the market that the non-EU provider has met its obligations

Distributor (Article 24)

Verifies CE marking, declaration of conformity and instructions for use before passing the system on

Deployer (Article 26)

Use according to instructions, human oversight, monitoring, logs and information to workers and affected persons

Product manufacturer (Article 25(3))

Is the provider where the high-risk system is a safety component of a product under Annex I, Section A, under the manufacturer's name or trademark

Suppliers (Article 25(4))

Agree in writing with the provider which information, access and assistance it needs to comply with the AI Act

Decision tree: determine your role

A first answer in three questions

Question 1: did you develop the AI system or have it developed? If not, you are probably a deployer. If so, go to question 2. Question 2: do you place it on the market under your own name or trademark? If so, you are a provider. If not, go to question 3. Question 3: do you only put it into service internally? You are still a provider, because putting into service for own use also counts (Article 3(3) and (11)). Note: if you buy a high-risk system and put your own name or trademark on it, or substantially modify it, you can become its provider (Article 25(1)).

Self-developed?

No: deployer. Yes: continue

Own name or trademark?

Yes: provider. No: continue

Internal use only?

Still a provider

Substantial modification or new purpose?

You can then move from deployer to provider (Article 25)

Provider obligations

What must a provider of high-risk AI do?

As a provider of a high-risk AI system, you have extensive obligations (Article 16). You set up a risk management system that runs through the whole lifecycle, draw up technical documentation before placing on the market, carry out the conformity assessment, affix the CE marking and register the system in the EU database where Article 49 requires it. After placing on the market, you monitor the system and report serious incidents.

Risk management system

Continuous, throughout the entire lifecycle (Article 9)

Technical documentation

Drawn up before placing on the market (Article 11)

Conformity assessment

With CE marking and, where required, registration in the EU database

Post-market monitoring

Track performance and report serious incidents (Articles 72 and 73)

Related articles

Deployer obligations

What must a deployer do?

As a deployer of a high-risk AI system, you have fewer obligations than a provider, but they are no less important. You use the system according to the instructions for use, assign human oversight to competent people, control the input data to the extent you manage it, monitor operation and keep the logs for at least six months. Where you see a risk, inform the provider or distributor and the market surveillance authority and suspend use; report a serious incident immediately, to the provider first (Article 26(5)). Public bodies and certain other deployers also carry out a FRIA (Article 27). The full list by paragraph, with a checklist, is on the Article 26 page.

Follow the instructions

Use within the provider's limits (Article 26(1))

Human oversight

By people with competence, training and authority (paragraph 2)

Logs and monitoring

Monitor operation and keep logs for at least six months (paragraphs 5 and 6)

Risk or incident

Report, and suspend use in case of a risk (paragraph 5)

Related articles

Special cases

When the role is less clear

Sometimes your role is not immediately clear. If you buy a high-risk system and put your own name or trademark on it, substantially modify it, or change the intended purpose of an AI system so that it becomes high-risk, you become its provider (Article 25(1)); if you use the system yourself, you are also its deployer. If you build your own application on a general-purpose AI model and place it on the market or put it into service under your own name, you are the provider of that application. Importers and distributors have their own obligations in Articles 23 and 24.

Dual role

You can be both provider and deployer of one system

Application on a GPAI model

Your own application under your own name makes you its provider

Importer

Obligations in Article 23

Distributor

Obligations in Article 24

Related articles

What the Digital Omnibus changed

Regulation (EU) 2026/1744, in force since 27 July 2026

The Digital Omnibus on AI is Regulation (EU) 2026/1744 and has applied since 27 July 2026. For providers and deployers, mainly the timeline shifts: the high-risk obligations apply from 2 December 2027 for Annex III systems and from 2 August 2028 for Annex I systems. EU database registration for systems that are not high-risk under Article 6(3) remains, with fewer data fields. Article 4 now requires providers and deployers to take measures that support AI literacy. The allocation of roles itself, with the definitions of Article 3 and the routes of Article 25, has not changed.

Annex III: 2 December 2027

High-risk obligations for stand-alone systems

Annex I: 2 August 2028

High-risk obligations for systems in regulated products

Registration remains

Simplified for systems under Article 6(3)

Roles unchanged

Articles 3 and 25 still determine your role

Frequently Asked Questions

Answers to the most common questions about the EU AI Act

Ready for your first AI Act route?

Discover which EU AI Act gap your organization should solve first.

500+
Professionals trained
50+
Organizations helped