liveBook · Manning

Deployer

As explained in AI Governance

A regulatory role for an entity that uses an AI system under its authority, except where the system is used in the course of a personal, non-professional activity.

A deployer uses an AI system under its own authority, except for personal, non-professional use. Under the EU AI Act, the role carries obligations that cannot be delegated away simply because a vendor built the system. section 7.3 section 7.3.4

Role and risk classification are separate decisions. A company using a vendor’s tool as intended is generally a deployer. If it builds and puts its own system into service, it can be both provider and deployer of that system. Contract labels do not settle the role: what the organization actually does matters. section 7.3 section 7.3.6

Table 7.5 Activity-to-role mapping
What you do
Your role
Use a vendor’s AI product through their interface (e.g., ChatGPT, Copilot)
Deployer
Call a base model API and ship a product built around it (prompt scaffolding, RAG, UI) under your own name
Provider of your system; deployer of the underlying model
Host an open-source model internally with light prompts and filters, no distinct system built on top
Deployer (you cross into provider once you build a recognizable system on it)
Build and deploy an AI system for internal use (e.g., internal HR screening, claims triage)
Provider and deployer of your own system
Embed an AI feature into your existing software product, branded as yours
Provider of the integrated system
Buy a vendor AI tool and use it as intended (e.g., HR screening platform, credit scoring tool)
Deployer (if the use case sits on Annex III and Art. 6(3) doesn’t carve it out, full Art. 26 obligations apply)
Purchase a SaaS product with agentic workflows where you define the tools, system prompts, and purpose, branded as yours
Provider of the agent system
Build an agent on top of a vendor’s agent-building platform (Agentforce, Copilot Studio): you define tools, prompts, and purpose for your customers or staff
You are the provider; the platform vendor is a third-party supplier
Put your brand on a vendor’s AI system and offer it to clients
Provider via rebranding (Art. 25)
A consulting firm builds a custom AI system; the client puts it into service under the client’s name
Client is the provider (had it developed and put it into service under their name); firm is a third-party supplier
Resell a vendor’s AI without modification or rebrand
Distributor (Art. 24)

Compare common adoption patterns, including vendor tools, API-based products, and internally built systems. section 7.3.6

A deployer can become a provider of a high-risk system by branding and offering it to others, changing its intended purpose so it becomes high-risk, or making an unforeseen substantial modification affecting compliance or intended purpose. Fine-tuning alone is not the general trigger; placing a system on the market or putting it into service under your own name can establish provider status. section 7.3.2 section 7.3.6

Automating a credit decision

A bank licenses a credit-scoring tool tested for recommendations reviewed by a credit officer. Its engineers add an extension that automatically approves applications above a threshold. The change turns assisted decisions into automation the vendor did not validate, making the bank the provider of the modified system. section 7.3.2

For a high-risk system, turn deployer duties into operational checks:

  • Before signing, request the CE marking, declaration of conformity, and instructions for use. Treat missing compliance documentation as a red flag; do not deploy without the marking or declaration. section 7.3.4
  • Use the system within its intended purpose and validated input conditions. Establish human oversight with staff who can intervene. section 7.3.4 section 7.3.1
  • Monitor performance against provider guidance and report serious incidents. Reassess when significant changes to capabilities, data sources, or deployment context warrant it. section 7.5

How AI Governance covers it

How deep it goes
Sets out role-transition triggers and pre-deployment and live-operation checks for high-risk systems.
Examples
Uses a vendor credit-scoring tool modified for automatic approvals and an internally built screening system to illustrate role changes and overlap.
What you can do after
Evaluate and understand an organization’s AI Act role and identify checks for operating a high-risk system.
How it connects
Connects deployer status to provider status, risk classification, human oversight, and performance monitoring.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of AI Governance. The section links point to the parts of the book it draws on.