TOPIC 02 OF 06
Provider or deployer?
Your role decides your dutiesThe same regulation puts very different obligations on the organisation that makes or brands an AI system (the provider) and the one that puts someone else's system to use under its own authority (the deployer). Getting your role right, per use, is what makes the rest of the duties make sense — and a single organisation can be a provider of one system and a deployer of another.
Using a third-party model inside your product feels like 'just a deployer' — but brand it as your own feature, or substantially modify it, and you can take on provider duties. The label isn't automatic; it depends on what you actually do with the system.
Assuming you're only ever a deployer because you didn't train the model is a common and costly error. Obligations differ sharply by role, so misidentifying it misdirects every duty that follows.
For one AI system you use, decide: are you the provider or the deployer here? Note what makes you think so — and whether any use pulls you toward the other role.