Deployer vs Provider Under the EU AI Act: Which Role Does Your Company Hold?
Your obligations under the AI Act are decided by the role you hold for each system — and most companies hold several at once. A clear test for each, with the articles that follow.
Nobody is “compliant with the AI Act” in general. You are compliant, or not, for each system in the role you hold for that system. A single company can be a provider for the product it sells, a deployer for the tools it buys, and an importer for a plugin it resells.
Getting the role wrong is the most expensive classification error there is, because it sends the entire obligation set to the wrong party — and the authority will still ask you.
The five roles, in one line each
| Role | Test | Core articles |
|---|---|---|
| Provider | You developed a system, or put your name/trademark on it, or substantially modified it | Arts. 8–15, 16, 17, 43, Annex IV |
| Deployer | You use a system under your own authority | Arts. 26, 27, 86 |
| Importer | You place a third-country system on the EU market | Art. 23 |
| Distributor | You make a system available on the EU market | Art. 24 |
| Authorised representative | Appointed by a third-country provider before placing on the market | Art. 22 |
“Placing on the market” means making an AI system available in the Union. “Putting into service” means using it for the first time under your own control. Those two verbs do most of the interpretive work in Article 2.
The deployer test — what most mid-market companies are
You are a deployer if you use an AI system under your own authority. You did not build it, you did not brand it, you are not selling it on. You decided the purpose and you run it.
Concretely, that is anyone who:
- Licences a recruiting platform and configures it for their own hiring.
- Runs a support chatbot on their own website.
- Buys a credit-scoring service for their own lending decisions.
- Uses a general assistant inside their own operations.
Deployer duties are narrower than provider duties and almost entirely operational: use as instructed, human oversight, input-data quality, logs, worker notification, cooperation with authorities. Add Article 27 only if you are a public body, a private entity providing public services, or a deployer of creditworthiness or essential-services systems.
The provider test — when you become one without meaning to
Article 25 exists precisely because vendors and customers keep arguing about this. You become a provider of a system that is not yours if you:
- Put your name or trademark on it. Rebranding a third-party model or system as your own product.
- Substantially modify a high-risk system. Changing its intended purpose in a way not foreseen by the original provider — taking a general tool and making it do something Annex III.
- Modify the intended purpose of a non-high-risk system such that it becomes high risk.
- Hide or remove the provider’s identity or trade on their conformity documentation.
The classic mid-market trigger: a SaaS company adds a generative feature, puts its logo on the output and ships it to customers. For that feature, it is now a provider — technical documentation under Annex IV, CE marking route, quality management system under Article 17, registration in the EU database, and post-market monitoring under Article 72.
Note that white-labelling a deployer’s internal configuration does not by itself create a provider role. The test is market-facing: did you make this available as your product?
The hybrid case: GPAI and foundation models
If you fine-tune a general-purpose model and offer the result as a service, the analysis depends on whether the fine-tune substantially modifies the model or simply configures it. Fine-tuning for a specific internal purpose keeps you a deployer. Offering a fine-tuned model to the market as your own may make you a provider of that model.
Providers of general-purpose AI models carry their own regime — Article 53 documentation, copyright policy and training-data summary for all GPAI models, with heavier systemic-risk duties above the compute threshold. The deployer of a system built on that model keeps its Article 26 duties regardless.
Importers, distributors and the authorised representative
Three roles matter when the vendor sits outside the EU:
- Importer (Art. 23): you place a third-country system on the Union market. You must verify the provider has done its conformity work, keep the declaration of conformity and the instructions, and put your name and address on the system.
- Distributor (Art. 24): you make it available. You must verify the required marking and documentation before distributing.
- Authorised representative (Art. 22): a third-country provider must appoint one in the Union before placing a high-risk system on the market, and that representative holds the technical documentation and answers to the authority.
If you are a European company reselling or embedding a non-EU vendor’s AI product, you are probably an importer as well as a deployer — and that changes your contract requirements substantially.
How to run the role analysis
Do it once per system, not once per company:
- Name the system as it exists in your register — the tool, not the vendor.
- Who put their name on it in the market? If you, you are a provider.
- Who decides its purpose in your organisation? If you, you are a deployer.
- Where was the provider established, and who brought it into the Union? That identifies importer or distributor duties.
- Write the conclusion with its reasoning and the article you relied on.
Five rows per system, ten minutes each, and the whole obligation map becomes deterministic. This is also the field that enterprise questionnaires probe hardest: “State your role for each system listed” is a standard line in AI vendor security reviews.
One system, several roles at once
It is entirely normal to be a deployer of a licensed model and a provider of the application you built on it and an importer of a plugin you resell. The roles are attributes of the transaction, not of the company. Record them per system in the register, and re-run the analysis whenever you rebrand, resell or substantially modify something.
Frequently asked questions
Can we be both a provider and a deployer at the same time?
Yes — but for different systems, or for different aspects of one system. You are a provider of the AI features you brand and sell, and a deployer of the third-party tools you use internally. Record the role per system; the obligations attach to the role, not to the company.
Does using an AI tool internally ever make us a provider?
Only if you put your name or trademark on it, substantially modify it, or change its intended purpose in a way the original provider did not foresee. Configuring a licensed tool for your own use keeps you a deployer.
What counts as a substantial modification?
A change to the system that alters its intended purpose beyond what the original provider specified — particularly where the modified use falls into Annex III. Adding a new decision-making purpose to a general tool is the standard example; cosmetic changes, integrations and configuration are not.
Are we an importer if a US vendor sells directly to us?
Not necessarily. Importer duties under Article 23 attach to placing a third-country system on the Union market — distribution and onward availability matter more than where the invoice comes from. Selling or reselling that system into the EU market is where the importer role crystallises.
What happens if we get the role wrong?
The obligations are statutory and enforced by the market surveillance authority regardless of your internal reading. Getting it wrong typically means the wrong party was doing the documentation, so when the authority asks, neither side can produce it — which is a failure in itself under the information and cooperation duties.
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
Build a live AI register in minutes — upgrade only when you need the audit pack.
Keep reading
AI in healthcare under the EU AI Act: clinical decision support and high-risk duties
11 min
Risk & ClassificationThe Annex III High-Risk AI Systems List: All Eight Use Cases Explained with Examples
11 min
Risk & ClassificationThe Eight Prohibited AI Practices Under Article 5: A Compliance Checklist
10 min