Putting an AI system into service means making it available for its intended purpose for the first time. Internal deployment counts: an HR team puts a screening tool into service when it starts using it. section 7.3.1
Putting a system into service under your own name can make you its provider. The trigger is not fine-tuning by itself: it is putting a system into service or placing it on the market. Building a specific-purpose application around a general-purpose model, including with retrieval, can create a new system. section 7.3.1 section 7.3.6
Internal deployment
An organization that builds and deploys an AI system for its own HR screening may be both provider and deployer of that system. section 7.3.1 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 to their provider or deployer roles, including internal systems and products built around model APIs. section 7.3.6
