Docs

GPAI providers vs deployers: definitions, role-switch rules, and obligation split

As of 18 November 2026 · checked against Regulation (EU) 2024/1689, Regulation (EU) 2026/1744 and the Commission GPAI guidelines · Deutsch

Information only, not legal advice. The provider/deployer split has direct compliance consequences and changes when you fine-tune. Confirm role attribution with qualified counsel.

The AI Act allocates obligations by role. A provider builds and places on the market. A deployer puts the system to use. For general-purpose AI models the line gets blurry fast: most modern stacks involve fine-tuning, retrieval augmentation, agent scaffolding, and re-distribution under a new brand. Article 25 explicitly turns deployers into providers under defined conditions. This page sets out the definitions, the role-switch triggers, and what each side owes for GPAI specifically.

The two definitions, side by side

AspectProvider (Art. 3(3))Deployer (Art. 3(4))
ActionDevelops or has developed an AI system or GPAI modelUses the system under its own authority
TriggerPlaces on the market or puts into service under its own name or trademark, for payment or free of chargeAny use except in the course of a personal, non-professional activity
ScopeIncludes free of charge and open source where placed on the EU marketIncludes public sector and private sector
Liability axisProduct-side (Art. 16, Art. 53 for GPAI, Art. 55 for systemic risk)Use-side (Art. 26, Art. 27 FRIA where applicable)

When a deployer becomes a provider: Article 25

Article 25 turns a downstream actor into a provider of a high-risk system in three situations:

When one of these cases occurs, the initial provider is no longer the provider of that specific system. As amended by the Digital Omnibus, Art. 25(2) requires it to cooperate with the new provider: technical documentation, known limitations and failure modes, and targeted technical access for testing. That duty does not apply if the initial provider clearly stated that its system is not to be changed into a high-risk system. A downstream provider that integrates a GPAI model becomes provider of its own system, not of the model. It relies on the information the GPAI provider must supply under Art. 53(1)(b) and Annex XII.

Obligation split for GPAI specifically

ObligationGPAI providerDownstream provider integrating GPAIPure deployer
Technical documentation (Art. 53(1)(a))YesNo; for its own high-risk system Art. 11 appliesNo
Information for downstream providers (Art. 53(1)(b))YesReceives itNo
Copyright policy (Art. 53(1)(c))YesNoNo
Training-data summary (Art. 53(1)(d))YesNoNo
Systemic-risk obligations (Art. 55)If above 10^25 FLOP threshold or designatedNoNo
Conformity assessment of integrated high-risk systemIf integratingYesNo
Article 26 deployer dutiesWhere also deployerWhere also deployerYes
FRIA (Art. 27)Where also deployer in scopeWhere also deployer in scopePublic bodies, private entities providing public services, and deployers under Annex III, points 5(b) and (c)

Fine-tuning: when does it flip the role

This is the hard question for builders. The Commission guidelines on GPAI providers answer it with a compute criterion (Commission Q&A):

Decision pattern: pin the role at release time

function classifyRole(release) {
  if (release.isOriginalGPAI)                 return 'gpai-provider';
  if (release.modificationComputeShare > 1/3) return 'gpai-provider-of-modified-model';
  if (release.cumulativeFLOP >= 1e25)         return 'gpai-provider-systemic';
  if (release.integratedIntoAnnexIIIPurpose)  return 'high-risk-provider';
  if (release.usesUnderOwnAuthority)          return 'deployer';
  return 'undetermined-escalate';
}

What we track as events

The gpai topic covers Article 53/55 developments, the roles sub-topic covers Article 25 interpretations and Commission guidance on substantial modification. Subscribe with both filters to see role-switch implications cleanly.

Sources

→ See live updates: https://aiactradar.com

→ Subscribe to webhook: https://docs.aiactradar.com/quickstart